Camunda BPM Runtime 7.14.0-alpha1 Released

We are happy to share the first alpha release of Camunda BPM 7.14 with you! As a bonus, we include an alpha release of the Java External Task client.

This release features the following improvements:

  • Sending Telemetry
  • Java External Task Client 1.4.0-alpha1
  • 14 Bug Fixes

You can Download Camunda for free (click on Preview Release) 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.

Sending Telemetry

With this alpha, we are introducing an option to send telemetry data to Camunda. The goal for this initiative is to offer you a great and stable user experience when using Camunda. The insights into common environment setups and product usage patterns we can gather will help us to make product development decisions to your benefit. A list to the type of information we can collect can be found here. By default, the feature it disabled and has to be explicitly enabled either with process engine configuration option when setting up your Camunda instance or via Java/REST API later on whenever you decide to switch the option on or off. Please note the feature is still under development. Only if sending telemetry is enabled, the engine is going to send every 24 hours or upon engine stop the following data:

  • process engine installation id
  • process engine version and edition (community or enterprise)
  • database vendor and version

Java External Task Client 1.4.0-alpha1

This first 7.14 alpha release is accompanied by an alpha release of the Java External Task client, which comes with two new features.

Fetch local variables only

When fetching external tasks, all variables visible to the external task are attached to the response and submitted to the external task worker. In some cases, users want to have more control over which of these variables should be included. The concept of variable scopes and visibility helps to limit access to only the necessary ones, and the REST API provides a flag (localVariables) to include only local variables and exclude global variables.

The external task client was extended to make use of this. Now it is possible to limit the returned variables to local variables by using a new configuration option:


Fetch extension properties

Extension properties are custom key-value-properties that can be set on any BPMN activity, e.g., with the Camunda Modeler using the Extension tab in the Properties Panel.

For external tasks, we now support fetching these properties via the REST API (using the includeExtensionProperties flag) and the external task using a new configuration option:


Share Your Thoughts with Us!

Your feedback is really important to us, so please download Camunda BPM 7.14.0-alpha1, try it out, and let us know what you think about it.

You can contact us in the forum, send a tweet to @Camunda, or file a bug in our ticket system.

  • Spring Boot Starter for the External Task...

    We are happy to announce that Camunda Platform Runtime 7.15 will provide a Spring Boot Starter for the External Task Client. It allows you to implement Service Tasks decoupled from the Process Engine using Spring Boot. In seconds, you can build an executable JAR that can run almost anywhere. In 2018, Camunda released the first version of the External Task Client. Since then, our community member Oliver Steinhauer developed a Starter that combines the External Task Client with Spring Boot. With the 7.15 release, we will add the former Community Extension to the official Camunda Stack and will maintain it as part of future product releases. Let’s look at the following example to get a better understanding of the Spring...

    Read more
  • The Zeebe Community Welcomes Camunda Cloud

    The Zeebe Community Welcomes Camunda Cloud!

    The Rise of Camunda Cloud Whether you’re a current Camunda Platform user, interested in our open source software, or simply poking around our blog as a result of a tweet you saw from someone in our community, you may have noticed an increase in the number of times you’re seeing words like Camunda Cloud, SaaS, or Zeebe pop up over the past few months. As you may know, we first released Zeebe, the source-available, community-supported workflow engine, in 2017 (read the history of Zeebe in our CEO’s words). Since then, in addition to creating an amazing enterprise product with Camunda Platform, we’ve been listening to your feedback on Zeebe as well as Camunda Cloud, working hard to build a SaaS...

    Read more
  • Camunda Cloud 1.0.0-alpha2 Released

    We’re excited to announce the release of Camunda Cloud 1.0.0-alpha2, which includes Zeebe 1.0.0-alpha2 Operate 1.0.0-alpha2 Tasklist 1.0.0-alpha2 Updates in Cloud Console How to get it In this post, we’ll highlight some of the new capabilities introduced in these alpha releases. Zeebe 1.0.0-alpha2 The Zeebe team continued its work on getting ready for the 1.0 release and improving many internal components of the workflow engine and its underlying infrastructure. Nevertheless, the alpha2 release already provides an improvement for users of the Java client. The Java job worker implementation now offers a back-off mechanism if the Zeebe service is not available. Before the job worker continues to poll the unavailable service continuously, the job worker will apply an exponential back-off strategy...

    Read more