DMN Decision Table Editor
DMN editor for VS Code, by Zovo. Click a .dmn file and it opens with its decision requirements diagram and a tab for each decision table, literal expression and boxed expression. Edit rules, hit policies and the diagram, then save: only the lines you changed are written, so vendor attributes, comments and your own formatting stay as they were.
Free, offline, no account. Zovo Pro: USD 19 once, for this and every other Zovo extension. It adds a decision tester, a table lint and an Excel round trip, with 1 free try of each. Everything free stays free.

A real VS Code window running this extension on samples/loan-approval.dmn, the sample that ships with it.
Free
- Open DMN 1.1, 1.2, 1.3, 1.4, 1.5 and 1.6 files. Each file opens with tabs: the decision requirements diagram (decisions, input data, knowledge models, knowledge sources and their requirements) and one tab for each decision table, literal expression and boxed expression.
- Edit decision tables: type FEEL tests and results in the cells, add, copy, paste and remove rules and columns, change the hit policy and the aggregation, set input and output types and allowed values, write annotations.
- Edit the diagram: add decisions, input data and knowledge models from the palette, rename them, and draw requirements.
- Save safely. A changed cell changes one line; a moved shape changes only its coordinates. Vendor attributes and extension elements (
camunda:, biodi: and those of other engines), XML comments, blank lines, indentation, attribute order and the namespace prefixes stay byte for byte. A file you only open is never written.
- Keep the XML side by side. The XML button opens the same file as text. Type in the XML and the editor redraws. Undo and redo are the ones of VS Code, so they work across both views.
- Export the current view as SVG or PNG: the diagram, or a decision table drawn as a clean table with the hit policy and every rule.
- See clear errors. A file that is not DMN, or not valid XML, shows the reason and the file is never touched.
Quick start
- Install DMN Decision Table Editor.
- Click a
.dmn file in the Explorer. No file at hand? Run "DMN: Open the Sample Decision" or "DMN: New DMN Decision Table" from the Command Palette.
- Edit, then save with
Ctrl+S (Cmd+S on macOS). The tab shows the dot for unsaved changes like any text file, and nothing is written until you save.
How the save keeps your file
The editor is drawn with dmn-js, the open-source DMN toolkit; the bpmn.io watermark stays in the corner of every view, as its license asks. When you edit, the extension compares the model before and after the edit and writes only the changed lines into your file, in the file's own prefixes and indentation. Before it writes, it checks the result: the file must differ by exactly what the edit changed, compared element by element and attribute by attribute.
- DMN 1.2, 1.4, 1.5 and 1.6 files keep their own version. The editor model is DMN 1.3, and the namespaces of the other versions map onto it for reading only.
- DMN 1.1 files are shown through a migration to DMN 1.3, and edits are still written into the 1.1 file as line patches. When the layout of an old file does not allow that, the edit is not saved and you choose: open the XML, or save the file as DMN 1.3.
- A file with content the model would drop (DMNDI styles, unknown elements of newer DMN versions) gets a note at the top that lists it. Edits are still saved as line patches; one that cannot be is refused with an explanation, never written halfway.
We tried this on 1,548 real DMN files from open-source engines, examples and the DMN TCK. 1,538 opened (the other 10 are not DMN, or use a prefix without a namespace). A changed table cell was saved as a line patch in 436 of the 565 files with a decision table, as a checked full write in 5, and refused with an explanation in 124 (122 of them DMN 1.1 files). In DMN 1.2 to 1.6 files, 305 of 307 cell edits were saved. A rename was saved in 1,375 of 1,444 files. No edit was lost and no file changed outside the edit.
- Decision tester: enter input values and evaluate a decision on your computer with a FEEL engine. See the result, the required decisions and, in each decision table, which rules matched and which fired under the hit policy (UNIQUE, FIRST, PRIORITY, ANY, COLLECT with SUM, MIN, MAX or COUNT, RULE ORDER, OUTPUT ORDER). Save test cases as JSON next to the file and rerun them all with one click. It gives the expected result in all 126 DMN TCK compliance level 2 tests and in 3,000 of 3,364 level 3 tests.
- Table lint: overlapping rules (with an example input both match), gaps (inputs no rule matches, with an example), rules that can never fire, hit policy problems, values outside the allowed list and FEEL that does not read. A Markdown report with line numbers, the Problems panel, and a JSON file for CI. Right-click a folder to lint every DMN file in it.
- Excel round trip: export every decision table to an XLSX workbook (one sheet per table) or one table to CSV for business users, then import the edited sheet back. Changed cells, new rows and removed rules go into the file as line patches you can undo.
The first use of each tool is free on this computer. After that, a click on the tool shows what Zovo Pro is and how to get it; nothing appears on its own. One key turns on Pro in every Zovo extension, for life.
Settings
dmnEditor.exportScale: pixel scale of PNG exports (default 2).
dmnEditor.showProTools: show the Pro tools in the Command Palette, the Explorer menu and the editor toolbar (default on).
dmnEditor.askForRating: ask once for a rating after two good days of use (default on).
dmnEditor.showSupportLinks: the small Rate, More free tools and Zovo Pro links under the editor (default on).
Privacy
No network requests, no telemetry, no account. The editor, the FEEL engine and the XLSX writer all run inside VS Code. The only links that open a web page are the ones you click (rating, Zovo Pro, the bpmn.io watermark).
Known limits
- DMN 1.4, 1.5 and 1.6 elements that DMN 1.3 does not have (conditional, filter, iterator and some list expressions) are kept in the file but are not shown or edited.
- The decision tester evaluates FEEL only; expressions in JUEL, JavaScript or Groovy (older engine files) show a clear error instead of a result.
- An Excel import changes cells and rules; to add or remove a column, change the table in the editor and export again.
License
MIT for this extension. The bundled dmn-js uses the bpmn.io license and other libraries use MIT, ISC or Apache-2.0; see THIRD-PARTY-NOTICES.md.
Made by Zovo. Questions and bugs: GitHub issues.
| |