Camunda Automation Platform 7.20.0-alpha2 Released

We are pleased to announce the next alpha release of Camunda Automation Runtime 7.20. This release features the following improvements:

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 see the list of known issues.

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

Additional operations for TaskService

Using TaskService from the Java API, users can perform various CRUD operations on Tasks as well as use some id-based operations to change state, e.g TaskService#setPriority.

If a client needs to change partially properties of a Task, the only solution available would be to use the Query API, fetch the Task, modify & persist it again using TaskService#save.

The above practice can lead to OptimisticLockingException if used by multiple clients at the same time and is also redundant (using save to make partial changes on Task, e.g changing the task’s name)

Now, the TaskService Java API is extended with the following new transactional operations as demonstrated in the example below:

taskService.setName(taskId, "newName");
taskService.setDescription(taskId, "newDescription");
taskService.setDueDate(taskId, new Date());
taskService.setFollowUpDate(taskId, new Date());

Dedicated retry configurations for clean-up jobs

In certain use cases, users of the engine might find it convenient to configure the history clean-up jobs with a dedicated retry configuration to the rest.

An example would be operation engineers that want to turn off retries for history clean-up jobs during some expected temporary disruptions, e.g network failure and db-timeouts.

As a result, this feature enables users to configure the newly added property historyCleanupDefaultNumberOfRetries through ProcessEngineConfiguration with a positive integer number to customize the max retries number for history cleanup jobs separately.

If this property is not configured, clean-up job retry-configuration will be controlled by the global setting which is used by all the jobs, defaultNumberOfRetries.

Security Notice 91: Path Traversal Vulnerability

This alpha release and the patches 7.19.3, 7.18.9, and 7.17.14 fix a path traversal vulnerability in the Camunda 7 web applications (Cockpit, Tasklist, Admin). We strongly recommend updating Camunda to a version with a fix if your setup is affected. You can find all details in security notice 91.

Future releases

Share Your Thoughts with Us!

Your feedback is really important to us, so please download Camunda Automation Platform 7.20.0-alpha2, 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 issue tracker.