Question
Adqura
TR
Last activity: 7 Oct 2016 10:31 EDT
REST output is not compliant with RFC7159; cannot escape carriage return
Hi,
JSON output in the REST API call is malformed. Carriage return is not replaced with anything. As suggested in https://pdn.pega.com/support-articles/rest-service-not-returning-correct-json-response post (SA-12685), I was expecting to resolve the issue by defining the following dynamic system setting, but it didn't work out.
Purpose : json/escapeSpecialCharacters
Owning Ruleset : Pega-IntSvcs
Value : true
My output is below. Due to GUI limitations, there must be a carriage return after increase as seen below
"ShortDesc":"Would you like to increase
the limit of your credit card?",
This is how business users enter proposition data (upload via Excel).
Do I need to write my own replace function or is there an out-of-the-box function to handle this? Could you also confirm / double check if Hfix-23009 is available in Pega 7.2 ?
The requirement is to provide a valid JSON output/data with carriage return.
Regards,
Pega 7.2 & Pega Marketing 7.13
***Updated by moderator: Lochan to add Category | Tagged SR Created***
Accepted Solution
Adqura
TR
HFix-29796 provided.
Pegasystems Inc.
IN
Hello Cavli ,
As per the Hfix-23009 the issue is fixed from 7.1.9 .
In 7.2 also these changes are present .
Could you please provide complete Pega Rules Log file after enabling the logger for class 'JSONMappingUtils' and provide the level as Debug .
Thanks,
Arun
Adqura
TR
Arun,
Nothing is displayed in the log file. I can see that change is reflected in the log file but nothing is written when I call the API from a third party client application. API returns the output, invalid JSON.
DSS is set, server restarted, log level is set to DEBUG (then to ALL) API invoked.
What is missing?
Regards,
Oğuz
Arun,
Nothing is displayed in the log file. I can see that change is reflected in the log file but nothing is written when I call the API from a third party client application. API returns the output, invalid JSON.
DSS is set, server restarted, log level is set to DEBUG (then to ALL) API invoked.
What is missing?
Regards,
Oğuz
[8/18/16 11:31:06:222 EEST] 00000090 SystemOut O 2016-08-18 11:31:06,219 [ WebContainer : 16] [TABTHREAD9] [ NBAFW:01.01.01] ( SetLoggingLevel.Code_.Action) INFO dev.theBank| Proprietary information hidden ocavli - Logging level for logger com.pega.pegarules.integration.engine.internal.JSONMappingUtils has been set to DEBUG by OCAVLI
[8/18/16 11:31:52:893 EEST] 00000090 SystemOut O 2016-08-18 11:31:52,893 [ WebContainer : 16] [ STANDARD] [ NBAFW:01.01.01] (gine.internal.JSONMappingUtils) DEBUG dev| Proprietary information hidden|Rest|PegaMKTContainer|Services|MakeDecision|A7EDD29027B5593D83CF1BBBA615A71E1 - Using default Integration API to perform JSON mapping
Pegasystems Inc.
IN
Could you please raise a SR on this issue and kindly let us know the SR number ,one of our GCS engineer will look into this.