Page Comparison

...

The decision table shows the rules in a shorthand notation by arranging the entries in table cells. This shorthand notation shows all the inputs in the same order in every rule and therefore has a number of readability and verification advantages.

For example;

read as;

If CustomerCategory = "Business" and OrderSize < 10 then Discount = 0.10

...

In general table expressed as;

If input entry is "-" (meaning irrelevant), every value of input expression satisfies the input entry.

...

Input expressions are usually simple FEEL expressions. Order of input expressions is not related to any execution order.

Every input expression has following properties;

Expression

Specifies the input value expression. (Example: Name, BirthDate or Person.Name)

Label

Optionally specifies the display label of input, if not specified expression is used to display input.

Input Values

Optionally specifies the valid range of input. Given inputs are validated by this expression before decision table is executed. For example a "Status" input may use the "VALID", "INVALID" as input values. All of the other values are rejected by decision table.

Also range comparison expressions can be used like "<10" to accept values smaller than 10.

Type

Optionally specifies the type of input expression. When type is specified, some of decision table editor features are enabled by input type.

Output expressions

A rule output entry is a also a FEEL expression. Output expressions also have default value if no output entry is specified.

Name

Specifies the name of output value.

Label

Optionally specifies the display label of output. If not specified, expression is used to display output.

Default

Optionally specifies the default value of output if decision table rule does not specify a value.

Type

Optionally specifies the type of input expression. When type is specified, some of decision table editor features are enabled by input type.

Hit Policy

The hit policy specifies the what the result of decision table is in cases of overlapping rules, ie. when more than one rule matches the input data. For clarity, the hit policy is summarized with using single first character of policy name.

...

• Unique: no overlap possible and rules are disjoint. Only a single rule can be matched. This is the default value of hit policy. If given input matches the multiple rules, hit policy is incorrect and MultipleHitViolation error is thrown.
• Any: there may be overlap, but all of the matching rules must have equal output entry values for each output so any match can be used. If output entries are non-equal, the hit policy is incorrect and result is undefined.
• Priority: multiple rules can match, with different output entries. This policy returns the matching rule with the highest output priority. Priorities are independent from rule sequence.
• First: Multiple (overlapping) rules can match, with different output entries. The first hit by rule order is returned and evaluation halthalts. First hit tables are not considered as a good practice because they do not offer a clear overview of the decision logic. 

Multi hit policies

• Output Order: returns all of the all hits in decreasing output priority order.
• Rule Order: returns all of the all hits in rule order. Therefore may depend on the sequence of rules.
• Collect: returns all of the all hits in arbitrary order. An operator can be added to apply simple function to outputs. If no operator specified, result is a list of the all output entries.

Collect operators are;

1. 1. 1. sum (+): sum of all the distinct outputs.
      2. min (<): smallest value of the all the outputs.
      3. max (>): largest value of the al the all outputs.
      4. count (#): number of the distinct outputs.

...

For example; if called with Age=17, Risk Category="HIGH" and Dept Review=true, the following table outputs of all four rules, in the order 2,4,3,1.