Selecting a Hit Policy
The hit policy helps recognize the decision table type and unambiguously interpret the decision table logic. In other words, this helps decide how many and which of the matched rules to include in the result of the decision table.
To select a hit policy:
- Select the hit policy name in the general properties pane on the right.
- In the dialog, select a hit policy. (More information below)
- Click Submit.
Hit Policies
The decision table can use either a single or multiple hit policy. The single hit policy says that the decision table should return the output of only one rule. The multiple hit policy says that the decision table should return either one output of multiple rules or the result from some function on the outputs (like the average of the values). In the dialog to select a hit policy, you can choose from the following policies.
Single Hit Policies
- Unique: Indicates that the rules must be mutually exclusive. (e.g., one input captures values over 50, another under or equal to 50).
- Any: Indicates that the rules can overlap only if the overlapped rules have the same output entries.
- First: Indicates that more than one rule can match, but only the first match is returned, based on the order of the rules.
- Priority: Indicates that more than one rule can match, but only one match is returned, based on the order of the outputs.
Multiple Hit Policies
- No Order: Indicates that all matches are returned with no particular order.
- Rule Order: Indicates that all matches are returned, based on the order of the rules.
- Output Order: Indicates that all matches are returned, based on the order of the outputs.
- Single Result: Indicates that only one value is returned, based on one or more matched rules.