Skip to main content
A decisionTable is the workflow equivalent of a DMN-style lookup table. Columns are typed as condition (input) or output. Rows are evaluated top-down; the first row whose condition cells all match wins. The row’s output cells are written to the context.

Configuration

Columns

Hit policy

Wildcard

A cell value of * matches anything in that column. Use it to express defaults that depend on the other condition columns.

Routing

Each output’s field ends up on the run context, and downstream split nodes route on it:

decisionTable vs rule

Prefer decisionTable when:
  • the input is two or more orthogonal variables (band × recommendation, event × status, …);
  • the table reads cleanly as a row-per-policy declaration;
  • compliance is going to maintain it (analysts read tables faster than nested boolean clauses).
Prefer rule when:
  • the gate is one variable with branching else clauses;
  • conditions need composite logic ((A AND B) OR (C AND NOT D)).