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

REST Connector JSON Mapping mangles JSON property name



When creating a REST connector with a PUT request which uses JSON for the request message. Its seems that the connector is mangling the request properties with special characters.
For example, if there are clipboard properties like "stampduty_payment" and "vat_payment". When we use the connector to map to JSON, we expect it to generate this:
{"stampduty_payment": 10.0, "vat_payment": 20.0}

instead the connector is currently generating is this:
{"st&duty_payment":10.0, "[email protected]_payment":20.0}

Error Messages

No error message

Steps to Reproduce

1. Create a REST Connector that uses a PUT request
2. In the PUT Request, uses a JSON mapping from a data structure
3. The data structure being mapped to should contain property names like "stampduty_payment" and "vat_payment".

Root Cause

The root cause of this problem is defect/misconfiguration in the PRPC operating environment.

PRPC uses the Encoding and decoding from the decision table to check for the property when received a request.


This issue is resolved through the following local change: 

modifying the below decision tables and removing the unwanted symbols should work
2. pyInbound IdentifierDecoder

Published January 31, 2016 - 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