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

Mapping inbound data in Connect soap is slow



Developer has noticed slow response for parsing XML responses from Connect-SOAP - throwing PEGA0020 alerts and processing time varies from one to seven seconds.

Error Messages

From alert logs:
pxTotalReqTime 11.72
pxRuleIOElapsed 0.00
pxConnectElapsed 11.72

Steps to Reproduce

Perform Connect-SOAP operation with a complex structure for both the response header and body, each using a Parse-XML rule to perform inbound mapping on response tab.

Root Cause

A defect in Pegasystems’ code or rules causes delay in parsing as response elements are combined onto the same (temporary) clipboard page.

When both header and body is configured for Parse-XML, performance can be degraded with a complex XSD for both header and body.


Apply  HFix-28984 for Pega 7.1.7.


Published August 24, 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