We’re pleased to announce the first alpha release of Camunda Automation Platform 7.18.0. This release features the following improvements:
- Access to process instance comments via REST API
- Cockpit: Displayed removal time for process and decision instances
- Support for Quarkus 2.8.2
- Groovy script engine updates
Get Process Instance Comments via REST API
Since the early days when Camunda was using Java APIs, users have been able to add comments to tasks. However, this feature was never available for a REST API – but now it is with this alpha release. Thanks to a contribution from Dimitrios Michail from the Harokopio University of Athens, users can now retrieve all task comments for a given process instance via REST API.
Cockpit: Displayed Removal Time for Process and Decision Instances
The instance removal time is a key element of the History Cleanup feature used to remove historical process data. Before this release, the instance removal time was only available to users with direct access to the production database. With Camunda Automation Platform 7.18.0-alpha1, the removal time is now displayed in both the process instance history and decision instance views of Cockpit, making it easier and quicker for all relevant stakeholders to access.
Support for Quarkus 2.8.2
Camunda Platform 7.18.0-alpha1 features support for the latest version of Quarkus. You can use Quarkus 2.8.2 together with the Camunda Automation Platform Quarkus Extension.
Make sure to check out the Quarkus migration guides between 2.1 and 2.8 for further details on what’s new.
Groovy Script Engine Updates
Camunda Platform 7 provides the Groovy script engine with pre-packaged distributions by default. With Camunda Automation Platform 7.18.0-alpha1, we bumped Groovy to version 2.4.21. We also decided to move away from the groovy-all.jar since newer Groovy versions no longer include it. Instead, the following Groovy modules are included in our pre-packaged distributions:
The Groovy modules, groovy-2.4.21.jar and groovy-jsr223-2.4.21.jar, are the only ones required for the correct operation of the Groovy script engine. However, we decided to provide additional useful Groovy modules to make the migration away from the groovy-all.jar less painful.
This change lays the groundwork for future Groovy updates that would have been more difficult if we continued using the groovy-all.jar. Using separate Groovy modules also gives you, the Camunda user, more freedom and flexibility in deciding what parts of Groovy you want to include in your Camunda setup.
Share Your Thoughts with Us!
Your feedback is really important to us, so please download Camunda Platform Runtime 7.18.0-alpha1, try it out, and let us know what you think.
You can contact us in the forum, send a tweet to @Camunda, or file a bug in our ticket system.