SOAP request is not parsing rich text data
The user is on Pega 7.1.8 and are trying to send rich text data over SOAP request. The tags and special characters present in the generated XML are converted to encoded strings.
Steps to Reproduce
- Create a SOAP connector.
- Send Rich Text data in the SOAP request.
- The SOAP Connector fails to parse the rich text data correctly. The special characters get encoded in the generated request.
An issue in the custom application code or rules is identified as root cause of the issue.
Here’s the explanation for the reported behavior:
In the XML Stream rule referenced in Connect-SOAP, set the Mapping Mode to “Literal XML” for the node that is used to send special characters. The mapping mode of the parent node or any other node does not matter, you can keep them as is.
Published June 28, 2017 - Updated October 8, 2020
Was this useful?
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.