- Release notes
- Before you begin
- Getting started
- Managing access
- Working with process apps
- Creating process apps
- Loading data
- Customizing process apps
- Data transformations
- TemplateOne app template
- Purchase to Pay app template
- Order to Cash app template
- Basic troubleshooting guide
Loading data using DataBridgeAgent
.tsv
files. These .tsv
files are loaded into the Microsoft SQL Server database using CData Sync. See the illustration below for an overview of the
data flow.
.mvp
connector. Otherwise, use CData Sync, Theobald Xtract Universal for SAP, or files to upload data.
.mvp
file) can be loaded using DataBridgeAgent. This enables you to reuse the existing Data transformations, and load the output data into a process app in Process Mining Automation Suite.
.mvp
connector file created in Process Mining on-premises (standalone) to DataBridgeAgent.
Use the following link to download DataBridgeAgent: https://download.uipath.com/ProcessMining/versions/21.10.3/DataBridgeAgent/DataBridgeAgent-21.10.3.zip.
.mvp
connectors of a Process Mining on-premises standalone version that is the same version as the DataBridgeAgent. (v2021.10.3).
DataBridgeAgent is a standalone tool. It is recommended to create a separate folder on the server to use DataBridgeAgent.
C:\
drive. Since DataBridgeAgent contains connectors that have rather long names, file paths can become very large, which may cause issues when running the
datarun.bat
file to create the dataset.
<PLATFORMDIR>
). Also, do not install DataBridgeAgent in the Downloads folder.
.mvp
connector used to prepare the dataset. Currently, the following on-premises (standalone) connectors are included in DataBridgeAgent:
- SAP Connector for Purchase-to-Pay Discovery Accelerator; See Using DataBridgeAgent with SAP Connector for Purchase-to-Pay Discovery Accelerator.
- SAP Connector for Order-to-Cash Discovery Accelerator; See Using DataBridgeAgent Wwith SAP Connector for Order-to-Cash Discovery Accelerator.
.mvp
connector, you can add it to DataBridgeAgent. In this case, you need to configure DataBrigdeAgent for use with your connector. See Adding a custom connector to DataBridgeAgent.
DataBridgeAgent automatically converts input field names to lowercase and special characters to underscores. If you use DataBridgeAgent to load data, make sure to edit the transformations of your process app and set all input fields to lowercase. For example:
{{ pm_utils.to_varchar('Cases_base_raw."Case_ID"') }} as "Case_ID", must be changed to
{{ pm_utils.to_varchar('Cases_base_raw."case_id"') }} as "Case_ID",.
DataBridgeAgent is different from an on-premise (standalone) installation since it:
- is a command-line tool, and therefore does not have a user interface;
- does not require a separate license;
-
does not require IIS.
Note: The DataBridgeAgent already includes the connectors. You do not need to download and deploy the connector itself.
See also System requirements.
Uploading data to Process Mining (Automation Suite) requires access to the SQL Server database location to which the extracted data needs to be uploaded. To set up a SQL Server destination connection you need the following setup parameters to authenticate access to the SQL Server database location.
Server
Database
Schema
Role
If you want to use data directly from your SAP system in Automation Suite you must set up the SAP extraction before you can use DataBridgeAgent. See Set up Native SAP Extraction for a detailed description.
.csv
files always make sure that:
- a separate
.csv
file is available for each table. - the file names of the
.csv
files are the same as the names of the input tables of the connector. - all the fields used in Process Mining are present in the
.csv
file. - the fields in the
.csv
files have the same names as the field names used in Process Mining column.
The CSV settings can be defined in the CSV parameters of DataBridgeAgent.
If you want to use data from an external data source via an ODBC connection, make sure that the required ODBC driver is installed on the server.
A Credential store allows you to use passwords without showing the actual password. See Set up a Credential Store for a detailed description.
By default, an encrypted credential store is used. See Setting up an encrypted file-based credential store for more information.
<EXTRACTORDIR>\databases\ServerSettings.json
file.
- Introduction
- Using .mvp connectors
- Downloading DataBridgeAgent
- DataBridgeAgent
- Difference from an on-premises (standalone) installation
- Prerequisites
- Setup credentials for the SQL Server database
- Extracting data from an SAP source system
- Extracting data via loading .csv files
- Extracting data via an ODBC connection
- Using a credential store
- Next steps