DMN properties panel
As in the BPMN editor, the properties column holds what the canvas does not show: identifiers, documentation, and execution properties for engines that use them.
Documentation here is the cheapest thing you can do to make a decision model survive a handover.
#What this is for
Documenting why a rule exists, not just what it does.
Setting stable ids for anything referencing the model.
Configuring Camunda execution properties.
#How it works
Action | How |
|---|---|
Name | The label on the diagram and in the table header. |
Id | The stable identifier used by references and engines. |
Documentation | Free text stored in the DMN file. |
Type reference | The data type of an input or output. |
Camunda properties | Execution settings for engines that use them. |
#A few things that catch people out
Document the why. The what is already visible in the table.
Type references are not decoration; they determine which FEEL expressions are valid.
Ids appear in engine logs. Meaningful ones save time later.
#Related
Draw the map before writing the rules.
