We are happy to share the first alpha release of Camunda BPM 7.13 with you!

This release features the following improvements:

  • Show Failed Activity in Jobs & Incidents
  • Exclude Nodes from participating in History Cleanup
  • Define Invocations per Batch Job by Batch Type
  • Oracle 19c Support
  • 22 Bug Fixes

You can Download Camunda for free (click on Preview Release) or Run it with Docker.

For a complete list of all improvements take a look at the release notes.
Please also see the list of known issues.

If you want to dig in deeper, you can find the source code on GitHub.

Show Failed Activity in Jobs & Incidents

Quick discovery of exception root causes can be key to a frictionless operation of processes. Among other tools, Camunda provides job logs and incidents to easily gain insights into failures and their causes. For specific scenarios this can however be harder to achieve than desired. Take the following example:

  1. A process has two tasks foo and bar.
  2. Task foo is marked as asyncBefore.
  3. The execution of task bar fails.

In that case, the job and its job log will only show the failure’s stacktrace and the id of task foo as the related activity of the asynchronous continuation job. However, identifying the actually failing task bar as the root cause here is a rather manual task that might for example involve further investigations of server log statements.

With this release, runtime and history data for jobs and incidents will additionally provide the id of the activity that caused the failure. With this, the root cause of a failure will be more accessible and also digestible as structured information.

You can find the new lastFailingActivityId in numerous REST request results as shown in the Get Jobs and the Get Historic Incidents endpoints.

Exclude Nodes From Participating in History Cleanup

In a multi-engine setup, it is sometimes not desired to execute the History Cleanup job on all nodes,
for instance, because the additional load during History Cleanup ties up capacities and slows down
other tasks in the Workflow Engine.

Camunda Cockpit history cleanup

Starting with this release a new engine configuration flag is available to exclude a specific node
from participating in History Cleanup:

<property name="historyCleanupEnabled">false</property>

You can read more here:

Define Invocations per Batch Job by Batch Type

With the help of the global engine configuration property invocationsPerBatchJob, it is already
possible to configure how often a batch job is called. Sometimes it is necessary to define the
invocations per batch job individually for each batch type. For instance, to balance the number
of jobs that are created per batch type.

This feature is now available and can be configured for Spring-based environments as follows:

<property name="invocationsPerBatchJobByBatchType">
  <map>
    <entry key="process-set-removal-time" value="10" />
    <entry key="historic-instance-deletion" value="3" />
  </map>
</property>

You can read more here:

Oracle 19c Support

Starting with this alpha, Camunda is officially supported to run on Oracle 19c.

Your Feedback Matters!

With every release, we strive to improve Camunda BPM. To make this possible, we are reliant on your feedback. Feel free to share your ideas and suggestions with us.

You can contact us by writing a post in the forum.

  • Header image that reads, "Camunda Automation Platform 7.18.0-alpha4 Released

    Camunda Automation Platform 7.18.0-alpha4 Released

    We are pleased to announce the next alpha release of Camunda Platform Runtime 7.18. This release features the following improvements: Support for H2 2.1 Traditional Chinese translations are available Improved status monitoring of batch jobs Improved safety of executing a batch operation on the Batch Operation page 8 Bug Fixes You can download Camunda for free or run it with Docker. For a complete list of all improvements, take a look at the release notes. Please also see the list of known issues. If you want to dig in deeper, you can find the source code on GitHub. Support for H2 2.1 This release adds support for the H2 database in version 2.1, which provides fixes for vulnerabilities. Enterprise customers...

    Read more
  • A title slide that reads "Camunda Optimize 3.9.0 alpha3 Released

    Camunda Optimize 3.9.0 alpha3 Released

    We’re excited to announce a new release of Camunda Optimize. Camunda Optimize provides business activity monitoring for workflows, supporting continuous process improvement by providing transparency into your automated workflows and decisions. Business-friendly reports, dashboards, and alerts make it possible to identify process bottlenecks, improve end-to-end processes, and evaluate the success of your process automation initiative. In the rest of this post, we’ll highlight some of the new capabilities introduced in Optimize 3.9.0 alpha3. What’s new? Ease of adding new reports to dashboard Reports are added to dashboards to design an individual overview of the performance of your processes. Adding reports to dashboards was already possible with previous versions of Optimize, but now we’ve reduced the number of steps to do...

    Read more
  • A Technical Sneak Peek into Camunda’s Connector...

    Learn what a connector is made of, how the code for a connector roughly looks, and how connectors can be operated in various scenarios. Since this is a preview, details are subject to change.

    Read more

Ready to get started?

Still have questions?