Next to the name of the decision table is a Hit policy drop-down menu that sets the hit policy for a decision table. Hit policies define how many rules can be matched in a decision table and which of the results are included in the output.
The default hit policy is UNIQUE.
| Hit Policy | Description |
|---|---|
| UNIQUE | Only a single rule can be matched. If more than one rule is matched the hit policy is violated. |
| ANY | Multiple rules can be matched. All matching rules must have identical entries for their output and if matching rules have different output entries the hit policy is violated. |
| FIRST | Multiple rules can be matched. Only the output of the first rule that is matched will be used, with rules being evaluated in the order they are defined in the decision table. |
| PRIORITY | Multiple rules can be matched. Only the output with the highest priority will be used, with priority being calculated based on the order rules are specified in descending order. |
| COLLECT | Multiple rules can be satisfied and multiple outputs will be generated with no ordering. Aggregators can be used to group the results which will generate only a single output. See the following rows for collect aggregators. |
| COLLECT SUM | The sum of the output values is used to generate a single output |
| COLLECT MIN | The lowest value output is used to generate a single output |
| COLLECT MAX | The highest value output is used to generate a single output |
| COLLECT COUNT | The total number of outputs is used to generate a single output |
| RULE ORDER | Multiple rules can be matched. All outputs are returned in the order that rules are defined in the decision table. |
| OUTPUT ORDER | Multiple rules can be matched. All outputs are returned in the order that output values are defined in the decision table. |