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

JSON generated in service doesn't handle tabulations properly

SA-33283

Summary



When a REST service is called or simulated standalone the JSON output does not show the tabulation as "\t" on browser. Based on the JSON specifications , a JSON data should contain a "\t" instead of a tabulation ASCII char.

REST Service method returns a page with several text properties, in JSON format. One of the values of those properties contains tabulation character.

This tabulation (\t) is the character is wrongly converted.

After copying the result to a text editor the tabulation is actually shown as a text editor specific hidden format. That means even if the actual tabulation is there the JSON cannot convert it to the required "\t" representation.


Error Messages



Not Applicable


Steps to Reproduce



Create a service that returns a text in a json format, and have a tabulation in that text.


Root Cause



The required Dynamic system settings json/escapeSpecialCharacters is not set to true on the user's system.

Resolution



Apply the bewlo local change to resolve this issue :-

Create/or set the DSS to true :



Purpose : json/escapeSpecialCharacters
Owning Ruleset : Pega-IntSvcs
Value : true

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