We are pleased to announce the third alpha release of Camunda Platform Runtime 7.17. This release features the following improvements:

You can download Camunda Platform Runtime 7.17.0 for free 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.

Camunda Run improvements

We are constantly working to get the Camunda Run distro closer to what is offered from our other Camunda distros. The 7.17.0-alpha3 release provides a start to the improvements of the Camunda Run distro.

Groovy scripting engine included

A large part of the Camunda community utilizes the Groovy scripting engine that is shipped by default with our other distros. As a result, the Camunda Run distro now ships with the Groovy scripting engine as well, in the form of the groovy-all-2.4.13.jar located in the {RUN_HOME}/configuration/userlib/ directory. Your BPMN process Groovy scripts can run out-of-the-box with Camunda Run now!

Camunda Connect plugin included

The Camunda Connect plugin is another feature that is included by default with our distros, except for Camunda Run. With this release, we fixed that. You can now use connectors in Camunda Run just like with any other Camunda distro.

Better control over the CORS filter

Cross-Origin Resource Sharing (CORS) has been available for Camunda Run right from the start. CORS allows users to interact with the Camunda process engine from multiple origins via the REST API. However, the CORS configuration in Camunda Run so far only allowed specifying the allowed origins. We have now expanded this configuration with properties like allowed-headers, allow-credentials, and many others. Have a look at the Camunda Run CORS documentation for more details.

Share your thoughts with us

Your feedback is really important to us, so please download Camunda Platform Runtime 7.17.0-alpha3, 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.