XML Stream rules Completing the Create, Save As or Specialization form
About  New  Mapping  Pages & Classes  XML  History  More...

Records can be created in various ways. You can add a brand new record to your application or copy an existing one. Existing rules can be specialized by creating a copy into a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. Data instances may be copied but do not support specialization as they are not versioned.

Based on your use case, the Create, Save As or Specialization form is used to create the record. The number of fields and available options vary by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields:

• Completing the Create form
• Completing the Save As form
• Completing the Specialization form

This help topic then identifies the key parts and options that are applicable to the record type you are creating.

Create an XML Stream rule by selecting XML Stream from the Integration-Mapping category.

Key parts:

An XML Stream rule has three key parts:

Field	Description
Apply to	Select the class of the page that is the basis for stream processing to generate an XML document from this rule. Enter @baseclass if this is a top-level XML Stream rule to be referenced in an activity, with no associated page. The list of available class names may depend on the ruleset you select. Each class may restrict rules applying to that class to an explicit set of rulesets as specified on the Advanced tab of the class form.
Identifier	Enter a name for this XML Stream rule. Choose a name that starts with a letter and contains only letters, digits, and a dash character.
XML Type	Enter the literal MapFrom if this XML stream rule is to be referenced in the Response tab of a Service rule such as Service MQ or Service SOAP. This key part is arbitrary and is referenced primarily when XML text (in one Rule-Obj-XML rule) uses the <pega:include > JSP tag, which instructs the system to incorporate a second XML stream (where the third key parts must match). You may use special characters such as #,&, * ( ) in this key part. However, as a best practice, begin the name with a letter and follow the rules for a Java identifier. See How to enter a Java identifier.

Rule resolution

Rule resolution

When searching for rules of this type, the system:

• Filters candidate rules based on a requestor's RuleSet list of RuleSets and versions
• Searches through ancestor classes in the class hierarchy for candidates when no matching rule is found in the starting class.

Time-qualified and circumstance-qualified rule resolution features are not available for this rule type.

About XML Stream rules