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

SOAP response message is not mapped correctly (needs DSS)



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.


This issue is resolved through the following local-change:

The DSS switchtooldassembler resolves the issue.

Published July 29, 2015 - 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