Skip to content
44

Features ​

Everything the modeler does, in the order you work: model, simulate, code, review and deploy. The pages describe VS Code. The desktop app runs the same extension, and the IntelliJ plugin shares the BPMN modeler (it does not edit DMN or forms).

Model ​

  • Editor modes: switch an editor between View (read-only), Design (engine-neutral) and Implement (full Camunda modeler).
  • Append menu: add the next element from one searchable popup with BPMN elements and element templates.
  • Flow navigation: move along sequence flows with Tab, Shift+Tab and Enter.
  • IDs from names: rename IDs like Activity_0x1y2z3 to serviceTask_checkStock from the element names, for one element or the whole diagram in one undo step.
  • Element templates: browse, preview and apply Camunda element templates.
  • Element template editor: build Camunda 7 and 8 templates in a form, with the JSON beside it and a live preview.
  • Template marketplace: load templates from shared GitHub or GitLab repositories or local folders.
  • BPMN plugins: extend the BPMN editor with bpmn-js plugins from your repository, including Camunda Modeler plugins, once you allow them.
  • Add-ons: see the plugins, rule packages, element templates and marketplaces of your workspace, allow or revoke code and turn templates on or off.
  • Forms: edit Camunda Forms (.form) and test them in a preview.
  • Language support: switch the modeler UI language.

Simulate and check ​

  • Token simulation: send tokens through the process to see which paths it takes, without an engine.
  • Linting: check the diagram live with bpmnlint and your own rules.

Code ​

  • Jump to code and models: open the source file behind a task, the model a call activity or business rule task refers to, or reuse messages and signals from other models.
  • Inline scripts: edit script tasks and listener scripts in a real editor tab.

Review and deploy ​

  • BPMN diff: compare two versions of a diagram side by side, with changes highlighted.
  • BPMN merge (alpha): resolve a Git conflict in a .bpmn file per element, then build the result into the file and compare it with both sides.
  • DMN diff: compare two versions of a decision model side by side, down to the cells of its decision tables.
  • Deployment: deploy BPMN and DMN files to Camunda 7 or Camunda 8 and start process instances.