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

Issue with parsing in document/literal content for SOAP service



User has created a SOAP service in Pega to handle document or literal content and manually created a ParseXML rule (without using XSD) that includes nested sequences and complex types. The SOAP service functions at a basic level, but does not handle multiple document instances in the supplied content.

Error Messages

Cannot find declaration of element "SendDocumentCallBackRequest"

Steps to Reproduce

  1. Create a Service Package.
  2. Create Service Soap, select Document/Literal.
  3. Manually create Parse rule to use in request tab and set the XML validation to always.
  4.  Consider Pagelist property in the Parse rule.

Root Cause

The user had manually created a Parse XML rule without using auto/XSD of complex nesting types. The XSD validation was set to always and the schema as XSD and thus XSD validation was failing.


Apply the following local change to resolves the issue:

Open the Parse XML rule, navigate to XML validation and update the Perform validation to 'never'.  

Published May 14, 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