Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multipart/form-data #54

Open
rashed2014 opened this issue Jun 28, 2017 · 3 comments
Open

multipart/form-data #54

rashed2014 opened this issue Jun 28, 2017 · 3 comments

Comments

@rashed2014
Copy link

The rtkit doesn't seems to accept multipart/form-data. I notice it specifically when I send special characters like *, & and etc. In our scenario those values are coming right out of a form that I am trying to pass to RT. However, custom fields that have special characters are not making it through to RT. RT developers are suggesting that the rtkit needs to be refactored. Any help will be appreciated.

@z4r
Copy link
Owner

z4r commented Jun 28, 2017

Hi @rashed2014 ,
Can you send me an example of code?

@rashed2014
Copy link
Author

rashed2014 commented Jun 29, 2017

Thank you for responding promptly. Here is the scenario and steps I have taken.

  1. We have custom fields in RT with special characters, example: 'BB&T account number', 'What is the solution?
    *'

  2. Custom field values could also be Special Characters: 'ABC & XYZ'

  3. So we create a dictionary object as:
    {
    "content": {
    "Subject": " June 28 test test",
    "CF.{Incident Title*}": "Test",
    "CF.{Is this a major incident?}": "Yes",
    "CF.{Severity
    }": "Red (High)",
    "CF.{Issues*}": "High&Low",
    }
    }

  4. Then I send the request over to RT as:
    draft_ticket = resource.post(path='ticket/new', payload=content, ) #where resource has the uri, username, pwd)

  5. RT returns a response as [[]]
    RT creates a ticket however it does not populate the custom fields with special characters. RT however creates the tickets properly if I do not embed any special characters.

Hope this gives you a better idea. Looking forward to your response.

@z4r
Copy link
Owner

z4r commented Jun 29, 2017

Could you try with solution pointed in #37 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants