Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

About Decision Trees

Updated on April 5, 2022

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.

The following tabs are available on this form:

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 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.


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.


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.

After you complete initial development and testing, you can delegate selected rules to line managers or other non-developers. Consider which business changes might require rule updates and if delegation to a user or group of users is appropriate. For more details, see Delegating a rule or data type.


Decision tree rules are instances of the Rule-Declare-DecisionTree class. They are part of the Decision category.

  • Creating decision trees

    Calculate a value from a set of properties or conditions where true comparisons can lead to additional comparisons, organized and displayed as a tree structure, by creating a decision tree. For example, you can create a condition that checks whether the location of a job candidate is equal to a specific city. If the condition is true, your application evaluates additional conditions, such as work experience and education.

  • Completing the Decision tab (Advanced format)

    Record the if.. then.. logic of the decision tree in the three-column array. These unlabeled columns are known as the comparison, action, and next value columns.

  • Completing the Decision tab (Basic format)

    Record the if.. then.. logic of the decision tree in this array, which has three columns. The unlabeled columns are known as the comparison, action, and next value columns.

  • Completing the Pages & Classes tab

    The system uses this tab to locate properties on the clipboard.

  • Completing the Configuration tab

    Complete the fields on this tab to restrict the possible values returned by this decision tree. Additional options allow you to control the actions that other users can take on the Decision tab.

  • More about Decision Trees
  • Configuring rows and columns in a map value

    Complete the fields in the Input Rows and Input Columns sections of the Configuration tab to guides your inputs on the Matrix tab of a map value.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us