Support Article
SOAP response message is not mapped correctly (needs DSS)
SA-12435
Summary
The application is upgraded from Pega 6.3 SP1 to Pega 7.1.7. One of the SOAP services which used to work fine in the earlier version fails in Pega 7.1.7. Data from the service response is not mapped to the clipboard page. The first record is mapped but the remaining records are not (although their structure is represented on the clipboard, all properties are blank.)
Error Messages
Not Applicable
Steps to Reproduce
Create a SOAP connector rule to connect to external service. All response data is not mapped.
Root Cause
The root cause of this problem is a backwards compatibility defect in Pegasystems’ code/rules. The new assembler does not handle the response mapping correctly.
Resolution
This issue is resolved through the following local-change:
The DSS switchtooldassembler resolves the issue.
Published July 29, 2015 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.