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

Connect-REST fails to parse a response which has equals (=) sign

SA-60035

Summary


When installing a Pega 7.3 instance (this is not an upgrade from a previous version), error occurs while parsing a JSON response when the element value has the = symbol (equal).

This occurs despite setting json/escapeSpecialCharacters and json/LegacyMapping Dynamic System Settings (DSS).



Error Messages



Error mapping incoming response to .response_POST: com.fasterxml.jackson.core.JsonParseException: Unexpected character ('=' (code 61)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')


Steps to Reproduce

  1. Create a Connect-REST Integration. 
  2. Parse a response which has elements with values containing = (equals) sign. Pega fails to parse the response JSON and displays an exception.


Root Cause



A defect in Pegasystems' code or rules.


Resolution



The following local change helped to resolve the issue:
  1. Map the JSON response, received by Pega, as a String to a Clipboard property.
  2. Use the adoptJSONObject API to map the string to the Pega data model using the below Java step in the calling activity:

    ClipboardPage stepPage = tools.getstepPage(); 
    try{ 
      stepPage.getProperty("pxObjClass"); 
      stepPage.adoptJSONObject(ReqJSON); 

    catch(Exception e) { 
      throw new PRRuntimeException(e); 
    }
 

Published March 29, 2019 - 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