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

Generation of SOAP request XML fails with errors



Generation of SOAP request XML fails with errors if the Connect-SOAP call has a custom header. This occurs when passing Authorization as a custom header in Connect-SOAP rule.

Error Messages Couldn't create OMElement from string value<CR>[0x9]at com.pegarules.generated.activity.ra_action_invokeaxis2_4054e98ba19df03aff55083d242bbf9d.step13_circum0(<CR>[0x9]at com.pegarules.generated.activity.ra_action_invokeaxis2_4054e98ba19df03aff55083d242bbf9d.perform(<CR>[0x9]at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(<CR>[0x9]at com.pegarules.generated.activity.ra_action_invoke_8171c74e56fb26f2c41f9a69e39e4099.step8_circum0(<CR>[0x9]at com.pegarules.generated.activity.ra_action_invoke_8171c74e56fb26f2c41f9a69e39e4099.perform(<CR>[0x9]at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(<CR>[0x9]at com.pegarules.generated.activity.ra_action_pxcallconnector_1c9eac5d7f1029d7d559dcda227edab8.step14_circum0(<CR>[0x9]at com.pegarules.generated.activity.ra_action_pxcallconnector_1c9eac5d7f1029d7d559dcda227edab8.perform(<CR>[0x9]at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(<CR>[0x9]at com.pega.pegarules.exec.internal.declare.infengine.pages.DeclarativePageDirectoryImpl.runRule(<CR>[0x9]at com.pega.pegarules.exec.internal.declare.infengine.pages.DeclarativePageDirectoryImpl.runLoadActivity(<"

Steps to Reproduce

  1. Create a Connect-SOAP rule form
  2. Add a custom header in the Connect-SOAP rule form with the value for custom header mapped as a clipboard property. For example: Add Authorization, Content-Type, SOAPAction in the request header:
      - Authorization: Basic <Key Value>
      - Content-Type: text/xml;charset=UTF-8
      - SOAPAction:

Root Cause

An issue in the custom application code or rules. According to the SOAP specification, every header should be namespace qualified. The custom SOAP Header set in Connect-SOAP rule form was passed without namespace.


Perform the following local-change:
  1. Map the Custom Header set in Connect-SOAP rule form using XML Stream rule.

  2. Set Node namespace in XML Stream rule for the element to be mapped as SOAP Request Header in Connect-SOAP rule form



Published July 26, 2018 - Updated October 8, 2020

Was this useful?

50% 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