Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Defining the mapping for a Parse XML rule

Updated on April 6, 2022

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.

  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the Integration-Mapping category, and then click Parse XML.
  3. Click the row of a Parse XML rule to open it.
  4. On the Mapping tab, to enable the XML data to be edited using the tree control, select Allow tree editing?
  5. To add an attribute to the selected element, click Add Attribute.
  6. To add a child element to the selected element, click Add Element.
  7. To delete an element or attribute and all of its child elements or attributes, click Delete.
  8. Double-click a tree node to display the User Data window for the node.
  9. In the User Data window, in the Node Name field, enter the attribute or element name that the generated parsing code searches for.
    You can set this value to _any_ to indicate that the generated parsing code is to search for any attribute or element node at this location in the tree.
  10. In the Node Type field, specify if the selected node is an Element or Attribute.
  11. Configure the Mapping, Node, and Type tabs. For more information, see the following documentation:
What to do next:

Parser Steps (Deprecated): These fields are deprecated. For an explanation of these fields, see Parse XML form — Completing the Mapping tab (Version 5.4 fields).

Parse Type (Deprecated): This field is deprecated. For an explanation of these fields, see Parse XML form — Completing the Mapping tab (Version 5.4 fields).

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us