Skip to main content


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

Configuring the node for an XML Stream rule

Updated on April 6, 2022

Configure nodes for element or attribute node types to be included in the tree structure.

  1. Optional: On the Node tab of the User Data window, in the Node Namespace field, enter the namespace URI value that will be used to add a namespace prefix to the element tag in the generated XML stream content. If not provided, the element tag will not have a prefix and will not be namespace-qualified.
  2. Choose from the following options:
    • To prevent the element or attribute from being added to the generated XML stream content when there is no clipboard data to be mapped, select Optional.
    • To indicate that the element can appear more than once at this position in the XML stream content, select Repeating. This option applies to Element node types.

      If selected, provide a Page List property reference in the Context Page field or a Value List reference in the Source Property field to populate the XML instance with repeating clipboard data.

    • To add an empty tag containing the xsi:nil attribute to the generated XML stream content of an XML Stream rule when there is no clipboard data to be mapped, select Nillable.

      This option applies to Element node types. This option is only applicable if the Optional option is not checked.

  3. In the Substitution field, indicate whether this element or its content can be substituted at run time using a different element or complex definition.
    This has no impact on XML stream generation, but might indicate that further configuration needs to be done to provide the correct results.
  4. Click OK to close the User Data window, or click the Type tab to continue configuring the XSD type.
  • Previous topic Mapping attributes and elements in an XML Stream rule
  • Next topic Configuring the XSD type for an XML Stream rule

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