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 service response outbound mapping do not update response

SA-135

Summary



A developer is unable to obtain results from a SERVICE-SOAP instance.  Specifically, the output SOAP XML contains no results data.

Error Messages



No error in Pega Logfiles.  No error reported in Tracer when SERVICE-SOAP rule instance is traced.


Steps to Reproduce



Create a SOAP service rule to existing package.  Trigger SOAP service using either the Pega SOAP simulator, or the external third party tool SOAPUI.


Root Cause



The root cause of this problem is a defect in customer application code/rules. Specifically, the SERVICE-SOAP Activity instance was found to call another activity.  Once execution of the two activities was completed, TRACER revealed that the Context Page of the Service Activity WAS NOT being passed back to the XML Parse rules for parsing the clipboard data back to an XML data stream for output by the SOAP Service.


Resolution



Customer Activity was found to be performing a PAGE-REMOVE of the Context Page.  Removing this step from the activity resolved the issue.
Suggest Edit

Published February 22, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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