It was a hard time of two months without a new Camunda BPM release, but the waiting came to an end today. We are happy to announce the first release of 2014: Camunda BPM 7.1.0-alpha2. The highlights of this release are:

  • engine:
    • enhance PVM Atomic Operation and Graph Model to provide facility for an activity to cancel a scope or be executed concurrently to activities in the same scope. This refactoring has the following positive effects:
      • write History for Boundary Events, Intermediate Catch Events following an Event Based Gateway
      • Execution Listeners on cancel scope / concurrent activities now work proper
      • and fixed a lot of further bugs
    • a Receive Task with a message reference can be triggered like an ordinary event (docs)
    • query after Historic Activity Statistics
  • cockpit:
    • use grunt to build client sides assets, manage client sides dependencies and fetch them
    • show suspended Job Definitions on the process diagram
    • add a view switcher to be able to write an own process definition or instance view as a plugin
    • implement a new process definition view as a enterprise plugin to show historic process instances data
  • performance test suite (GitHub)
  • enterprise support for Oracle WebLogic 12c, jBoss EAP 6.1 and 6.2
  • some contributions from Clint and Markus
In total, about 90 Issues have been closed during the last two months. For further details have look into the Release Notes and finally

Camunda BPMN model API

Another big thing is the Camunda BPMN model API to parse, create and edit BPMN 2.0 XML files. The BPMN model API has been implemented by Sebastian and the repository is accessible since today! A separate blog post is followed in short.


We had a lot of discussions about how to provide the possibility for an activity to cancel a scope or be executed concurrently to activities in the same scope as native PVM Atomic Operations. In the course of the discussion we drew a lot of graphs for different cases (ie. interrupting and non-interrupting boundary events and interrupting and non-interrupting event sub processes) and discussed how the graphs should be transformed to support the behavior native. As a result we drew some “nice” ASCII pictures in the source code to describe how the source graph should be transformed to achieve the desired behavior.

ASCII pictures in the source code

You are welcome to have a closer look at it and give us some feedback 😉

Define your own view in cockpit

It is now possible to define your own views on process definitions and process instances in cockpit.
Defining views in Cockpit
We used this new mechanism to implement an enterprise plugin containing a view which is based on historic process data, that includes finished process instances too.

Cockpit History

Learn here how to develop a cockpit plugin and implement your own view.

What’s next?

The following weeks we will continue the work on the following topics: standalone eclipse modeler, monitoring of processes based on historic data in cockpit, non-interrupting message event subprocesses, audit trail of task etc. In three or four weeks we will release the next alpha version of Camunda BPM 7.1.
Until then try and test the current release of Camunda BPM and give us feedback!
  • Monitoring Camunda Platform 7 with Prometheus

    Monitoring is an essential facet of running applications in a production system. Through this process, organizations collect and analyze data, and determine if a program is performing as expected within set boundaries. When combined with alerting, monitoring allows for detecting unexpected system behavior to mitigate exceptional situations as fast as possible. Furthermore, tracking the performance of a system enables organizations to improve those aspects that have the biggest impact with higher priority. One essential aspect of monitoring is the list of key metrics you want to observe. There are different categories of statistics that can be of interest here. To observe the defined metrics, there are plenty of application monitoring tools on the market today. They differ in many aspects...

    Read more
  • Securing Camunda 8 self-managed cluster and applications...

    Directory services are an effective way to manage an organization’s users, groups, printers, devices, and more. Most organizations accomplish this using Active Directory, Apache Directory, Oracle Internet Directory, or other similar tools. Recently I worked with a customer who wanted to see how he could secure the Camunda 8 Platform and process applications with such a directory. Their requirements consisted of: Allowing Directory users to access Camunda applications (Tasklist, Operate, Optimize) Accessing secured Tasklist & Operate APIs from our custom project Securing the custom project In this article, I’ll briefly explain the 3 easy steps taken to fulfill their requirements which include: Federate users from the Directory service into Keycloak Declare an application in Identity to access Camunda APIs Configure...

    Read more
  • Accelerate Connectivity with Camunda Platform 8.1

    We’re thrilled to announce Camunda Platform 8.1, the latest release of our process orchestration solution. This new version introduces features that accelerate connectivity to the many different systems and technologies that are required for true digital transformation, including: Create custom Connectors with our Integration Framework to accelerate connectivity New out-of-the-box Connectors for popular services Enhancements to Camunda Modeler that improve productivity Hot backups and official support for Amazon EKS and Red Hat OpenShift Plus, several upgrades requested by Camunda Platform 7 customers Organizations across all industries rely on complex technology stacks to adapt and enhance their operations in response to market dynamics, new disruptive companies, and increasing consumer expectations. Your technology stack likely includes everything from cutting-edge technologies to legacy...

    Read more

Ready to get started?

Still have questions?