Camunda Team Blog

camunda BPM 7.0-alpha7 released

Written by Roman Smirnov on , under Execution category.
camunda BPM 7.0.0-alpha7 is out now!

The highlights of this new release are:
  • In Cockpit we worked on the visualization of Process Instances:
    • Incidents of a running process instance will be shown in the corresponding rendered process diagram.
    • The former introduced Activity Instance Tree will be visualized as a tree.
    • Now it is possible to select a BPMN element in the rendered process diagram or to select a activity instance wihtin the activity instance tree. If a single BPMN Element is selected, the corresponding activity instances will also be selected in the tree (and vice versa).
    • Variable instances of the process instance/activity instances will be shown in the view.
  • In Cockpit you can switch between the configured process engines (multi-tenancy).
  • The variable instances can be selected via an introduced Java and REST Api.
  • Support of a further Bpmn 2.0 Element: Link Event.
  • New user guide for Cycle and Tasklist.
33 issues were closed. See the complete release notes in Jira.

Visualization of a Process Instance

The following screencast summarizes all in this release implemented features in camunda Cockpit:




Support of multi-tenancy in camunda Cockpit

Due to the possibility to run multiple tenants on the camunda BPM platform you can now switch between the configured process engines in Cockpit to get the process engine specific information.


Variable Instance query

Now it is possible to create a variable instance query to get variables instances:
runtimeService
  .createVariableInstanceQuery()
  .list()
Furthermore, with the Java Api you are able to query after variables instances for more than one task id, process instance id, execution id and activity instance id at once. For example:
runtimeService
  .createVariableInstanceQuery()
  .taskId("aTaskId", "anotherTaskId")
  .list
In the case of the example you will get all variable instances with the task id "aTaskId" and "anotherTaskId". This is also possible with the process instance ids, execution ids and activity instance ids.

Note: At the moment it is not possible to select variable instance with the type 'bytes'.

The variable instance query is also exposed via the REST API.