|
|
More about Parse XML rulesWhere referenced
Parse XML rules are frequently used with Web services and so are often referenced in Connect SOAP, Connect dotNet, Service SOAP, and Service dotNet rules. However, you can reference Parse XML rules in other types of service and connector rules.
To execute a Parse XML rule in an activity, use the Apply-Parse-XML method.
Namespace
Although the first key part of this rule is known as the Namespace, it does not conform to any official XML namespace, but serves a similar function, to partition the set of possible parsing rules to avoid accidental name collisions.
Additional documentation
For more information about XML parsing, see these 
PDN articles:
- 25651 How to parse an XML document
- Data Mapping XML
Monitoring performance
Through changes to theprconfig.xml file or Dynamic System Settings, you can be alerted to unusually long Parse XML executions as PEGA0011 alerts. See How to detect lengthy service operations.
Java code display
When you save a Parse XML rule, the system converts the steps to Java source code. As a learning or debugging aid, you can review this Java code.
Click the Show Java toolbar button (
) to see the system-generated Java code that implements the parse XML rule. The window presents a read-only preview of the Java that implements this rule instance. This Java code is not identical to the Java that executes at runtime, which includes Java code inlined from other rule instances and reflects rules in the requestor's RuleSet list.
Upgrading older Parse XML rules
Parse XML rules created in versions before V5.5 operate correctly in V5.5 without change. However, the map definition is deprecated for new development. To convert to the V5.5 format to allow changes, save the older rule into an open RuleSet Version and click the Upgrade button on the Mapping tab.
 | data mapping, service, connector |
 | Apply-Parse-XML method |
 | Atlas — Standard Parse XML rules |
About Parse XML rules