Camunda BPM 7.10.0-alpha3 is here and the highlights are:
- Extending “Handle External Task BPMN Error”
- Complete Hierarchical History Cleanup
- 9 Bug Fixes
Together with the third alpha of platform, we released also:
- Spring Boot Starter 3.1.0-alpha1 – release notes
- Node.js external task client 1.1.0-alpha1 for non-Java developers – release notes
- Java external task client 1.1.0-alpha1 – can be embedded in Java applications, release notes
You can Download Camunda for free (click on Preview Release) or Run it with Docker.
If you are interested, you can see the complete release notes
and the list of known issues.
If you want to dig in deeper, you can find the source code on GitHub.
Extending “Handle External Task BPMN Error”
During process execution a business error can occur. In the world of External tasks, the worker can report a BPMN error to the process engine by using ExternalTaskService#handleBpmnError (or the respective Rest endpoint). The method can only be invoked by the worker possessing the most recent lock for a task. The additional data which can be passed now when reporting such kind of BPMN errors are error message and variables which can be used later in the process flow.
Here is an example how this can be achieved via Java API:
externalTaskService.handleBpmnError(externalTaskId, "aWorker", "ERROR-SPEC-10", "anErrorMessage", variables);The REST API call would look like:
POST /external-task/externalTaskId/bpmnError
Request Body:
{
"workerId": "aWorker",
"errorCode": "ERROR-SPEC-10",
"errorMessage": "anErrorMessage",
"variables": {
"aVariable" : {
"value" : "aStringValue",
"type": "String"
},
"anotherVariable" : {
"value" : true,
"type": "Boolean"
}
}
}Complete Hierarchical History Cleanup
This alpha release adds upon the Hierarchical History Cleanup feature introduced in the second alpha. Previously, the new mechanism was only aware of the hierarchical structure of Historic Process Instances.
With this release, the mechanism is expanded to include Historic Decision Instances, covering both cases, when decision instances are evaluated individually and as part of a BPMN process. In the former, the removal time of the root decision instance is adopted by all the child decision instances, and in the latter, the root process instance removal time dictates the removal time of it’s process and decision instance descendants (read more here).
Furthermore, the Cleanable Process and Decision Instance Reports have been adjusted to report the correct number of cleanable instances when the new mechanism is used.
Finally, the attributes: removalTime and rootProcessInstanceId have been made available through the Historic Process Instance and Historic Decision Instance endpoints of the Rest API.
Next Steps…
As usual the fourth alpha release is scheduled for the end of the next month and we are already working on it.
Among other things, we are working on the following topics, which are planned to be released in one of the next alpha releases:
- Support of latest WildFly version
- bpmn-js plugins are available in Cockpit
To get a complete overview of already implemented and planned features, please take a look at the roadmap for the bigger list of planned features.
The minor release of Camunda BPM 7.10 is coming this fall (November 30, 2018).
Your Feedback Is Highly Appreciated!
With every release we constantly strive to improve Camunda BPM. To make this possible, we rely on your feedback.
Feel free to share your ideas and suggestions with us.
You can contact us by writing a post in the forum.
