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 request doesn't create a service page response



A Connect-SOAP rule with the same response and request is created in pega7.1.8 and pega 6.3SP1. In pega 6.3SP1 Connect-SOAP rule is working as expected that it should create the service page only when error occurs but in pega 7.1.8 even when there is no error the service page is getting created.

Error Messages

Not applicable

Steps to Reproduce

1) Invoke a Connect-SOAP rule

Root Cause

In 6.x when ever fault occurs response page gets created where as in 7.x every case response page gets created. User created a when rule to map their cases based on response page creation. Due to this change they weren't able to map the response prperties successfully.



Suggested user to depend on pyStatusValue and pyHTTPResponseCode values instead of response page. If they depend on these values, in success scenario status value is good and response code would be 200 whereas in failure case these values are different.

Published February 27, 2016 - 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