process-mining

false

Process Mining

DELIVERY:

Last updated Nov 11, 2025

2.2510

Release date: November 11, 2025

App templates

Purchase to Pay - SAP app template improvements

The following dashboards are now available for the Purchase to Pay - SAP app template:

Efficiency - Order process velocity
Efficiency - Supplier performance
Efficiency - Accounting process
Compliance - Maverick buying

These dashboards provide insights into KPIs relevant to the SAP Purchase to Pay process.

Check out Purchase-to-Pay SAP app template for more information.

Simplified structure of input data

We simplified the structure of input data for app templates. Input tables now retain the same names used in your source system.

For Event log and Custom process app templates, input tables do no longer need the _raw suffix.
For Purchase-to-Pay and Order-to-Cash app templates, input tables do no longer need the _base_raw suffix.
For specific app templates, input tables do no longer need the _input suffix.

Note: You need to create a new process app to benefit from these improvements.

Simplified data transformations for Purchase to Pay - SAP app template

We simplified data transformations for the Purchase to Pay - SAP app template by removing redundant dependencies on the Event log and streamlining Common Table Expressions across SQL files. This allows you to define tags and due dates more easily.

CData Sync extractions

We updated the hours format in replication queries that use the FORMAT function, changing hh to HH. For example, FORMAT([Created], 'yyyy-MM-dd hh:mm:ss') has been updated to FORMAT([Created], 'yyyy-MM-dd HH:mm:ss').

If applicable, update your queries and rerun the extraction to ensure your data reflects the correct hours in 24-hour format.

Support for CData Sync 25.2.9369

We now support CData Sync 25.2.9369 for Loading data using CData Sync. Read more about the updates in the official CData Sync documentation.

Workspace Management

CData Sync 25.2.9369 includes Workspace Management. Workspaces allow you to organize connections, jobs, and access policies, and make it possible to restrict user access to specific connections or jobs.

Refer to the official CData Sync documentation on Workspace Management for more information.

Upgrade CData Sync

Check out Upgrading CData Sync for more information on upgrading to CData Sync 25.2.9369.

Create new app wizard

Improved flow

New process apps are created using a Directly follows process model, by default. You can switch the process mining type to a Discover process model or an imported BPMN model from the Process models page.

Refer to Switching the process mining type for more information.

Dashboard editor

Dashboard editor layout

We organized the access for enhanced editing in a more logical way. The Data transformations editor, Process manager, and Automation manager can now be accessed from the Dashboards drop-down menu by selecting the applicable option.

You can return to the dashboard editor by selecting the Dashboards option in the menu.

Check out Working with the dashboard editor for more information.

Duplicating dashboards

You can now duplicate a dashboard. This enables you to quickly create dashboards from dashboards that are already present in your app. Duplicating a dashboard creates a copy of the original dashboard that you can adjust without the need to build a new dashboard from scratch.

Undo and Redo

The Undo and Redo options allow you to reverse or reapply your last actions or modifications to dashboards and charts.

Adding automations

You can now add fields and select field values to define conditions for automatic triggers.

Logic configuration editor

The following operators are available for aggregate expressions:

DISTINCT COUNT
PERCENTAGE
ANY is TRUE
ALL are TRUE

Check out Expressions for more information.

Data transformations

When opening the Data Transformations editor, a preview of the input data is now immediately available. You no longer need to run all transformations to see the initial preview.

Dbt transformations now run only the models that have changed, making the Apply to dashboards action faster.
SQL files and input files are now displayed in tabs. When you open a SQL file or an input file, a new tab is opened in the Data transformations editor. This enables you to open and work with multiple files simultaneously.
- Folders and file tabs are retained across sessions.
- You can quickly pin a tab or close the current tab, all other tabs, or all tabs from the tab context menu.
- You can open a file in a pinned tab. This allows you to quickly access files without having to reopen them repeatedly.
You can view a compiled version of the SQL code after running the queries by enabling the Compiled SQL toggle option. This is helpful when debugging SQL errors, as the reported line numbers correspond to the line numbers in the compiled SQL.
File and folder actions previously available in the context menu are now accessible through the More actions menu.
A warning or error message will be displayed when a table in the dbt project exceeds a certain number of records. This will help you protect against potential mistakes, such as incorrectly formed join operations that significantly inflate the table size.

You can modify the thresholds for these warnings or errors in the dbt_project.yml file.

Managing deviations

Managing deviations allows you to mark deviations as conforming. In this way, you can define that the deviations will not be taken into account in the calculations for the Conformance rate and the number of deviations, and also will not be visible in the Conformance checking dashboard.

Check out Managing deviations for more information.

Managing input data

Input data screen

Input data is now automatically mapped to the expected tables and fields when uploading data files. You can change the mappings and edit the settings of target tables and fields to your business needs. The following illustration shows an example field mapping.

Input data mapping is available in the following scenarios: creating a new app, uploading data for existing apps, cloning or importing apps, and adding input tables in Data transformations.

Watch the following video for a demo of the input data screen capability.

Refer to Managing input data for more information.

Note:

When using input data mapping for uploading data for existing apps, warning messages regarding dbt tests may be displayed when running the transformations. Follow these steps to resolve the issue:

1. Go to Data tranformations.

2. Select the dbt_project.yml file.

3. Delete the following lines.

# Overwrite default name of schema suffix to prevent long schema name.
data_tests:
  +schema: ""# Overwrite default name of schema suffix to prevent long schema name.
data_tests:
  +schema: ""

4. Run the transformations.

You should no longer see the warning messages.

Note:

When existing apps perform a new data run, sources.yml will be backed up and replaced by an auto-generated sources.yml file. Going forward, new input tables are automatically added to your sources.yml.

Multi-process Process Mining

With multi-process Process Mining, you can break up your end-to-end process in multiple parts. This makes it easier to analyze the individual processes, while still being able to draw conclusions about the end-to-end process.

Each process can follow a different object in your end-to-end process. For example, one process could focus on the purchasing part of a Purchase-to-Pay process and follow a Purchase Order. Another process could focus on the finance part, and follow all Invoices, regardless of whether these Invoices had a Purchase Order or not. This way, both can be analyzed in one app.

Refer to Adding and editing processes for more information. Watch the following video for a demo of the multi-process Process Mining capability.

Note: Currently, multi-process Process Mining is only available for newly created apps.

Note: If you have changed a process name, a message Data model changed may pop up when opening the app without performing a new ingestion. This happens because process table names are now automatically derived from the data model. After you close the message, the name of the process table is updated to match the new process name.

PostgreSQL for Process Mining Airflow database

Starting from Process Mining on Automation Suite 2.2510, you must use PostgreSQL for the AutomationSuite_Airflow database. PostgreSQL runs with the latest versions of Apache Airflow. Latest versions of Apache Airflow have various functionality, performance, and security fixes that older versions lack.

Important: Using Microsoft SQL Server for the AutomationSuite_Airflow database is no longer supported.

Refer to SQL Requirements for Process Mining and Database configuration for more information on how to set up and configure the PostgreSQL AutomationSuite_Airflow metadatabase.

Process graphs

Process graph heatmap

The heatmap capability animates the flow of events through your process graph, helping you identify areas of high activity and congestion. As events move through the process, edges and activities will grow thicker and appear in darker shades to represent higher volumes of events occurring over time.

Refer to Working with process graphs for more information.

Export process graph as BPMN 2.0

You can export a process graph as a Business Process Model Notation (BPMN) 2.0 file. Export as BPMN 2.0 diagram generates a BPMN model based on the filtered dataset that you can download to your computer.

You can utilize the downloaded BPMN model in model-based apps using the Import BPMN model option in Process manager. Additionally, you have the option to import the file into a BPMN modeler, for example BPMN.iO or in the Maestro modeling canvas.

Check out Process models for more information on importing BPMN models.

Horizontal view

You can now switch the process graph to a horizontal view. For example, if you are familiar with Business Process Model Notation (BPMN) diagrams, which are often displayed horizontally, you might find a horizontally oriented graph easier to read.

Process Mining AI Units consumption dashboard in Insights

The Process Mining AI Units consumption dashboard provides visibility into the usage of AI units for Process Mining apps. It offers detailed insights into how apps consume AI units, which apps consume the most AI units, and historical AI unit consumption trends.

For more information, refer to Process Mining AI Units consumption in the Insights guide.

Also refer to the Insights 2.2510 release notes April 2025.

Process Mining portal

The Development tab is now visible if you have edit permissions for at least one app. In this case, you do not need to be assigned the Developer role.

Published process apps

Percentage and number of objects for filters

The percentage of objects is now displayed in the graphic for the applied filters. If you hover your mouse over the graphic, the number of objects in the selection out of the total number of objects, and the percentage of selected objects are displayed.

Refer to Data selections for more information.

Filter panel

The After timeframe filter now filters all data after a particular date until the current date. It no longer includes the date of selection.
The percentage of objects is now displayed in the graphic for the applied filters.
The number of applied filters is now displayed in the Filter icon.

Process apps

We organized the access for actions in the header bar in a more intuitive way to help you navigate faster.

Unified Pricing

We are excited to announce Unified Pricing, our innovative licensing model that brings new licensing plans, user licenses, and a consolidated consumption unit. We are also excited to let you know that Process Mining is now available through Unified Pricing. For details on the impact of Unified Pricing on Process Mining, visitUnified Pricing for more information.

For extensive release notes, refer to the Automation Suite release notes guide. For overview licensing information, refer to the Automation Suite Admin guide.