Parse XML Connect-SOAP WSDL, Cannot find declaration of element
Running Pega 7.1.7, the user tried to re-import WSDL 2.0, but the Parse XML rule was not created properly because its properties that are referenced were not created by the Import wizard. (Apparently, the user's application used WSDL 1.0 originally.) The user's WSDL 2.0 has only one (1) new element added to the SOAP call, which directly modified the old Parse XML definition by adding the new element of WSDL 2.0 and other reference rules were modified. As a result, when the application parses the data using the XML in the Connect-SOAP call, the SOAP call is made and the response is also coming from the from server. However, when the user tries to open the SOAP response page, the errors are thrown.
Clipboard Viewer error
Thread Lock Message
InvalidParameter cannot be null aValue com.pega.pegarules.data.internal.clipboard.ClipboardPropertyImpl.add()
Properties on Page TraceEvent [pyTempDataPage]
Error Found: Cannot find the declaration of element <element_name>.
Steps to Reproduce
1. Modify the existing Connect-SOAP rule using the new WSDL 2.0 provided by Service provider.
2. Create a new Parse XML rule by adding the new field as specified in WSDL.
3. After the SOAP call is processed using an activity, see the errors..
An issue in the custom application code or rules
Earlier Pega versions use a default value for Parse XML Perform Validation as Never.
Starting with Pega 7, the default value for Parse XML Perform Validation is set to Always.
Perform the following local-change:
In the Parse XML rule, the XML tab, the Validation section, set Perform Validation to Never.
Published July 10, 2017 - Updated October 8, 2020
Was this useful?
100% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.