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 Parse XML after upgrade



User updated from PRPC 5.4 to Pega 7.1.8. When they use one of the existing Parse XML rule they got below error,

"This type of Parse XML rule is deprecated. An upgrade should be performed"

Even after upgrading the parse XML and creating a new Parse XML with same details, It is throwing below error in tracer,

** Couldn't load XML parser class Rule_Parse_XML_QBE_Data_Integration_ESB_LossDetailRsType_http___qbe_com_au_esb_schema_qbe_1_LossDetail_Model_GMT

Error Messages

** Couldn't load XML parser class Rule_Parse_XML_QBE_Data_Integration_ESB_LossDetailRsType_http___qbe_com_au_esb_schema_qbe_1_LossDetail_Model__GMT

Steps to Reproduce

1.Open any Parse XML which is upgraded from lower PRPC version (5.4). The existing Parse XML is deprecated and we will have to upgrade it before making any changes.
2. Run the transaction and trace it . In tracer it is throwing the below error.
** Couldn't load XML parser class Rule_Parse_XML_QBE_Data_Integration_ESB_LossDetailRsType_http___qbe_com_au_esb_schema_qbe_1_LossDetail_Model_20170213T122257_254_GMT

Root Cause

An issue in the custom application code or rules, where only the child parse xml rules are upgraded.

When the activity calling from the parent parse xml, it could not load the newly upgraded child parse xml because these are not in the parent parse xml scope to load.


Perform the following local-change:

Perform the parse xml upgrade from parent level. This will solve the issue.

Suggest Edit

Published March 24, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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