Camunda BPM platform 7.9.0-alpha4 is here and the highlights are:
- External Task Notifications for Long Polling
- Version Tag Binding in Business Rule Task and Call Activity
- Asynchronous Modification of a Single Process Instance
- History Cleanup in Multiple Threads
- Camunda Wildfly Swarm Community Extension
- Integration of the Latest Version of dmn-js
- 20 Fixes
If you want to dig in deeper, you can find the source code on GitHub.
External Task Notifications for Long Polling
With the preceding Camunda 7.9.0-alpha2 release, we introduced a long polling Fetch & Lock handler for External Tasks. This reduces the amount of requests and a more efficient use of client, and server side resources.
However, it is possible that a new External Task has been created before the long polling timer runs out. Till now, the clients were not notified about this. This release introduces ExternalTask notifications for the long polling Fetch & Lock handler. Thereby, the handler is immediately notified after a new External Task is created. Then, the handler interrupts the suspension periods and attempts to respond with the new External Task to some of the pending client requests.
Version Tag Binding in Business Rule Task and Call Activity
Version Tag is a useful feature if you want to maintain customized versioning of processes. This alpha release extends the usage of the version tag with two new bindings: * Decision to evaluate in a business rule task - learn more * Process in a call activity - learn more
Asynchronous Modification of a Single Process Instance
Process instance modification allows to flexibly start an activity again or cancel a running activity. Within this alpha release it is possible to execute a modification of single process instance asynchronously.
Here is an example of async modification:
Batch modificationBatch = runtimeService.createProcessInstanceModification(processInstanceId) .cancelActivityInstance("anActivityInstanceId") .startBeforeActivity("anActivityId") .executeAsync();
As you can see a new batch is created which will asynchronously execute the desired modification in a separate job. For more information please check the User Guide in the docs.
History Cleanup in Multiple Threads
Now historic data can be removed faster by defining the configuration parameter
This parameter defines how many history cleanup jobs will be created by the engine. Allowed values are between 1 (default) and 8.
With the appropriate configuration of the job executor, these jobs may be executed in parallel, speeding up the history cleanup process.
Camunda Wildfly Swarm Community Extention
In case you’re using Wildfly Swarm to build your application, the new community extension is now available to easily include Camunda Engine and/or Web applications to Wildfly Swarm projects. Please check the project on GitHub.
Integration of the Latest Version of DMN-JS in Cockpit
This alpha release integrates the last version of DMN-JS, the DMN library Cockpit uses internally and which was completly rewritten recently. The benefits are mainly UX improvements and a huge performance boost when vieweing & modeling Decision Tables and Decision Requirement Diagrams.
Next month we will release a minor version. It is scheduled for the end of May and our team is already working on it. Finalising larger features and clearing the backlog are the clear focus.
You can also find out more details if you check out our roadmap.
Your Feedback Matters!
With every release we constantly strive to improve Camunda BPM. To make this possible, we are reliant on your feedback. Feel free to share your ideas and suggestions with us.
You can contact us by writing a post in the forum.
Furthermore, if you have any feedback related to User Experience, things that keep bugging you, things that you think should work differently etc., please share your thoughts with us at https://camundabpm.userecho.com