The highlights of this release are:
- Improved DMN Engine
- Hit Policies
- Data Types
- New Cockpit Features,
- Auditing of DMN Decisions,
- BPMN Heat Map,
- Improved BPMN Engine
- Support for BPMN Escalation
- Improved Asynchronous Execution Efficiency
- SLF4j Logging
- Faster Deployments
- Improved CMMN Engine
- Add Support for Repetition Rule
- Support for Tomcat 8
- New Documenation
- Many Bugfixes
Overall more than 170 issues were closed. See complete Release Notes in Jira.
DMN Auditing in Cockpit
Cockpit now provides a preview of the support for DMN-based Decision Auditing.
The dashboard displays now all deployed decision tables. Selecting a decision table opens the Decision Definition View:
|Decision Definition View|
This view displays the decision table itself and displays aggregated information of all past executions of the decision table (decision instances).
Currently, only a list of all decision instances is displayed. However, much more features can be added here in the future, such as searching for decision instances,
displaying aggregated information about how often each rule in the table fired, and so on.
Selecting an individual decision instance opens the Decitions Instance View:
|Decision Instance View|
The Decision Instance view provides information about an individual execution of the decision (table). The focus of this view is to allow users to inspect an individual decision, understanding which rules evaluated to true (and why?) and what output was produced. At the moment it is possible to inspect the input and output values of the table. This view can will be enhanced by visualizing as much information as possible inside the table itself, including highlighting of fired rules etc.
BPMN Heatmap in Cockpit
(This feature is only available in the Enterprise Edition.)
Cockpit now features a BPMN Heat Map which gives a quick overview about hot spots in a BPMN process in the blink of an eye:
|BPMN Heat Map|
The idea is that activities and sequence flows are colored based on the number of times they have been executed. Activities which have been executed many times are colored in a brighter color than activities which were executed fewer times. Or in other words, some activities are “hotter” than others 🙂
How the history plugin came together is actually a nice success story for “community-driven innovation”:
Since quite a while, our man Jakob has been preaching about how BPMN allows intuitive visualization of statistics and data around process execution. “Even something like a heatmap, you know like the weather man uses, is easily possible”, he used to say. At some point Matthias Wiedemann -at the time working for our consulting partner Opitz Consulting- actually built a BPMN Heatmap as a Community maintained Cockpit Plugin. The plugin was a huge success and everybody wanted to use it. But, since it was a community maintained plugin, people did not always have time to port it to the latest version of Camunda or ensure compatibility with all versions. It also had a lot of limitations around how the visualization was rendered (because it was a proof concept implemenation) and we thus decided to re-iterate on the idea, rewrite the code and add it to cockpit as an out of the box feature.
Support for BPMN Escalation
The Camunda Engine now fully supports BPMN Escalation.
Improved Asynchronous Execution Efficiency
Again, the performance and efficiency of the job executor has been improved. Read all about it in Thorben’s Blogpost.
Support for CMMN Repetition Rule
CMMN Repetition Rule is now supported in CMMN engine. This was a much requested feature and I am very happy that we could add it in these busy DMN times 🙂
We have completely revamped the whole documentation, improving content, structure and the layout.
What’s up next?
- DMN, DMN, DMN, … 🙂
- Process Engine Runtime Repository View in Cockpit,
- Support for reactive Service Task Workers,
- As always, amazing things are happening in bpmn.io,