The 7.1 release is the basis for the next supported production release for camunda BPM. It is fully supported in the camunda BPM enterprise subscription. Support includes Help Requests based on different SLAs as well as access to camunda BPM maintenance releases. Maintenance releases allow customers to get bug fixes for production systems based on the 7.1 codebase. While the community project will forge ahead for 7.2, we will backport bug fixes to the 7.1 branch and perform maintenance releases reserved for enterprise subscription customers.
There is a Migration Guide targeting existing camunda bpm 7.0 installations.
Detailed Features Overview
The following is a more detailed overview of the new features:
Allows querying, activating & suspending job execution on a per activity level. This allows you to prevent an activity from being executed. This is particularly useful for fixing technical problems or preparing system migrations or updates: process instances can make progress until they reach a given activity and will then queue up until the activity is activated again.
Support for receive tasks was improved: receive tasks now support the messageRef attribute and can be triggered through correlateMessage().
Improved Message Correlation
Message correlation was improved and it is now possible to use a fluent builder API for correlating a message:
.setVariable(“CANCEL_TIMESTAMP”, new Date())
User Operation Log
A new History Entity allowing to query for operations a user performed on a task.
Again, we improved the process engine performance for some constructs mainly in combination with concurrent executions and scopes. We further reduced the number of database queries (SELECTs) necessary at runtime. We also added a performance test suite to our repository which allows running benchmarks and SQL statement logs.
Bpmn Model API
We added a completely new component called the BPMN Model API. The camunda BPMN model API provides a simple and lightweight library for parsing, creating, editing and writing of BPMN 2.0 XML files. The model API enables an easy extraction of information from an existing process definition or to create a complete new one without manual XML parsing.
The following example shows how to create a new process with the fluent builder API:
History for Process Instances including sophisticated querying and searching for finished process instances and drill down into individual instances, providing:
Audit Log, allowing to follow the path of a process instance through the diagram, visualizing running, completed and cancelled activity instances.
As well as a Variable Log and a User Task log:
Taskforms including support for select boxes, radio buttons and custom scripting & validation. (Quickstart Example, Docs).
In addition, we added the Generated Task Forms feature which allows you to define a simple form in camunda Modeler and have it rendered in Tasklist (Quickstart Example, Docs).
We now provide a standalone distribution for the web application (Tasklist + Cockpit) as .war file download. This distribution includes an embedded process engine (configured using spring xml) and can be deployed on most application servers.