We’re pleased to announce the next alpha release of Camunda Automation Platform 7.17.0. This release features the following improvements:

  • Cockpit: CSV Export for Process Instances
  • Admin: SYSTEM Permissions
  • Camunda Run improvements
  • 13 Bug Fixes

You can download Camunda for free or run it with Docker.

For a complete list of all improvements, take a look at the release notes. Please also browse the list of known issues.

If you want to dig in deeper, you can find the source code on GitHub.

Cockpit: CSV Export for Process Instances

This feature is only available in the Enterprise Edition of Camunda Automation Platform. We invite you to test it out with a free trial.

Sometimes incidents make it necessary for the Operations Engineer to intervene manually. However, these incidents might not always be solvable from Cockpit if other services or systems are involved. 

This release introduces a new feature to Cockpit to export affected process instances and their process variable values as CSV spreadsheets. The export feature helps to communicate efficiently with other system owners.

We extended the process instances search on the processes dashboard for this feature. 

You can read more about this feature in our documentation.

Admin: SYSTEM Permissions

In our 7.17.0-alpha4 release blog post, we announced new permissions for operations engineers. With this release, you can now set these permissions in Admin. Please check out our documentation for a complete list of the resources and features available to users with system permissions.

Camunda Run Improvements

We are providing even more improvements to the Camunda Run distribution. With the 7.17.0-alpha5 release, we added improvements to the Camunda Run start scripts, as well as added better process engine plugin support for Camunda Run.

Camunda Run start & shutdown scripts

Camunda Run now provides start and shutdown scripts. We made a small change to the behavior of these start scripts. If you don’t provide any additional arguments to the start script, it’ll start Camunda Run as a detached process with the web apps, REST API, Swagger UI, and example modules enabled. 

You can then use the new shutdown.sh or shutdown.bat script to stop Camunda Run.

Finally, you can still control what Camunda Run modules are enabled by passing the appropriate script arguments to the start scripts. In that case, Camunda Run will start in the foreground.

Registering process engine plugins in Camunda Run

We developed Camunda Run for non-Java users in mind. However, registering process engine plugins still required some Java knowledge.

With this latest release, you can now register a process engine plugin with Camunda Platform Run in three steps

  1. Add your-plugin.jar binary in the ${RUN_HOME}/configuration/userlib/ directory.
  2. Find the process engine plugin canonical class name and any configuration parameters it might have. The canonical class name should look something like your.process.engine.Plugin.
  3. Add the following to your YAML configuration file:
camunda.bpm.run.process-engine-plugins:
  - plugin-class: your.process.engine.Plugin
    plugin-parameters:
      pluginParameterOne: valueOne
      pluginParameterTwo: true

That is all you’ll need to do. You can find more details in the Camunda Run process engine plugin registration section of our documentation.

Share Your Thoughts with Us!

Your feedback is really important to us, so please download Camunda Automation Platform 7.17.0-alpha5, try it out, and let us know what you think about it.

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

Ready to get started?

Still have questions?