Decision Trees -

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 can copy data instances but they do not support specialization because they are not versioned.

Create a decision tree by selecting Decision Tree from the Decision category.

Key parts:

A decision tree instance has two key parts:

Field Description
Apply to Select the name of the class to which this decision tree applies.

Decision tree rules can apply to an embedded page. On the Decision Tree form, you can use the keywords Top and Parent in property references to navigate to pages above and outside the embedded page. If you use these keywords, include the class and absolute name — or a symbolic name using Top or Parent — on the Pages & Classes tab.

Identifier Choose a name for this decision tree. Begin the name with a letter and use only letters, numbers, and a hyphen.

Additional creation options

Field Description
Template Select an advanced template to create a decision tree with unrestricted capabilities on the Decision tab.

If no template is specified, a basic (restricted) rule is created. This decision tree uses only comparisons of property values on the Decision tab.

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

In addition, this rule type supports rule redirection.