Join our largest event of the year | CamundaCon 2022 October 5-6

Icon Close

We’re pleased to announce the next alpha release of Camunda Platform Runtime 7.17.0. This release features the following improvements:

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.

Composite Incident Handlers

Incidents are notable events that happen in the process engine. Such incidents usually indicate some kind of problem related to process execution. Depending on your setup, you might want to have a custom incident handler that – additionally to the default behavior – sends an email to an administrator whenever an incident of type failedJob occurs. By default, adding that custom incident handler overwrites the default behavior with the custom incident handler’s behavior. As a consequence, the default incident handler is not executed anymore. If the default behavior should be executed as well, then the custom incident handler also needs to invoke the default incident handler, which includes using an internal API.

With this release, you can enable the use of composite incident handlers by using the process engine flag compositeIncidentHandlersEnabled. As a result, adding custom handlers via the ProcessEngineConfiguration#setCustomIncidentHandlers for an incident type will not override the default handler. Instead, those custom handlers will be called as sub handlers from the default handler. Now, there is no need to use an internal API for this anymore.

This feature was proposed and implemented by one of our Camunda community members, Pavel Pletnev. Thank you very much, Pavel!

Share Your Thoughts with Us

Your feedback is really important to us. Please download Camunda Platform Runtime 7.17.0-alpha1, try it out and let us know what you think about it.

You can contact us in the forum, send a tweet to @Camunda or file a bug in our ticket system.

  • Feel Example Flow in Camunda 8

    FEEL more confident transforming data

    FEEL (Friendly Enough Expression Language) was created by the Object Management Group (OMG) “as part of the DMN standard”. Its goal is to be easy to understand, and at the same time, be full-featured enough to handle decision tables and literal expressions. When business and IT often work together on complex projects, writing expressions in a (relatively) accessible way reduces miscommunications and helps align teams. Camunda uses FEEL to map and transform business process data dynamically. For example, a loan application process pulls a credit score from an API call into a decision table. The decision table automates the next step of the process depending on the rules in the table. The data from the decision automation can then be...

    Read more
  • Increase your resilience with new regions in...

    We’re excited to announce new regions for Camunda Platform 8 SaaS that further strengthen the resilience, performance, and data requirements for our SaaS customers. Enterprise customers can now choose to create their clusters in a number of regions including Europe West, US Central, US East, and the most recent addition, Australia South East. This provides multiple benefits, such as increasing availability, allowing to set up fail-safes, adhering to regulatory requirements for regional data storage, and reduced latency due to closer physical proximity. Resilience and redundancy in technology are important for all modern organizations and are top of mind for many. Across industries, organizations need a solution that scales effectively and is resilient to provide a good base for process orchestration....

    Read more
  • Black title slide that reads, "The CAM project in JIRA is moving to GitHub"

    The CAM project in JIRA is moving...

    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...

    Read more

Ready to get started?

Still have questions?