We are pleased to announce the next alpha release of Camunda Automation Runtime 7.21. This release features the following improvements:
- Set local variables in the triggered execution by message correlation
- Heatmap statistics 5 minute and 1 hour filters (Enterprise)
- Display BPMN process documentation field in Cockpit
- Add SkipIoMapping Support to BatchDeletion Operation
- 4 Bug Fixes
If you want to dig in deeper, you can find the source code on GitHub.
When triggering a message correlation, you can pass variables to be injected into the execution waiting on the message. However, there are some use cases when you want to pass variables to the newly triggered execution by the message correlation instead of the existing one.
Let’s have a look at the following process model:
When variables are set for the existing execution, they will be stored within the process instance scope, which might lead to racing conditions and inconsistent outcomes when multiple message correlations are triggered. (Note, the asynchronous continuation is enabled for the message event, a job will be created after the message correlation is triggered. If several correlations are triggered, the variable will be overwritten, and multiple jobs will be created, which might lead to inconsistent or wrong outcomes.)
With this alpha, you can trigger the following correlation:
outsideTemp variable will be set to the newly created execution by the message correlation. That way, the outcome of the getaway will be consistent with the message correlation input.
Camunda Cockpit’s process history heatmap statistics dropdown now offers two new filter options. The new Last 1 hour and Last 5 minutes options make understanding the system’s current condition easier.
This feature is only available in the Enterprise Edition of the Camunda Platform Runtime. Test it out with a Free Trial
The root documentation of the BPMN process is now also displayed in the Camunda Cockpit under the Documentation tab.
Similar to the Delete Process Instance operation, the users now will have the option to Skip IO Mappings when deleting processes in a Batch.
The feature will be useful for users who would like to be able to skipIOMappings when deleting processes in a batch. The individual deletions performed will not fail in case any of the selected processes contain variable declarations that exist in nested subprocesses.
The new option can be found under Cockpit | Batches | Delete Running Process Instances, as depicted in the following screenshot:
Your feedback is really important to us, so please download Camunda Automation Platform 7.21.0-alpha2, try it out, and let us know what you think about it.