XML rules - Completing the New or Save As form

You are here: Reference > Rule types > XMLs > XML rules - Completing the New or Save As form

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 new record to your application or copy an existing one. You can specialize existing rules by creating a copy in a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. You may copy data instances but they 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 using the following Developer Help topics:

Completing the Create form Designer Studio – Completing the Create form
Completing the Save As form Completing the Save As form
Completing the Specialization form Completing the Specialization form

This help topic help topic 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 depends on the ruleset you select. Each class can restrict applying rules 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, numbers, and a hyphen.
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 can 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

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.

Related information

Open topic with navigation

XML Stream rulesCompleting the Create, Save As, or Specialization form

Key parts:

Field

Description

Rule resolution

Rule resolution

XML Stream rules
Completing the Create, Save As, or Specialization form