- Release notes
- Before you begin
- Getting started
- Integrations
- Working with process apps
- Working with dashboards and charts
- Working with process graphs
- Working with Discover process models and Import BPMN models
- Showing or hiding the menu
- Context information
- Export
- Filters
- Sending automation ideas to UiPath® Automation Hub
- Tags
- Due dates
- Compare
- Conformance checking
- Root cause analysis
- Simulating automation potential
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- Loading data
- Transforming data
- Customizing dashboards
- Publishing Dashboards
- App templates
- Notifications
- Additional resources

Process Mining
2024.10.3
AutomationSuite_Airflow
database. Newer Airflow versions do not support Microsoft SQL Server for Airflow meta databases.
AutomationSuite_Airflow
database, a PostgreSQL database is required for Process Mining on Automation Suite 2025.10. This will apply to both new installations
and existing installations that upgrade to 2025.10.
AutomationSuite_Airflow
database in Process Mining on Automation Suite 2024.10.3.
Also check out the Deprecation timeline in the Overview guide.
AutomationSuite_Airflow
database. If you choose not to use PostgreSQL and keep using Microsoft SQLServer, Process Mining on Automation Suite will
run with a legacy version of Airflow.
AutomationSuite_Airflow
metadatabase.
You are recommended to move to PostgreSQL for the Airflow database, as 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.
Logic configuration editor
SUM of
, COUNT of
, MIN of
, MAX of
, AVERAGE of
, can be used in metric calculations.The following illustration shows an example expression in the Logic configuration editor.
The Case average option for aggregation types, when creating metrics, is no longer available.
Actions on process apps
We organized the access for actions on process apps and process app data in a more logical way.
-
Actions related to the app itself, such as Manage permissions and Clone app, can only be accessed from the app menu in the actions column on the Development tab in the Process Mining portal.
-
Any settings of the app can be changed in the edit app experience.
Custom layout for dashboards
You can now create a custom layout for your dashboards. The new dashboard layout tools enable you to add additional charts by splitting the chart placeholders horizontally or vertically, and to delete charts.
Stacked bar charts
Stacked bar chart is now available as a chart type in the Dashboard editor.
A stacked bar chart allows you to compare different categories while also keeping track of the total value. A stacked bar chart is a bar chart, with bars that are divided into multiple sub-categories. Each sub-category represents a portion of the total. The length of each bar corresponds to the total value, while the lengths of the different parts of the bar represent the values of the different sub-categories.
Check out Charts for more information.
Process manager
The Switch model type button is now labeled Switch process mining type.
Data manager
The field type is now indicated by an icon in front of the field name.
Other
You can now drag and drop the metrics defined for KPI lists and KPI value list charts to arrange the metrics as desired.
Refer to Creating dashboards for more information.
Fiscal calendar
By default, the Gregorian calendar is used to display time-based data in dashboards. If your organization uses a different calendar, such as a financial or corporate calendar that does not align with the Gregorian calendar year, you can now choose to use the Fiscal calendar option.
To use the fiscal calender in the Timeframe filter, the Use fiscal calendar option must be enabled in the Timeframe filter.
Refer to Changing calendar settings.
Process graphs
-
You can use the Show metric values as percentages icon
on the process graph to toggle between numeric values and percentages for metrics that represent a count of values, such as Number of events or Total case value.
Refer to Working with process graphs for more information.
-
The layout of the process graph has been significantly improved, which provides better visibility of the process graph, reduces edge crossings, and makes more efficient use of horizontal space.
Export process graph as BPMN 2.0
You can now 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 manager for more information on importing BPMN models.
Process data dashboard
You can now select display columns from other objects rather than just the main object in the process app in the Visible columns list.
Dashboard charts
We enhanced bin labels for interval formats in line charts and KPI line charts, which improves readability of the data displayed in the chart.
Data export
-
The Export as .CSV option now allows you to export up to 1 Million rows.
-
The data file is no longer immediately downloaded. When the export is ready, you will now get a notification message with a link to the exported file.
-
We enhanced labels for interval formats in line chart and distribution chart exports, which improves readability of the data displayed in the export file.
Refer to Export for details.
Viewing logs
The Log panel now has a link to Data transformations. This allows you to directly go to Data transformations to debug any errors that appear in the log.
Bar charts
The total values for the metrics displayed are now displayed beneath the bar chart.
Pivot table charts
The total values for the metrics are now displayed beneath the pivot table chart.
Dbt version 1.8
Dbt projects now run with dbt version 1.8. Check out the official dbt documentation to make use of the latest dbt functionalities.
tests:
key was renamed to data_tests:
. For existing process apps, this results in a deprecation warning that is displayed when running an ingestion or opening
Data transformations.[WARNING]: Deprecated functionality The `tests` config has been renamed to `data_tests`. Please see https://docs.getdbt.com/docs/build/data-tests#new-data_tests-syntax
for more information.
tests:
config to data_tests:
in the dbt_project.yml
and the sources.yml
files to fix this. For customized process apps, this can be present in other .yml
files as well.
Check out the official dbt documentation on the New data_tests:
syntax for more information.
Adding input tables in Data transformations
You can now easily add input tables by uploading CSV files in the Data transformations editor. Adding an input table in the Data transformations editor does not trigger a new data run. This enables you to create the required SQL queries step-by-step when adding new input tables.
Refer to Data transformations for details.
Data transformations
-
The Preview panel has been enhanced with an updated style. More records are viewable and the preview loading speed increased. We also implemented some small bug fixes.
-
The run status chip and the View logs button are is now displayed in the header bar of the Data transformations window.
-
The View logs button is a toggle button to display or hide the Logs panel. The Logs panel is now displayed as a separate panel to the right of the Data transformations. This allows you to view the SQL files you are editing, the data preview, and the log at the same time.
Simplified data transformations for App templates
-
Generating internal IDs has been shifted from the data transformations to the platform itself. This means that the platform now automatically generates the internal IDs, and that they no longer need to be generated in the data transformations.
Note:This also leads to more flexibility in the data type used for the ID fields. For example,Case ID
fields do no longer need to be of type integer. -
We simplified the SQL for in Event log, Custom process, SAP Purchase-to-Pay, and SAP Order-to-Cash app templates. This makes it easier to customize the data transformations for process apps created with these app templates.
-
Simpler SQL queries.
-
Improved structure with less SQL files.
-
Configuration (seeds) files are no longer needed.
-
You need to create a new process app to benefit from these improvements.
App templates
Metadata_PrecomputedValues
query in the data transformations.
Metadata_PrecomputedValues.SQL
file is no longer available in the Data transformations for newly created apps.
Other
-
The following error message can occur when running the transformations.
Runtime Error:
No dbt_project.yml found at expected path /dbt/dags/.../.../dbt_project.yml
Runtime Error:
No dbt_project.yml found at expected path /dbt/dags/.../.../dbt_project.yml
Follow these steps to solve the issue:
-
Open the Data transformations for your process app.
-
Locate the Transformations section and check for a
sources
folder. -
Move any files and folders from the
sources
folder to the main level of Transformations. -
Delete the
sources
folder.
-
In rare cases, for existing process apps for which you have used sample data as a data source, you may regard input tables in Data transformations that were not visible before. If desired, you can safely delete these tables.
-
The ordering of data values in
Ordinal
andNominal
database fields has changed.
Creating filters from data selections
If you make a data selection on a chart, a filter is created automatically when you click on any of the other charts in the dashboard.
If you do not want to create a filter from the data selection, you can select the Clear selection icon on the chart to clear the data selection.
You can now also select a chunk in a pie chart to create a filter based on the values of the chunk.
Additional search options for list box filters
Additional search options for filter options allow you to search for filter values that you want to select from within a larger list of values. If the field in the list box contains more than 20 values, the following search options appear:
-
Contains;
-
Starts with;
-
Ends with.
List box filter
List box filter values that are unavailable due to values of other filters are now grayed out. This clearly indicates their unavailability at that time.
Timeframe filter
The Case end date field is now selected by default in the Timeframe filter.
Process filters
You can define multiple Starts with or Ends with filters. This allows you to filter on parallel activities by searching for cases that start with the specified activities as Starts with, or end with the specified activities as Ends with, respectively.
Cross-filtering on dashboard level
If you make a data selection on a chart, this will now automatically update the data in the other charts on the dashboard according to the data selection.
Refer to Filters for more information.
App permissions
If you have Edit dashboard permission for a process app, you are now allowed to import a BPMN model in Process Manager and select Apply to dashboards to make the BPMN model available for the process app.
Create new app wizard
The Process model step is now called Process mining type.
SAP Order-to-Cash app template
In the SAP Order-to-Cash template, activities related to Sales Order Item change events and Sales Order Schedule Line change events were not getting recognized correctly. This is now fixed.
SAP-Accounts Payable app template
There was an issue with the SAP-Accounts Payable app template, where accounting documents did not filter correctly on the other objects. This is now fixed.
If you have an existing process app created with the SAP-Accounts Payable app template, you can fix this issue using Data transformations.
-
Open the process app in development mode and go to Data transformations.
-
Add
Accounting_documents_base."Invoice_ID"
, in theAccounting_documents.sql
model, in theAccounting_documents
Common Table Expression (CTE).Note:If you customized the process app, make sure theInvoice_ID
is part of the output of the data model. -
Select Run all to run the data transformations.
-
In Data transformations, select Data model to open the data model for your process app.
-
Locate the
Invoices
table, and remove the relation withAccounting Document ID
. -
Locate the
Accounting_documents
table, and add a relation withInvoices
table based onInvoice_ID
. The following illustration shows the updated data model for SAP-Accounts Payable. -
Make sure the data model changes are saved.
-
Select Apply to dashboards to make the new data model available for use in dashboards.
-
If desired, publish the app.
Message: HTTP Error(422): Cannot look up tenant by Automation Cloud org and tenant name
Possible cause
When selecting the Submit to Automation Hub option in the process graph, the message "HTTP Error(422): Cannot look up tenant by Automation Cloud org and tenant name" can occur even when the Automation Hub service is enabled for your tenant. The issue indicates that provisioning of Automation Hub has not been fully completed automatically.
Possible solution
To solve the issue, you must create a new Automation Hub instance manually. Follow these steps.
-
Select the Automation Hub service from the Automation Suite menu. The Automation Hub landing page is displayed.
-
Select Continue. The Migrate existing Automation Hub data or create a new instance panel is displayed.
-
Make sure the Create new Automation Hub instance option is selected.
-
Select the applicable country from the list and select Confirm.
A new instance is created for your tenant. This may take a few minutes.When the instance is ready, the Explore Automation Program page in Automation Hub is displayed. -
Select the Process Mining service from the Automation Suite menu to go back to Process Mining. The Submit to Automation Hub option should no longer display the message.