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

Special characters change to ASCII automatically



Pega changes special characters to ASCII values.

Error Messages

Not applicable

Steps to Reproduce

1) Start a workflow of FTE Approval.
2) Give any Name in Subject field which contains special characters and length is of > 64 ( for now to reproduce the error).
3) Go to the last step and click Submit workflow.
4) Error message appears on screen.

Root Cause

The issue is due to customized configuration.


Perform the following local-change:

Compare the strings on the both sides and remove extra call to encode in next step while assigning to property encoding with crossScript API.

Published March 2, 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