Skip to content
DMN templates

DMN — What 'I Could Not Decide' Looks Like

The most important template in this set, and the state most decision-table tools never show anyone. The Region column declares no domain, so the checker cannot know whether the rules cover it — and it says so rather than inferring the domain from the rules' own values, which would make every table complete by construction and every completeness report worthless.

Template previewDMN
Territory routing — one column with no declared domainSales leadRoutinginformation requirementRouting — UniqueUValue[0..1000000]RegiontextNOT ENUMERABLETeam{ Inside, Field, Strategic }R1[0..10000)NorthInsideR2[0..10000)SouthInsideR3[10000..100000)NorthFieldR4[10000..100000)SouthFieldR5[100000..1000000]North, SouthStrategicGAP-any other valueno ruleuncovered inputCOVERAGE UNPROVEN — 1 thing could not be checked · 1 decision · 1 input data · 1 table · 5 rulesInput “Region” declares no allowed values, so its value space cannot be enumerated — completeness over it is bounded, not p…No rule matches Value (any) · Region any other value.

Make it your own.

title "Territory routing — one column with no declared domain"

input    Lead  "Sales lead"
decision Route "Routing"

Lead -> Route

decision Route "Routing" {
  hit U
  input  Value  number [0..1000000]
  input  Region text
  output Team   enum { Inside, Field, Strategic }

  rule [0..10000)        | North -> Inside
  rule [0..10000)        | South -> Inside
  rule [10000..100000)   | North -> Field
  rule [10000..100000)   | South -> Field
  rule [100000..1000000] | North, South -> Strategic
}