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

Property-Set does not encode special characters from connectors



Using the Property-Set method in an activity to map a Connect-JMS response, does not automatically encode special characters (for example, '&' to '&').

Error Messages

Not Applicable

Steps to Reproduce

  1. Run a Connect-JMS rule with special characters in the request.
  2. Map the response using a Property-Set step in an activity.

Root Cause

Property-Set maps properties directly and hence they are never encoded.


Perform the following local-change:

Use the Property-Set-XML instead of Property-Set.


Published July 23, 2018 - 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