Camunda BPM Runtime 7.14.0-alpha1 Released

By
  • Blog
  • >
  • Camunda BPM Runtime 7.14.0-alpha1 Released
TOPICS

30 Day Free Trial

Bring together legacy systems, RPA bots, microservices and more with Camunda

Sign Up for Camunda Content

Get the latest on Camunda features, events, top trends, and more.

TRENDING CONTENT

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:

  externalTaskClient.subscribe("topicName").localVariables(true).open();

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:

  externalTaskClient.subscribe("topicName").includeExtensionProperties(true).open();

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.

Try All Features of Camunda

Related Content

We're streamlining Camunda product APIs, working towards a single REST API for many components, simplifying the learning curve and making installation easier.
Learn about our approach to migration from Camunda 7 to Camunda 8, and how we can help you achieve it as quickly and effectively as possible.
We've been working hard to reduce the job activation latency in Zeebe. Read on to take a peek under the hood at how we went about it and then verified success.