process-mining
2023.10
false
- 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
- Customizing process apps
- App templates
- Additional resources
- Out-of-the-box Tags and Due dates
- Editing data transformations in a local environment
- Setting up a local test environment
- Designing an event log
- Extending the SAP Ariba extraction tool
- Performance characteristics
Process Mining
Last updated Sep 24, 2025
DataBridgeAgent is a standalone package that can be used to extract data from your source system for use in Process Mining. It contains the UiPath® Process Mining build and the on-premises connector used to prepare the dataset. Currently, the following on-premises connectors (
.mvp) are included in DataBridgeAgent:
- SAP Connector for Purchase-to-Pay Discovery Accelerator;
- SAP Connector for Order-to-Cash Discovery Accelerator;
If you want to use your own custom connector, you can add it to DataBridgeAgent. In this case, you need to configure DataBrigdeAgent for use with your connector.
Note: If you use DataBridgeAgent 2022.4.1 to upload data for TemplateOne-SingleFile, make sure that the output table of the
.mvp connector that is used is named Event_log_raw. If you use DataBridgeAgent 2022.4.1 to upload data for TemplateOne-MultiFiles, make sure that the output tables of the .mvp connector that is used are named Event_log_raw, Cases_raw, (optional) Tags_raw, and (optional) Due_dates_raw.
Prerequisites
Note: The information in the guide is only applicable for DataBridgeAgent 22.4.1 or higher.
It is assumed that you have:
-
a connector
.mvpfile. If the.mvpis dependent on files in the server data or on files in the workspace, these should also be added to DataBridgeAgent.- Server data files you should put in the
server datadirectory. - Workspace data you should put next to the
.mvp.
- Server data files you should put in the
-
a Process Mining on-premises (standalone) installation to:
- determine the application code of module of the connector. See Modules. The application code must be specified in the
connectorModulefield in thedatarun.jsonfile. See Step 4 in the table below. - verify that the connector is set up correctly, i.e. the correct tables are set to be an output table.
- determine the application code of module of the connector. See Modules. The application code must be specified in the
Follow these steps to add a custom .mvp connector to DataBridgeAgent.
- Go to the
workspaces/Connectordirectory. -
Create a new directory for the new connector.
Note: The name you give this directory will be the value you have to fill in for connectorWorkspace.See the illustration below.
- Copy the
.mvpconnector file in the new directory. -
Edit the
datarun.json, and fill in the connectorWorkspace and the connectorModule that correspond to themvpconnector. See the illustration below. - If not done, and if the recommendation above is followed, complete the rest of the
datarun.jsonfile with the extraction settings.
