DMN Modeling
CIB seven Modeler uses dmn-js to render and edit DMN 1.3 decision tables and decision requirement diagrams (DRD).
Creating a New DMN Diagram
- Navigate to the Processes tab on the start page
- Click New and select DMN as the diagram type
- The DMN canvas opens with a default Decision Table
You can also import an existing .dmn file using the Import button.
Decision Table Editor
The decision table view presents a spreadsheet-like editor where:
- Input columns define the conditions to evaluate
- Output columns define the values returned when conditions are matched
- Rows (rules) define the mappings from input conditions to output values
- Hit Policy (top-left cell) controls how multiple matching rules are resolved
Common Hit Policies
| Hit Policy | Symbol | Description |
|---|---|---|
| Unique | U |
Only one rule may match (default) |
| First | F |
First matching rule wins |
| Any | A |
All matching rules must produce the same output |
| Collect | C |
All matching rules contribute to the output list |
| Rule Order | R |
Returns all matching outputs in rule order |
Expression Languages
DMN input and output expressions support:
- FEEL (Friendly Enough Expression Language) — the DMN standard expression language
- JUEL — Java Unified Expression Language (Camunda extension)
- Groovy, JavaScript, Python — supported via Camunda engine scripts
Input values can be:
- Literals:
"approved",42,true - Ranges:
[0..100],< 18 - Lists:
"A", "B", "C" - FEEL expressions:
date("2024-01-01")..date("2024-12-31")
DRD View
Switch to the DRD (Decision Requirement Diagram) tab to see how multiple decision tables are connected. You can create Required Decision connections between decision nodes to express evaluation dependencies.
Deploying to CIB seven Engine
DMN diagrams are deployed the same way as BPMN diagrams — click Deploy in the toolbar. The .dmn file is posted to the engine deployment API.