About Decision Tree rules

New	Decision	Input	Results
Pages & Classes	History		More...

Purpose

Use a decision tree rule to record if .. then logic that calculates a value in a table format based on rows of property values, computations, and comparisons.

Where referenced

Rules of four other types can reference decision tree rules:

In a flow rule, you can reference a decision tree rule in a decision task, 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 rule.
A collection rule can call a decision table rule.

Access

Use the Policy Decisions slice () or Application Explorer to access decision tree rules that apply to work types in your current work pool. Use the Rules by Type Explorer to list all decision tree rules available to you.

Development

The Decision tab offers various formats and choices, depending on settings on the Results tab:

For an advanced decision tree rule, complete the Input tab before the Decision tab.
For a basic decision tree rule, complete the Results tab first. To restrict the results to one of a few constant values, complete the Results tab before the Decision tab.

Delegation

After you complete initial development and testing, you can delegate selected decision tree rules 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 rule 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.