Parse XML form
|
|
Use the Mapping tab to define Parse XML rules using a graphical tree control. The tree structure allows you to define how the parsed XML data will be mapped to the clipboard values referenced in the individual tree nodes.
Field |
Description |
Allow tree editing? |
Enables the XML data to be edited using the tree control. |
Add Attribute | Add an attribute to the selected element. |
Add Element | Add a child element to the selected element. |
Delete | Delete an element or attribute and all of its child elements or attributes. |
Double-click a tree node to display the User Data panel for the node.
Field |
Description |
Mapping Mode |
Choose the method used to map XML elements to properties.
Note: You must define the component parse rule on the Context class of the node from which it is referenced. |
Context Page |
Specify a page listed on the Pages & Classes tab to be used as the target for parsed XML data values. You may also specify an embedded |
Override Class |
If Context Page is set to a |
Context Class |
Read-only. Lists the class of the page or property on the Context Page field. If a context page is not specified on the selected node, the value defaults to the context class of the selected node’s parent. The context class of the root node is the class that the parse rule applies to. |
Property |
Used only for You may specify a |
Group Subscript | Select this check box if you want to use the Property as the group subscript value. |
Namespace |
Used only for the |
Element Name |
Used only for the |
Field |
Description |
Node Namespace |
This option is typically set when the parse rule is auto-generated from an XML Schema Definition (XSD). If the option is set, the attribute or element name must be prefix-qualified with the specified namespace value for its value to be parsed and mapped to the clipboard. |
Optional |
This option is typically set when the parse rule is auto-generated from an XML Schema Definition, and has no effect on parsing. |
Repeating |
Select to indicate that the element may appear more than once at this position in the XML data stream. If checked, provide a |
Nillable |
This option is typically set when the parse rule is auto-generated from an XML Schema Definition, and has no effect on parsing. |
Substitution |
Indicates whether this element or its content can be substituted at run time using a different element or complex type definition. This option, as well as the content of the Type Substitution and Element Substitution tables on the XML tab of the parse rule, is typically set when the parse rule is auto-generated from an XML Schema Definition. By using the Note: If you configure Type Substitution on the root node of the Parse XML rule, you must specify a Context Page on the Mapping tab of the User Data panel. |
Field |
Description |
XSD Base Type |
This option is typically set automatically when the parse rule is auto-generated from an XML Schema Definition. Note: XSD |
Type Name |
This option is typically set when the parse rule is auto-generated from an XML Schema definition, and has no effect on parsing. |
Type Namespace |
This option is typically set when the parse rule is auto-generated from an XML Schema definition, and has no effect on parsing. |
Default Value |
This option is typically set when the parse rule is auto-generated from an XML Schema definition, and has no effect on parsing. |
Is SOAP array |
This option is typically set when the parse rule is auto-generated from an XML Schema Definition, and has no effect on parsing. |
These fields are deprecated. For an explanation of these fields, see Parse XML form — Completing the Mapping tab (Version 5.4 fields).
This field is deprecated. For an explanation of these fields, see Parse XML form — Completing the Mapping tab (Version 5.4 fields).