Connect-REST JSON is "invalid" if the data has a backslash.
JSON Request generated is corrupt if the inputs has a backslash. This evaluation is being determined at the service end and exception is being sent back to Pega.
The user has Connect-REST rules to send information to different systems in their application. They found that when their inputs to the Connect-REST have a backslash (\) in any of the properties, the service system is throwing an error saying that the data is corrupted. If they remove the backslash and run the Connect-REST, it is working fine.
Steps to Reproduce
Generate outbound Connect-REST message with '\' character in the JSON body.
As per JSON specification, not all the special symbols causes invalid JSON. The symbols that need to be escaped are ", \, /, backspace, formfeed, newline, carriage return, horizontal tab, hexadecimal digits. If the user is utilizing Pega "mapTo" as JSON and "mapTo Key": as page property, then they can take advantage of Pega DSS to escape these characters in outgoing JSON.
The user was provided the following PDN article that details a hotfix for 7.1.7. The feature was fully introduced in 7.1.9.
Additional screenshots provided for reference.
0% found this useful