camunda Modeler 2.4.0 released: Design / Source View and enhanced file handling

Today we are happy to announce the new release of our camunda Modeler. Beside a couple of bug fixes this version adds a Source / Design view switch and an enhanced file handling.


Checkout the complete list of issues solved in this release. And of course, try out the new modeler and tell us what you think via our forums or on twitter.



The new features were initially developed for camunda Modeler Standalone and are now incorporated into the main modeler codebase. Thanks to Nico’s  work we could align the development of both projects.

Source/Design View
A feature that allows you to switch from the design perspective to the underlying BPMN 2.0 xml. Use the source view to see what is behind the graphical representation or to edit custom attributes. 







Enhanced file handling
Open and edit files outside of your eclipse workspace by drag and drop them directly into the editor tab.

Furthermore you can work on a diagram in your favorite text editor while the same file is opened in eclipse. Changes will be recognized by Eclipse so that you will not run into a version conflict.

The new release is available for Eclipse Kepler and Juno/Indigo.

We are hiring!

  • Orchestrating Cloud Events with Zeebe

    Disclaimer: This blog post is about Cloud-Native software, containers, Cloud Events, and Workflows. It describes a concrete example that you can run yourself using Kubernetes, Helm, and Zeebe.io. You should be familiar with Kubernetes and Helm to follow along and will learn about zeebe.io and cloudevents.io on your way. While working with Kubernetes the chances are quite high that you’ll find services written in different languages and using different technologies stacks. CloudEvents (cloudevents.io / CNCF spec) was born to enable these systems to exchange information by describing their events in a standard way, no matter which transports these services are using (HTTP, Messaging AMPQ/JMS, Protobuf, etc).  In such scenarios, where you have events being produced and consumed by different systems, there are common requirements that start to arise when...

    Read more
  • How we automatically keep our Documentation Screenshots...

    When you open the Camunda User Guide, you’ll see that there are many screenshots explaining the different functions and options the product offers. We hope that you, as a user, find those screenshots helpful. But for us as developers, creating and keeping those screenshots up to date has always been a pain. https://unsplash.com/photos/dDppsuM_UpE At the time of writing, the user guide for Camunda Optimize contained 94 screenshots. And with every release we add more functionality, which means the number of screenshots continuously grows. When we change the look of buttons or add a new section to the header, we need to update every screenshot that has a button or header in it. In practice, this meant we were manually recreating every...

    Read more
  • Git push to deploy to Camunda Cloud

    Using the Zeebe Action for GitHub, you can automate your GitHub repo to deploy BPMN models to Camunda Cloud when you push to a specific branch. In this quick tutorial, I show you how to configure your GitHub repo to deploy all BPMN models in the bpmn directory of your repo on a push to master. If you don’t have a Camunda Cloud account yet, you can join the public beta to get one. Create a client in Camunda Cloud Go into your Zeebe cluster in the Camunda Cloud console, and create a new client. You might want to name it “GitHub-Automation” so you know what it is for. Copy the “Connection Info” block by clicking the copy icon in the lower right-hand...

    Read more