Join our largest event of the year | CamundaCon 2022 October 5-6

Icon Close
Register

We are excited to announce the release of Camunda Modeler v4.0.0. This release introduces significant changes to the DMN editor, overhauls deployments from the Camunda Modeler, and adds error tracking.

Download the latest release and start modeling right away.

Ready for DMN 1.3

DMN 1.3 is the upcoming version of the DMN standard. Compared to DMN 1.1 version 1.3 of the standard ships with a number of improvements, most importantly, a diagram interchange that allows graphical information to be exchanged across vendors.
The app now exports DMN 1.3 and uses the standardized diagram interchange when doing so. You can open older DMN 1.1 or DMN 1.2 files; however, those will be migrated to DMN 1.3 on save.

Camunda BPM Compatibility with DMN 1.3

DMN 1.3 diagrams created with Camunda Modeler v4.0.0 are compatible with the following versions of Camunda BPM: 7.13.0, 7.12.4, 7.11.11, 7.10.17 and above. Make sure to update your Camunda engine accordingly if you are using DMN 1.3.

Simplified DMN Modeling

Besides adopting the latest DMN standard, we are continuously investing in our DMN modeler to make it an even better tool for decision modeling. With the introduction of automatic placement of BPMN elements in Camunda Modeler v1.12.0, creating well laid out diagrams became both easier and faster. This release finally brings this feature to the DRD editor of the Camunda Modeler.

Encouraging Best Practices…

When building the new modeling experience, we incorporated the latest results of our ongoing user research. The most significant one is that DRD diagrams are modeled from top to bottom, resulting in a tree structure. In contrast, BPMN diagrams are modeled from left to right. Now, diagrams in both toolkits are automatically laid out accordingly.

New DRD top-down editing modeling

Following the top to bottom layout, created connections will connect newly created elements to already existing ones. Furthermore, the layout of information requirements has been adjusted to support the tree structure resulting from the top to bottom approach.

…Without Enforcing Them

Even though we encourage you to layout your decision requirement diagrams top to bottom, you can still create diagrams any way you want. If you prefer modeling left-to-right, simply drag the elements from the context pad instead of clicking.

Overhauled Deployments from the Camunda Modeler

Deploying diagrams from the Camunda Modeler has been an integral feature since its introduction. With v4.0.0, we have completely overhauled the UX of deployments. This marks the first step in streamlining the look and feel of the Camunda Modeler.

Overhauled deployments UI

Error Tracking

Starting with this release, the Camunda Modeler is able to track errors that might occur. Knowing about these errors will help us build a more stable modeling application. To enable error tracking check the Enable Error Reports option in the privacy preferences found under Help > Privacy Preferences.

Enable error reports through privacy settings

If you want to learn more about what kind of information we collect and why we collect it, read our Privacy Policy.

Last but not least

As a part of the Camunda rebranding, we say goodbye to our old Camunda Modeler icon and introduce a fresh new icon. You may see this icon in your taskbar, app launch menu, etc.

New Camunda Modeler icon

Looking Forward

Read the changelog to learn about all the features, bug fixes, and numerous additional improvements that made it into this release. Download the new modeler, give it a try, and, most importantly, give us feedback.

Did we miss anything? Did you spot a bug, or would you like to suggest an improvement? Reach out to us via our forums, tweet us @Camunda or file issues you found in the Camunda Modeler issue tracker.

Stay tuned for future updates.

< Back
  • Feel Example Flow in Camunda 8

    FEEL more confident transforming data

    FEEL (Friendly Enough Expression Language) was created by the Object Management Group (OMG) “as part of the DMN standard”. Its goal is to be easy to understand, and at the same time, be full-featured enough to handle decision tables and literal expressions. When business and IT often work together on complex projects, writing expressions in a (relatively) accessible way reduces miscommunications and helps align teams. Camunda uses FEEL to map and transform business process data dynamically. For example, a loan application process pulls a credit score from an API call into a decision table. The decision table automates the next step of the process depending on the rules in the table. The data from the decision automation can then be...

    Read more
  • Workflow diagram and pattern examples using BPMN...

    There are multiple angles to look at workflows one of which is patterns. The Workflow Patterns initiative differentiates between control, data, and resource perspectives. They are not just focusing on the modeling language as such but have workflow systems in mind too. It’s valuable to have a closer look at those patterns and discuss which parts of it can be shown and even automated in BPMN, and which parts are taken care of in the technical implementation. I have seen BPMN diagrams that try to include every aspect in the diagram itself. This often leads to overloaded BPMN models with a lack of clear transparency of the business flow. Therefore, it is important to focus on all aspects of workflow...

    Read more
  • Title slide that reads "Camunda Automation Platform 7.18.0-alpha5 Released"

    Camunda Automation Platform 7.18.0-alpha5 Released

    We are pleased to announce the next alpha release of Camunda Platform Runtime 7.18. This release features the following improvements: Logging: Engine name parameter in mapped diagnostic context Exception Error Codes now available in the External Task Clients IBM WebSphere Application Server Liberty support New Supported Environments 7 Bug Fixes You can download Camunda for free or run it with Docker. For a complete list of all improvements, take a look at the release notes. Please also see the list of known issues. If you want to dig in deeper, you can find the source code on GitHub. Logging: Engine Name Parameter in Mapped Diagnostic Context As an addition to the already present list of parameters for the logging context,...

    Read more

Ready to get started?

Still have questions?