The Zeebe team is happy to announce the 0.17 release. You can download Zeebe 0.17 from the release page on GitHub.

In this post, we’ll discuss some of the highlights from the release and share other project updates.

Questions? Feedback? The Community page on our website lists a number of ways that you can get in touch with us. We monitor and respond to messages on the Slack group and user forum on an ongoing basis, and we’d love to hear from you.

Zeebe 0.17 Release Notes

In Zeebe 0.16, we completed a migration from payloads to variables and scopes for workflow instance dataflow.

Early adopters shared the feedback that variables would provide users with more flexibility and would be easier to reason about than payloads. Because payloads were attached to workflow instance tokens, whenever there was hierarchical or parallel execution (such as an embedded subprocess or parallel gateway), it was difficult to access the payload from a different branch. Additionally, it wasn’t intuitive to the user how to handle the merging of 2 or more payloads, with lots of manual mapping required.

These improvements to one of Zeebe’s fundamental concepts means that 0.17.0 introduces a handful of API breaking changes, most of which related to this payloads to variables migration. Here are a few of the details:

  • API methods that were previously called payload are now called variables. This update affects the Zeebe CLI, too.
  • Expressions are now written without $. So, for example, $.foo would now be written as foo. This affects sequence flows out of the Exclusive Gateway in the Zeebe Modeler and also Input/Output variable mappings and Message Correlation Key.
  • For the sake of consistency and clarity, many Maven artifacts were renamed to be prefixed with zeebe instead of zb.
  • In job workers, bufferSize has been changed to the more intuitive maxJobsActive.

Additionally, the exporter API was moved to the package io.zeebe.exporter.api. Previously, it was io.zeebe.exporter.

If you have any questions about these changes, please let us know via the Zeebe user forum.

Zeebe Q2-2019 Roadmap

We’re excited to share that we’ve updated the Roadmap page on to include our planned work for Q2-2019. There are three main areas the team will be focused on this coming quarter:

  • Make it possible for a Zeebe cluster to run forever: To enable a long-running cluster, Zeebe will need to delete data no longer required for execution of active workflow instances.
  • Ensure that a Zeebe cluster is fault tolerant: To prepare Zeebe for production-readiness, we need to harden and extensively test its fault tolerance characteristics.
  • Provide user guidelines for Zeebe production usage: To ensure users can confidently run Zeebe in production, we’ll improve the documentation and add new entries.

The top priorities in the near-term are clustering and stability. Q2 represents our final push as we get Zeebe to production readiness, and we’re on track for a first production-ready release at the end of Q2 / the start of Q3.

Recent Zeebe Blog Posts

In case you missed it, we published 2 Zeebe blog posts in the past month. Check them out if you haven’t already!

That’s all for now! Please get in touch with questions or comments.

  • Camunda Platform 8.1 Released – What’s New

    We’re extremely excited to announce the release of Camunda Platform 8.1.  In this post, we will go into the highlights of this release including Web Modeler, Connectors, Zeebe, Operate, Optimize, and more. Here’s the highlights of what’s included in this release: Easier Installation and maintenance for Camunda Platform Self-managed Hot backups for Self-Managed Token-Based authentication Modeler updates Process Templates FEEL Expression Editor Inline Annotations Changes to Camunda forms Connectors updates Workflow engine updates Operate updates Optimize updates Let’s get started! Easier installation and maintenance for Camunda Platform Self-Managed Improved Guides and Support for OpenShift and Amazon EKS (AWS) With this release, we are introducing official support for deploying and running Camunda Platform 8 Self-Managed on OpenShift and Amazon EKS (AWS)....

    Read more
  • Camunda Platform 7.18 Released – What’s New

    We’re extremely excited to announce the release of Camunda Platform 7.18 Here are some of the highlights: Cockpit: Improved instance selection to avoid unintended batch operations Cockpit: Easier navigation of high batch operation volumes MDC logging features Camunda Forms in Tasklist: Populate select options via process data Exception error codes Filter and order tasks by last updated WebSphere Liberty New and retired supported environments You can download Camunda Platform or run it with Docker. For a complete list of the changes, please check out the release notes. For patched security vulnerabilities, see our security notices. If you want to dig deeper, check out the source code on GitHub. Cockpit: Improved instance selection to avoid unintended batch operations Previously, when performing...

    Read more
  • Increase your resilience with new regions in...

    We’re excited to announce new regions for Camunda Platform 8 SaaS that further strengthen the resilience, performance, and data requirements for our SaaS customers. Enterprise customers can now choose to create their clusters in a number of regions including Europe West, US Central, US East, and the most recent addition, Australia South East. This provides multiple benefits, such as increasing availability, allowing to set up fail-safes, adhering to regulatory requirements for regional data storage, and reduced latency due to closer physical proximity. Resilience and redundancy in technology are important for all modern organizations and are top of mind for many. Across industries, organizations need a solution that scales effectively and is resilient to provide a good base for process orchestration....

    Read more

Ready to get started?

Still have questions?