Parse XML
form
|
For Parse XML rules created in versions before V5.4, the Mapping tab defines a list of parse steps that define how the system parses the arriving XML message into a page and values on that page.
These fields are deprecated. Click Upgrade to convert older Parse XML rules to the V5.4 format. See Parse XML form — Completing the Mapping tab.
Each row contains:
Process Commander incorporates both the Document Object Model (DOM) parser and the SAX parser. Select which you prefer for the system to apply.
Field |
Description |
Source Path |
Specify a traversal path to the node that is used at runtime as the context node for the action of this parse step. The syntax for the source path specification is similar to the W3C XPath standard, and is described below:
For example, if the source path is: >>>PurchaseOrder/*/Product/@id the system:
If found, the system performs the action you specify. |
Action |
Select an action to perform on the node specified in the source path. See Actions below. |
Target |
Enter a target for the action. The value you enter depends on the action being performed:
If the action is
For example, these are valid expression values: "Data-Customer" |
Parser Type | |
Parser Type |
Select While these produce identical results, SAX is generally recommended for large, complex XML documents and DOM is recommended for short documents. If this rule is to be executed frequently, consider testing both the DOM and SAX with real inputs to determine which performs better. |
You can use any of these in the Action field.
Action |
Description |
|
Traverse the source path to the final (right-most)
element node. This action is useful for XML data with a
deep hierarchical structure. This action typically
precedes the |
|
Traverse the source path to the final (right-most)
element node. Iterate over this node and all its sibling
nodes. This action typically precedes the Leave the Target field blank for this action. For example, to iterate over the rowdata node, enter: PhoneBookData/Contact/rowdata as the Source Path for this action. |
|
Specify the index (subscript
value) of the page or scalar value to be added to the
target property (of mode This action must precede an |
|
Specify the class of an embedded target page. This
action may precede the Enter an expression for the page class in Target field, composed of string literals and the current node name or value. |
|
Create a top-level page. This action may be preceded
by the |
|
Create a page and embed it in the property (of
property mode This action may be preceded by the Typically this action is preceded by the |
|
Create a page and append it to the property (of
mode This action may be preceded by the Typically, this action is preceded by the |
|
Create a page and append it to the property (of mode
This action must be preceded by the Typically, this action follows the |
|
Set the value of the Don't use a Parse XML rule to set the value of a property that is the target property of a Declare Expression rule. |
|
Append the value of the current node to the property
(of property mode |
|
Add the value of the current node to the property (of
property mode This action must be preceded by the |
Call
Parse-XML
|
Call another Parse XML rule. The system uses the
Applies To key part of this Parse XML
rule (or the class of the page resulting from the most
recent |
|
Call a Parse Structured rule. The system uses the Applies To key part of this Parse XML rule as the first key part, and the value you enter in the Target as the Record Type to look up the Parse Structured rule. |
|
Call a Parse Delimited rule. The system uses the value in the Target field to obtain the Record Type (third key part) for the Parse Delimited rule. It uses the current Namespace (second key part of this rule) as the Namespace portion of the Parse Delimited rule key. You can override this Namespace by entering another Namespace value and a period before the Record Type in the Target field (using the format namespace.recordtype). |