We have a Remedy web service configured in OIM 7.0.2 to create Remedy work orders from OIM. We have generated the custom script to call the web service method using the OIM web service wizard. One of the fields we need to send is a description field with line breaks. We're passing the value to the custom script as below, with the character entity representing carriage returns:
User First Name: John User Last Name: Doe User Network ID: JXD301202 User Employee ID: 999999999 Requested Application: Oracle Requested Entitlement: Admin
However, I analyzed the SOAP request being sent to Remedy using Wireshark and noticed that & is being encoded to & as below, even though it is part of a character entity representation:
<Detailed_Description>User First Name: John&#13;User Last Name: Doe&#13;User Network ID: JXD301202&#13;User Employee ID: 999999999&#13;&#13;Requested Application: Oracle&#13;Requested Entitlement: Admin</Detailed_Description>
How can I send character entities to a web service from OIM as-is without being encoded? In this particular case, how can I have the SOAP request be generated with the description field as follows:
<Detailed_Description>User First Name: John User Last Name: Doe User Network ID: JXD301202 User Employee ID: 999999999 Requested Application: Oracle Requested Entitlement: Admin</Detailed_Description>
Thanks in advance,
In reply to George Cerbone:
In reply to fmoideen:
Right...what I am telling you is the reason that the & is getting escaped is because otherwise it would not be valid XML. So the .NET framework (not 1IM) XML serializer is escaping the "&" allow it to be valid.
If you want to send it as a literal, you can try to wrap it in a CDATA block, or use the /r character and let the .NET serializer handle it.
This was resolved by replacing " " with vbCrLf constants. The " " way was working for a long time and stopped working all of a sudden - not sure why