process-mining

2023.10

false

Release notes
- 2023.10.12
- 2023.10.11
- 2023.10.10
- 2023.10.9
- 2023.10.8
- 2023.10.7
- 2023.10.6
- 2023.10.5
- 2023.10.4
- 2023.10.3
- 2023.10.2
- 2023.10.1
- 2023.10
Before you begin
- Installing Automation Suite
- Process Mining configuration checklist
- System requirements
Getting started
- Introduction to Process Mining
- Process Mining
- Architecture overview
- Process Mining portal
- Uploading app templates
- Migrating apps for use in Process Mining
- Managing access
  - Enabling Process Mining
  - Setting up the users
  - Managing access for process apps
Integrations
- Setting up Automation integration
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
- App Templates
- Migrating apps for the new process graph layout
- Create new app wizard
  - Scenarios
- Editing app settings
  - Setting data restrictions for a process app
- Cloning an app
- Deleting an app
- Exporting and importing process apps
Loading data
- Uploading data
- Retrieving the SQL Server database parameters
- Setting up a SQL Server account for data upload using an extractor
- Loading data using CData Sync
  - Installing CData Sync
  - Create a source connection
  - Create a destination connection
  - Create a job
  - Run the job
  - Incremental extraction
  - Troubleshooting CData Sync
- Loading data using Theobald Xtract Universal
  - Setting up Theobald Xtract Universal
  - Importing the template extractions
  - Configuring the source
  - Configuring the destination
  - Configuring the extraction script
  - Running the extraction script
  - Troubleshooting
- Viewing logs
- Optimizing an app
- Scheduling Data Runs
Customizing process apps
- Introduction to dashboards
- Working with the dashboard editor
- Creating dashboards
- Dashboards
- Charts
  - Bar charts
  - Distribution charts
  - Table charts
  - Line charts
  - Process graphs
  - KPI trends lists
  - Pie charts
- Data manager
  - Fields
  - Metrics
- Automation manager
- Data transformations
  - Defining new input tables
  - Adding fields
  - Adding tables
  - Data model requirements
  - Viewing and editing the data model
  - Exporting and importing transformations
  - Viewing the transformations log
  - Editing and testing data transformations
  - Structure of transformations
  - Tips for writing SQL
  - Merging event logs
- Process manager
Publishing Dashboards
App templates
- Event log and Custom process app templates
  - Overview of generic menus and dashboards
  - Menu Overview
  - Menu Analysis
    - Analysis - End to end
    - Analysis - Event analysis
  - Event log input fields
  - Custom process input fields
  - Configuring CData Sync for Event log or Custom process
- Purchase-to-Pay app template
  - Introduction to Purchase-to-Pay Process App
  - Overview of menus and dashboards
  - Menu Summary
  - Menu Analysis
    - Analysis - End to end process
    - Analysis - Event analysis
  - Menu Efficiency
    - Efficiency - Supplier performance
  - Menu Compliance
    - Compliance - Maverick buying
  - Purchase-to-Pay input fields
  - Configuring CData Sync for Purchase-to-Pay
- Order-to-Cash app template
  - Introduction to Order-to-Cash Process App
  - Overview of menus and dashboards
  - Menu Summary
  - Menu Analysis
    - Analysis - End to end process
    - Analysis - Event Analysis
  - Menu Efficiency
    - Efficiency - Customers
  - Order-to-Cash input fields
  - Configuring CData Sync for Order-to-Cash
Additional resources
- Out-of-the-box Tags and Due dates
- Editing data transformations in a local environment
- Setting up a local test environment
- Transformations
  - Custom throughput time metrics
  - SQL differences between Snowflake and SQL Server
  - Configuration settings for loading input data
- Designing an event log
- Loading data using DataBridgeAgent
  - Introduction
    - Using .mvp Connectors
    - Downloading DataBridgeAgent
  - DataBridgeAgent
  - 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
  - System requirements
  - Configuring DataBridgeAgent
  - Adding a custom connector to DataBridgeAgent
  - Using DataBridgeAgent with SAP Connector for Purchase-to-Pay Discovery Accelerator
  - Using DataBridgeAgent with SAP Connector for Order-to-Cash Discovery Accelerator
- Extending the SAP Ariba extraction tool
- Performance characteristics
- Basic troubleshooting guide
  - How to cancel a data run from the database
  - How to add an IP table rule to use SQL Server port 1433
  - When creating a process app the status stays in Creating app
  - Configuring Dapr with Redis in cluster mode
  - Data transformations
  - Uploading data
  - CData Sync

Process Mining

DELIVERY:

Last updated Jan 15, 2026

Configuring the extraction script

Follow these steps to configure the extraction script.

Go to the App Templates page and open the documentation page for your app template.
Locate the section Loading data using Theobald Xtract Universal and download the extract_theobald_as.zip file for your app template. This extract_theobald_as.zip file contains the extract_theobald.ps1 script and the config.json file.
Unzip the content of the extract_theobald_as.zip file on the server where Theobald Xtract Universal is installed.
Configure the variables for the script in the config.json as listed in the following table.

Variable	Description
`xu_location`	The Xtract Universal installation folder. This is the folder where you can find the `xu.exe`. For example: C:\\MyFolder.
`xu_server`	Address of the server where Xtract Universal is installed. The default is `localhost`.
`xu_port`	Port of the server where Xtract Universal is installed. The default port of an installation is `8065`.
`end_of_upload_api`	The API that is called to start data processing in Process Mining, once all data has been uploaded. Refer to Retrieving the SQL Server database parameters .
`extraction_start_date`^*	Start date to be used to limit extractions. Only tables where a date filter is applied are filtered on this date. Format is `YYYYMMDD`. The default is no limitation indicated by the start date `19700101`. Note: `extraction_start_date` must have a value. all events that happened before `extraction_start_date` will be excluded from the extracted data.
`extraction_end_date`^*	End date to be used to limit extractions. Only tables where a date filter is applied are filtered on this date. Format is `YYYYMMDD`. The default is no limitation indicated by the end date `20991231`. Note: `extraction_end_date` must have a value. all events that happened after `extraction_end_date` will be excluded from the extracted data.
`language`	The language in which data is extracted from the source system. The default is `E`.
`exchange_rate_type`	The exchange rate type that is used for currency conversion. The default is `M`.
`is_sap_hana`	Specifies if the source system is SAP HANA. Other versions of SAP might give errors in the extraction because of clustered tables. The default value is `true`.

*) To achieve a more complete overview of all events, it is recommended to set extraction_start_date and extraction_end_date so that the interval exceeds twice the known throughput time of the business process.

Was this page helpful?

PREVIOUSConfiguring the destination

NEXTRunning the extraction script