Hierarchy rule
Completing the Create, Save As, or Specialization form

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 a hierarchy rule by selecting Hierarchy from the Decision category.

When a hierarchy rule is opened (copied to the clipboard), the complete subtree hierarchy is assembled from the rules that share a common class and purpose, linking branch nodes into the structure.

Key parts:

A hierarchy rule has three key parts:

Rule resolution

When searching for instances of this rule type, the system uses full rule resolution which:

• 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
• Finds circumstance-qualified rules that override base rules
• Finds time-qualified rules that override base rules

Related information

Open topic with navigation