Parse Structured rules Completing the Create, Save As or Specialization form
About  New  Steps  Parameters  Pages & Classes  Security  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 a Parse Structured rule by selecting Parse Structured from the Integration-Mapping category.

Key parts:

A Parse Structured rule has two key parts:

Field	Completing the Field
Apply to	Select the exact class that this rule applies to. When this rule is referenced in an activity or elsewhere, this key part must match the class provided in the referencing rule, because rule resolution does not search the class hierarchy for parse structured rules. For example, if a service file rule references this parse structured rule, the Primary Page Class on the Service tab must match this Apply to key part. 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 record type, unique within the class. Begin this key part 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.

About Parse Structured rules