We’re excited to announce the release of Camunda Optimize 3.2.0.
Camunda Optimize provides business activity monitoring for workflows, supporting continuous process improvement through transparency into your automated workflows and decisions. Business-friendly reports, dashboards, and alerts make it possible to identify process bottlenecks and improve end-to-end processes.
If you’d like to get started with Optimize 3.2.0 right away, you can download the release here with your Camunda Enterprise Platform customer credentials. You can also use Docker to run Camunda Optimize.
And if you’re not yet a Camunda customer, you can sign up for a free 30-day trial of the Camunda BPM Enterprise Edition, which includes Camunda Optimize.
In the rest of this post, we’ll highlight some of the new capabilities introduced in Optimize 3.2.0.
Dashboard Templates & Advanced Sharing
With Optimize 3.2.0 we speed up the initial creation of Dashboards significantly. When creating a Dashboard you can now choose between three Dashboard Templates: Performance Overview, User Task Performance, and Blank Dashboards.
Once you save the newly created dashboard it will automatically create all underlying reports, so that you can share the dashboard with other users.
Sharing and Embedding Dashboards
Dashboards can be shared with external users that do not have access to Optimize or embedded into another website by enabling sharing.
With Optimize 3.2.0 we allow users to apply customized Dashboard Filters when activating sharing. This makes sharing more flexible since one shared dashboard can be reused for different scenarios, e.g. sharing the same dashboard once for running and once for completed process instances.
Simply use the feature by sharing a dashboard and activate the new checkbox:
Monitoring Incidents, Trends, and Process Performance
With Optimize 3.2.0 we are introducing incident and duration reports, and are significantly enhancing our trend analysis capabilities.
Introducing Incident Reports
Incidents are notable events that happen in the process engine. Such incidents usually indicate some kind of problem that is related to process execution. Incidents can have a significant, negative influence on process performance, since in certain situations the process instance does not progress any further.
With Optimize 3.2.0 we are introducing the first incident reports that analyze the number of incidents, as well as the length of time it took to resolve incidents. Understanding which incidents occur frequently, or how long it takes to resolve them, can be a good indicator of the process improvements needed in this particular step.
The number of incidents (including open and resolved incidents) can be displayed per process or also grouped by the flow nodes where they occurred. When grouping by flow nodes the result can be visualized as a table, a chart, or as process heatmap:
Introducing Duration Reports
With this release, you are now able to analyze the distribution of durations across selected process instances, flow nodes, and user tasks. This allows you to easily identify if there are certain instances that run especially long or short and gives you a good idea about where to start with your process improvements.
You can create such a report by simply creating a new process report with the view process instance, flow node, or user task count and group by duration. The results can be visualized as a table or bar chart as well as a line chart.
In situations where you are looking at flow nodes or user tasks, you can even distribute by flow nodes or user tasks in order to look at the single steps of the process in more detail.
The following screenshots show how to create the mentioned reports:
Improved Trend Analysis
Trend Analysis based on Process Context
Trend analysis has become more powerful since we introduced new capabilities related to process context. Process Instance Count and Duration reports that are grouped by start or end date can now be distributed by a variable. This allows you to easily identify how process instances are trending and if trends are dependent on the process context (e.g. a specific process variable):
You can create this report by grouping process instances by start or end date and distributing by a variable of your choice using the configuration options:
Flow Node Performance over Time
With this release, we are also adding a new trend analysis capability which allows you to easily analyze the frequency and duration of flow nodes over time. Subsequently, you can find if performance is trending over time and if changes to the process are speeding up the execution of certain steps of the process.
In order to use the feature, simply create a new process report with the view FlowNode count or duration and group by start or end date. Additionally, you can also distribute the results by Flow Nodes by using the Configuration Popover within the Report Builder.
The result of your report could look like this:
Process Reporting and Alerting Enhancements
Besides above mentioned new report types and dashboard improvements, Optimize 3.2.0 comes also with more reporting and alerting enhancements that improve process analysis.
Raw Data Pagination
We removed the limitation of 1000 results when looking at raw data of process reports. This means you can now page through all underlying process instances – even if the report includes more than 1000 process instances. This functionality significantly improves root-causing, because you do not have to adjust filters in order to see all instances.
New Cancelled Flow Node Filter for Process Reports
During process execution Flow Nodes can be cancelled or interrupted. In such case the Flow Node will not be executed or completed anymore, but instead either the whole process instance is cancelled, completed or the process instance continues with the execution of another flow node.
Since cancelled flow nodes can have an impact on process performance we are introducing a new Flow Node Cancelled Filter on the process level, so that you can identify which process instances were affected by a cancelled flow node.
Additionally, we introduce the cancelled flow node status which means you can look at duration and number of cancelled flow nodes within Flow Node Views:
New Variable Filter for Process and Decision Reports
With this release, we are introducing a new type of Variable filter for Process and Decision Reports. Within the Variable Filter modal, you can now choose to use contains or does not contain when filtering process or decision instances based on variables:
Alerts to multiple recipients
For cases where you want to be notified when your report hits a critical value, Optimize has an alerting function. With this release, you are able to send alerts to multiple recipients at the same time by simply adding multiple email addresses into the email field.
You can see in the following screenshot how it works:
With this release, we are introducing an option to send telemetry data to Camunda. The goal of this initiative is to offer you a great and stable user experience when using Camunda. The insights into common environment setups and product usage patterns we can gather will help us to make product development decisions for your benefit. A list of the type of information we can collect can be found here.
By default, the feature is disabled and has to be explicitly enabled. It can be either activated via configuration by setting the initializeTelemetry flat to true or alternatively via the user interface by superusers. Please find more information here.
Updates to Supported Environments
With Optimize 3.2.0 we are adding support for Camunda Runtime 7.14 and drop support for 7.11.
Additionally, we are extending the support of Elasticsearch 7.7 and 7.8.
This means Optimize 3.2.0 supports:
- Elasticsearch versions 7.0 – 7.8.
- Camunda Runtime 7.12.11+, 7.13.5+, 7.14.0+
In our documentation, you will find a full list of supported environments.
Improved Upgrade Experience
Optimize 3.2.0 allows you to run the upgrade as part of the Optimize startup. So instead of having to run the upgrade script manually you can switch on the upgrade using a parameter or make use of Kubernetes init-containers. Please refer to the Upgrade Guide.
How to get it
If you’re new to Optimize, we recommend that you watch the Getting Started with Optimize in less than 5 Minutes video.