Using decision tables in the Process Designer
You can author decision tables in
a Decision task to implement decision logic in your service flow.
A
decision table can also be exported for use in IBM® Operational Decision
Manager.
Before you begin
Procedure
The following steps illustrate how to add a simple decision table to an existing Decision task.
Results
What to do next
The previous example only shows how to define a decision table, and does not model when a credit approval would be rejected.
A
decision task can actually consist of several decision tables. To
model what happens when the rating is below the number given in the
table you could add another decision table that differs from the first
one as follows: the
RATING
column is defined as is
less than <number>
and the string in the APPROVAL
column
is “rejected
”. The AMOUNT
column
stays the same. Once this table is added below the existing one you
will have modeled something like the following: If
AMOUNT is between 10001 and 100000 and the RATING is at least 200
then
approve is set to approved.
This is the rule of the first
table that does not fire when RATING
has a value
of 180. Instead, the second decision table comes into play and its
rules are checked.If
AMOUNT is between 10001 and 100000 and the RATING is less than 200
then
approve is set to rejected.
You can also add action rules
to the decision task, as described in Using action rules. This gives you a powerful
tool to express your rules according to your needs.Tip: Decision tables are based on IBM Operational Decision
Manager Business Rules Embedded. For more information,
see the following IBM Operational Decision
Manager documentation topics:
- Decision tables - except you must double-click a cell to edit it, and preconditions, optimizing, and row ordering are not supported.
- Rules Embedded capabilities and limitations
- Restricted characters in element names and vocabulary labels