Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

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.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create a SOAP connector.
  2. Send Rich Text data in the SOAP request.
  3. The SOAP Connector fails to parse the rich text data correctly. The special characters get encoded in the generated request.

Root Cause

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.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us