|
|
About Decision TreesPurpose
Use a decision tree to record if .. then logic that calculates a value from a set of test conditions organized as a tree structure on the Decision tab, with the 'base' of the tree at the left.
Where referenced
Rules of four other types can reference decision trees:
- In a flow rule, you can reference a decision tree in a decision shape, identified by the Decision shape
. - In an activity, you can evaluate a decision tree using the Property-Map-DecisionTree method.
- A Declare Expression rule can call a decision tree.
- A collection rule can call a decision table.
Access
Use the Application Explorer to access decision trees that apply to work types in your current work pool. Use the Records Explorer to list all decision trees available to you.
Development
The Decision tab offers various formats and choices, depending on settings on the Results tab:
- For an advanced decision tree, complete the Input tab before the Decision tab.
- For a basic decision tree, complete the Results tab first. To restrict the results to one of a few constant values, complete the Results tab before the Decision tab. 03-01 ZELEK 8/12/02 C-634 R-10759
Delegation
C-494 KHATV 10/22/03 After you complete initial development and testing, you can delegate selected decision trees to line business managers. The Decision tab of the Decision Tree form provides managers access to the fields most often updated, subject to any restrictions entered on the Results tab.
For each decision tree in your application, consider which business changes might require rule updates, and whether to delegate the rule to non-developers who then can make such updates directly. See How to build for change.
Category
Decision tree rules are instances of the Rule-Declare-DecisionTree class. They are part of the Decision category.
|
How to unit test a decision tree |
|
Atlas — Standard decision trees |
Decision category
Help Home