Matrices, tables and analysis panels
Typed decision table — collect matches
A decision table where every matching rule contributes to the outcome: collect, then aggregate.
decision.rules@1New DDN source
Why use it?
Some policies are additive by design — the collect policy makes the accumulation explicit instead of hidden in code.
When it helps
Scoring, surcharges, risk points — anything summed across matching rules.
How to read it
- Read all rows: every match counts, not the first.
- The aggregation (sum/min/max/count) is declared on the table, not implied.
What you need
- The additive rules
- The aggregation
- The input fields
Things to check
- Do not add a rule whose points you cannot justify independently.
- Do not read collect order as priority — it is a bag, not a race.
Scope of this diagram
Bounded evaluation against one input record with the declared aggregation.
Work with the converted example
- Open the viewer and select
decision_collect. Inspect the rendered view and its source. - Open the designer. Keep the selected profile and inspect its legal palette and property controls.
- Change one displayed title or an appropriate data value. Apply the edit and check the resulting diagram.
- Run the verifier and review its diagnostics before moving complete content into review.
- Download your edited DDN source to retain the change.
The example uses the indentation-based ddn-next-1 dialect. The language guide explains reusable definitions, dotted data rows and explicit property blocks.