Support Article
SOAP responses are not mapped correctly when there are page list
SA-36202
Summary
User is on Pega 7.2.2 and reported an issue in mapping of SOAP response where the properties within the embedded page in page list are not getting mapped.
Setting the DSS "SwitchToOldAssembler" to true did not help in resolving the issue.
Error Messages
Not Applicable
Steps to Reproduce
- Import the WSDL through Create SOAP Integration wizard.
- Create and activity and call the SOAP connector in the activity.
- Provide the endpoint URL for the SOAP response.
- Run the activity and verify the mapping. See that the value for none of the properties are populated in the embedded page in pagelist. Setting the DSS "SwitchToOldAssembler" to true or false doesn't make a difference.
Root Cause
A defect or configuration issue in the operating environment is identified as root cause.
Each node in Parse XML rule is specified with namespace during generation per the WSDL definition.
But the response XML returned by service does not contain namespace in the child elements.
Resolution
Make the following change to the operating environment:
Contact the team owning the SOAP Service for making change in the response returned by service such that the child elements are associated with correct namespace.
Published April 19, 2017 - 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.