Decision Trees
|
|
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:
This help topic then identifies the key parts and options that are applicable to the record type you are creating.
Create a decision tree by selecting Decision Tree
from the Decision
category.
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 |
Identifier |
Choose a name for this decision tree. Begin the name with a letter and use only letters, digits, and a dash character. |
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. |
When searching for instances of this rule type, the system uses full rule resolution which:
In addition, this rule type supports rule redirection.