We’re excited to announce the release of Camunda Optimize 3.1.0-alpha2.

In this second alpha release of Optimize 3.1.0, you can get an early look at many improvements and features in advance of the stable Optimize 3.1.0.

This release adds following new capabilities:

  • Dashboard Filters
    • Instance State Filters
    • Process Start & End Date Filters
  • Flow Node and User Task Filters
    • Flow Node and User Task Duration Filter
    • Assignee and Candidate Group Filter
  • New User Task Reports in regards to Assignee & Candidate Groups

The complete release notes are available in Jira.

You can try out a free trial of Camunda Optimize.

New Dashboard Filters

In Optimize users can add one or multiple reports to Dashboards to get an up-to-date view of process performance at one glance.
With this release we made Dashboards even more powerful by introducing Dashboard Filters.

Dashboard Filters allow Dashboard Viewers to apply certain filters across all reports that have been added to a particular Dashboard:

  • Editors can choose between a range of different filters and add them to their Dashboard as needed.
  • Viewers can easily make use of them by clicking on the “Filters” Button on the Dashboard without having to open and edit every single report.

Within this release we added Process Instance State and Start / End Date Filters for Dashboards. Additional filters are already on the horizon.

In the following you can see how Dashboard Editors can add the filters to a Dashboard:

Dashboard Filters - Edit Mode

State Filters

Once applied the state filter can be used by a Dashboard viewer like this:

Dashboard Filters - Instance State Filtering

Start and End Date Filters

Similar to the state filter the start and end date filters can be used like this:

Dashboard Filters - Start Date Filtering

New powerful Flow Node and User Task Filters

With this release we add more capabilities for detailed Flow Node and User Task Analysis – mainly in the area of their durations as well as Assignee and Candidate Groups.

Flow Node and User Task Duration Filter

Flow Node and User Task Duration are a great indication for underperformance or bottlenecks within your end-to-end process.
Optimize already allows you to look at minimum, maximum and average durations of Flow Nodes and User Tasks for a long time, but with this release we add filtering capabilities for Flow Node and User Task Durations for the first time.

With the help of this new filter you can simply identify process instances where a certain flow node is taking longer or shorter than you expected.

You can find the new Flow Node Duration Filter in the Report Edit mode alongside the Process Instance Duration Filter under the category Duration.

Flow Node Duration Filter 1

Within the modal you are able to specify a duration for one or multiple flow nodes at the same time (combined with OR).

Flow Node Duration Filter 2

In the report edit mode you are able to see the applied filters with the help of a small overlay:

Flow Node Duration Filter 3

Assignee and Candidate Group Filter

When monitoring performance and execution of User Tasks, assignees and candidate groups are an important ingredient.
In order to make the analysis and monitoring more efficient we added Assignee and Candidate Group filters within this release.

You will find the new Assignee and Candidate Group Filters within the Report Builder Filter menu:

User Task Assignee & Candidate Group 1

Within the modal you can define which assignees (or candidate groups) should be included in the set of process instances you are looking at:

User Task Assignee & Candidate Group 2
User Task Assignee & Candidate Group 3

New User Task Reports in regards to Assignee & Candidate Groups

In Optimize 3.0 we added User Task Trend Analysis by introducing “group by start & end date” for User Tasks.
With this release we go even further and allow you to distribute the information by assignees or candidate groups.

This functionality allows you to easily identify how many User Tasks have been completed by assignees at a certain period of time.

You can find the new distribution capabilities in the Configuration Popover.

Assignee Trend Analysis 1

An example could look like this:

Assignee Trend Analysis 2

What’s Next?

This was the last alpha release before we’ll release Camunda Optimize 3.1 beginning of July 2020. Stay tuned.

A smooth update from Camunda Optimize 3.0 to Optimize 3.1 will be possible. Along with the release we will publish a dedicated update guide.

How to get it

If you want to give Camunda Optimize a try, you can download the alpha release here with your Enterprise customer credentials. Please sign up here for a free 30-day trial version.

Please note that alpha releases are not intended for production usage.

If you’re new to Optimize, we recommend that you watch the Getting Started with Optimize in less than 5 Minutes video.

  • Spring Boot Starter for the External Task...

    We are happy to announce that Camunda Platform Runtime 7.15 will provide a Spring Boot Starter for the External Task Client. It allows you to implement Service Tasks decoupled from the Process Engine using Spring Boot. In seconds, you can build an executable JAR that can run almost anywhere. In 2018, Camunda released the first version of the External Task Client. Since then, our community member Oliver Steinhauer developed a Starter that combines the External Task Client with Spring Boot. With the 7.15 release, we will add the former Community Extension to the official Camunda Stack and will maintain it as part of future product releases. Let’s look at the following example to get a better understanding of the Spring...

    Read more
  • The Zeebe Community Welcomes Camunda Cloud

    The Zeebe Community Welcomes Camunda Cloud!

    The Rise of Camunda Cloud Whether you’re a current Camunda Platform user, interested in our open source software, or simply poking around our blog as a result of a tweet you saw from someone in our community, you may have noticed an increase in the number of times you’re seeing words like Camunda Cloud, SaaS, or Zeebe pop up over the past few months. As you may know, we first released Zeebe, the source-available, community-supported workflow engine, in 2017 (read the history of Zeebe in our CEO’s words). Since then, in addition to creating an amazing enterprise product with Camunda Platform, we’ve been listening to your feedback on Zeebe as well as Camunda Cloud, working hard to build a SaaS...

    Read more
  • Camunda Cloud 1.0.0-alpha2 Released

    We’re excited to announce the release of Camunda Cloud 1.0.0-alpha2, which includes Zeebe 1.0.0-alpha2 Operate 1.0.0-alpha2 Tasklist 1.0.0-alpha2 Updates in Cloud Console How to get it In this post, we’ll highlight some of the new capabilities introduced in these alpha releases. Zeebe 1.0.0-alpha2 The Zeebe team continued its work on getting ready for the 1.0 release and improving many internal components of the workflow engine and its underlying infrastructure. Nevertheless, the alpha2 release already provides an improvement for users of the Java client. The Java job worker implementation now offers a back-off mechanism if the Zeebe service is not available. Before the job worker continues to poll the unavailable service continuously, the job worker will apply an exponential back-off strategy...

    Read more