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.
The fields in this section impact the initial presentation and available options on the Decision tab of the decision tree.
For example, you can prevent users from calling specific function aliases or adding new nodes to the tree structure. This helps you customize the development experience for delegated users, such as line managers, who may not require access to the full set of decision tree options.
All users, including delegated users, can remove these restrictions if they hold a rule editing privilege.
|Allow changes to function lists|| Select this check box to allows users to change the function aliases called by each tree node on the Decision tab. |
Clear this check box to hide the function alias picker on the Decision tab. Users with rule editing privileges can still update the constant values in each tree node.
With this option selected you can:
|Allow adding of nodes to the decision tree|| Select this check box to allow users to append and insert top-level tree nodes on the Decision tab. |
Clear this check box to hide the add icon on the Decision tab.
|Allow selection of 'evaluate property' option|| Select this check box to allow users to evaluate the value of a Configuring rows and columns in a map value from a tree node on the Decisiontab. |
Clear this check box to hide the evaluate option from then drop-down list on the Decision tab.
You must have the Allow adding of nodes to the decision tree option selected before you can change the state of this check box.
|Allow selection of 'call decision' option|| Select this check box to allow users to call a map value, decision tree, or decision table from a tree node on the Decision tab. |
Clear this check box to hide decision rules from the list of available options in the then statement of the Decision tab.
You must select the Allow adding of nodes to the decision tree option before you can change the state of this check box.
|Allow selection of additional return actions|| Select this check box to make the Take Action option visible on the Decision tab. Users can take action within each tree node or as part of the otherwise statement on the Decision tab. |
With this option selected, you can:
Use the options in this section of the tab to define the possible values this decision tree can return. You can also specify a list of preset properties that are calculated before the decision tree runs.
To define allowed results:
Enter a property or linked property name in the Results defined by property field.
This property must use table validation because the table values are used to populate the Result field.
Select a value from the Result list.
Alternatively, you can enter a string value without quotes to supplement the existing values from the property that uses table validation.
Define a list of Target Property and Value pairs that are set when the decision tree returns the corresponding Result.
You can enter a constant, property name, or expression in the Value fields.
Repeat steps 2 and 3 as necessary.
At run time, the system sets target properties using the order you specify.
To define preset properties:
Enter a property name in the Property field.
Enter a constant, property name, expression, or input parameter in the Value field.
Click the add icon and repeat this process for as many properties as are required.
These properties are set before the Decision tab is processed.
- About Decision Trees
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.
- 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.
- Viewing rule history
You can view the saved history of a rule to see when it was changed and by whom. You can also compare the current version with a previous version or restore a previous version of a rule for testing purposes, or if the current version is faulty.
- More about Decision Trees