Thorben Lindhauer

For almost 10 years, JIRA has been our development issue tracker for the core components of Camunda Platform 7. About 15,000 tickets later, Camunda’s engineering has grown from one team to a team of teams. Many new projects have used GitHub exclusively as a code repository and an issue tracker from the start. In October, we will move the CAM project to GitHub issues. With this change we are reducing the gap: our community can participate in our development processes with a single account. We achieve a unified approach for managing development issues, making it easier for everyone to participate. We thank everyone who has contributed to our CAM issue tracker and hope that the collaboration continues in our new...

We're excited to announce that Camunda Automation Platform 7.17.0 is now available with many new features.

We are proud to announce Camunda BPM Run, a new distribution of Camunda BPM that provides the Camunda web applications (Cockpit, Tasklist, Admin) and the REST API. Camunda BPM Run is highly configurable and can be operated without any Java knowledge.

Sometimes we start a process, and after some initial processing, it does not continue for no apparent reason. Usually, this happens at asynchronous continuations or BPMN timer events, so points in the process where the job executor, the process engine’s component for deferred work, takes over. While the job executor is a well-tested and battle-proven piece of software, it is not a closed system. It integrates with a relational database, an application server and the processes and applications it runs. Problems with job execution typically arise in this interaction of components. In this article, we look at common reasons why job execution can be delayed or stuck, how to diagnose, and how to resolve them.

In Camunda BPM, every process instance can have a so-called business key. This post explains its purpose, how it compares to process variables and how it can be used.

The Case Management Model and Notation (CMMN) standard deals with unstructured work that is performed in the context of a so-called case. A CMMN model specifies the frame in which a case is handled. It expresses design time considerations, such as hard restrictions when an activity can be performed or not. Aside from that, there are often soft patterns that only emerge at runtime based on case workers’ experience. Detecting such patterns and providing insights to case workers can make dedicated case management with CMMN and Camunda especially useful.

Today, we release Camunda BPM 7.6.0-alpha1. It is primarily a release that fixes a regression in the REST API’s correlation method as present in 7.5.0. Check JIRA ticket CAM-6139 for whether this problem affects your application. Also, it provides the following improvements / features: Access DelegateExecution from Context (Thread Local) using Public API Get a correlation result response when correlating a Message Retrieve the Error Message of a thrown Error Event Read the release notes for a complete list of changes. Download Camunda For Free or Run it with Docker. Please let us know on the user forum if you find any problems.

After six months of dedicated work, we are proud to announce the release of Camunda BPM 7.5.0. The highlights are: Process Instance Migration Multi Tenancy with Tenant Identifiers Reporting API and Duration Report External Task Improvements Webapp UI/UX improvements New Supported Environments And More Download Camunda For Free or Run it with Docker. Register for release webinars held in English language and German language where we will present the new features to you. Read the update guide to learn how to update an existing installation or application. See our JIRA for a list of known issues and the section at the end of this post on issues that we are fixing in the near future.