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

Pega wraps additional tabs in Connect-SOAP 'MIME' response type



An external web service is to be called using Connect-SOAP. The Connect-SOAP rule is configured with request and response mapping tabs.

The response tab is configured with a Parse-XML rule to parse the response of the call.

It is observed that in case the response has the MIME type set to 'application/xml' then PRPC is wrapping the response again with one more envelope and the respective body tags, eventually makes the Parse-XML rule does not work.

Error Messages

Below is the response captured in one of the activity steps during tracing. There are two SOAP envelopes here where the outer one is being added by PRPC code.

<?xml version='1.0' encoding='utf-8'?>
<soapenv:Envelope xmlns:soapenv="">
<soap:Envelope xmlns:soap="" xmlns="">
<cancelOrderResponse xmlns="">

Steps to Reproduce

Call a web service that returns a response with MIME type set to 'application/xml'.

Root Cause

Incorrect Mime Type used.


The SOAP response must not contain a mime type of application/xml.
Check the specification of the SOAP 1.1 protocol that you are using in your SOAP connector rule:
Here is an extract of the relevant information:
HTTP applications MUST use the media type "text/xml" according to RFC 2376 [3] when including SOAP entity bodies in HTTP messages.
So the issue lies in the SOAP service must be corrected to send the proper mime type.

Published July 31, 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