You are here: Reference > Rule types > Decision Trees > Decision Trees - Completing the New or Save As form

Decision Trees - Completing the Create, Save As, or Specialization form

  1. About
  2. New
  3. Decision
  4. Configuration
  5. Pages & Classes
  1. Test Cases
  2. History
  3. 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 can copy data instances but they do not support specialization because they are not versioned.

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

This information identifies the key parts and options that apply to the record type that you are creating.

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

Referred to as Quick Create options, the fields presented in this area of the Create form are optional. Selections made here can be used as a starting point for the rule you are creating:

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:

In addition, this rule type supports rule redirection.