Sebastian Menski

The Zeebe team is pleased to announce the Zeebe 0.11.0 release, which includes: Snapshot replication for fast failover An updated default output mapping for task and workflow instance payloads for simpler workflow creation Easier access to deployment events, including a list of all workflows deployed to Zeebe Accessing and setting the payload of workflow or job as generic map or POJO

Update: On Monday, June 11, the Zeebe team released version 0.10.1 (download and changelog available here), a patch that fixes an issue with stream processing, and also released a 0.10.1 update for zbctl, the Zeebe command line interface. The Zeebe team is pleased to announce the Zeebe 0.10.0 release, which includes:

The Zeebe team is pleased to announce the Zeebe 0.9.0 release. In this post, we’ll provide a brief overview of release highlights along with resources to help you get started.

Today we release the next alpha release of camunda BPM platform. The highlights of this release are: CMMN Listener support Embedded Forms in Tasklist JSON support in Spin JSON to Java mapping with Spin Simple REST HTTP Connector See complete release notes in Jira.   Download camunda BPM 7.2.0-alpha4 now. Add Listeners to your CMMN Case Definitions As the CMMN support of our platform steadily increases we started to add features known from our BPMN implementation. With this alpha release you can add camunda:caseExecutionListener to plan items and camunda:taskListener to human tasks: Case execution listener can be added for the following state transitions: close, complete, create, disable, enable, exit, manualStart, occur, parentResume, parentSuspend, parentTerminate, reactivate, re-enable, resume, start, suspend and...

As part of our scripting improvements we also addressed templating as a new feature of camunda BPM. With the new camunda BPM 7.2.0-alpha3 release it is now also possible to use FreeMarker or Apache Velocity templates inside your BPMN process. We integrated this template engines as JSR 223 compatible scripting engines. Therefore we create small wrappers for these template engines in our camunda-template-engines-jsr223 project. This has the advantage that we do not need new extension elements or attributes for the BPMN xml. Instead a template can be used everywhere a script can be used. This is especially useful for script tasks and input output mappings. If the template engine JSR 223 wrapper is part of your classpath you can use the name of...

With the last camunda BPM 7.2.0-alpha3 release we heavily extended the scripting support of the camunda BPM platform. We started to improve scripting support with the 7.2.0-alpha1 release and now we think we are done. It is now your turn to start using the different scripting languages and help us to polish this feature for our final release. To get an detailed overview of the scripting support please visit our user guide.   Where can I use scripts? Everywhere but to be more specific you can use scripts as: Script tasks (of course) Execution listener Task listener Condition of sequence flows Input output mapping (added in 7.2.0-alpha2) The implementation of the scripting support in camunda BPM is designed to be independent...

As already mentioned in our last alpha release blog post we are currently working on a BPMN model API to parse, create, edit and write BPMN 2.0 XML files. Last Friday we opened our GitHub repository and have since then created a userguide and some quickstarts.   The BPMN model API offers you a simple and straightforward way to interact with an BPMN 2.0 model. It enables you to gather information from an existing model, edit and extend them. Of course you can also create completely new ones. Technically the model API is based on a DOM layer which is accessed and manipulated by a general XML API developed by us. On top of this, the BPMN model API encapsulates the interaction...