camunda Modeler 2.6.0 released: Field Injection, properties panel and bug fixes

The camunda BPM team is happy to announce the release of camunda Modeler 2.6.0. This release contains updates on the properties panel, a new properties tab, bpmn 2.0 alignment and bug fixes.
Find a complete list of issues solved in this release in JIRA.

This release covers Eclipse  Eclipse Kepler and Juno/Indigo as well as the camunda Modeler Standalone.

The new features and bug fixes where mainly developed by Kristin!

Asynchronous Continuation on Parallel Gateways
As the parallel gateway is a synchronizing gateway, it is subject to optimistic locking. The new feature allows you to use the engines JobExecutor Retry mechanism for resolving optimistic locking conflicts without impacting the preceding tasks.

Field Injection
We introduced a new tab to configure field injections for the following elements: Service Task, Business Rule Task, Send Task, End Message Event and Throwing Message Event.
Find more information in our docs.

bpmn 2.0 alignment
The new modeler offers you the possibility to edit expressions without the xsi:type attribute. As the modeler is focused on executable processes, we didn’t support this in the past. This caused exceptions at the model import, mainly when used together with business focused design tools.

Download the prepackaged modeler, update your Eclipse plugin or check out the standalone version NOW! Give us feedback in our our forums or on twitter.

Happy modeling!!! 

  • 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 You should be familiar with Kubernetes and Helm to follow along and will learn about and 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 ( / 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. 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