process-mining
latest
false
- Release notes
- Before you begin
- Managing access
- 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
- Process simulation
- Root cause analysis
- Simulating automation potential
- Starting a Task Mining project from Process Mining
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- Loading data
- Transforming data
- Autopilot™ for SQL (preview)
- Structure of transformations
- Tips for writing SQL
- Exporting and importing transformations
- Viewing the data run logs
- Merging event logs
- Configuring Tags
- Configuring Due dates
- Configuring fields for Automation potential
- Activity Configuration: Defining activity order
- Making the transformations available in dashboards
- Data models
- Adding and editing processes
- Customizing process apps
- Publishing process apps
- App templates
- Notifications
- Additional resources
Process Mining
Last updated Nov 19, 2025
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.zipfile for your app template. Thisextract_theobald.zipfile contains theextract_theobald.ps1script and theconfig.jsonfile. -
Unzip the content of the
extract_theobald.zipfile on the server where Theobald Xtract Universal is installed. -
Configure the variables for the script in the
config.jsonas listed in the following table.
|
Variable |
Description |
|---|---|
|
|
The Xtract Universal installation folder. This is the folder where you can find the
xu.exe. For example: C:\\MyFolder.
|
|
|
Address of the server where Xtract Universal is installed. The default is
localhost.
|
|
|
Port of the server where Xtract Universal is installed. The default port of an installation is
8065.
|
|
|
The SAS uri of the Azure blob storage to which the extracted data needs to be uploaded. Refer to Retrieving the credentials for the Azure blob storage. |
|
| The API that is called to start data processing in Process Mining, once all data has been uploaded. |
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_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:
|
|
|
The language in which data is extracted from the source system. The default is
E.
|
|
|
The exchange rate type that is used for currency conversion. The default is
M.
|
|
|
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.
|
process_code | Defines the prefix of the extraction name that is used for the extraction in Theobald. You can accept the default value. |
extraction_type | Defines the extraction type used for the extraction. Possible values: full, incremental.
Note: Check out Incremental extraction for more information on how to configure incremental extraction for Theobald Xtract Universal.
|
extraction_tables_incremental | Enables you to specify the tables used for incremental extraction.
Important: Make sure to configure incremental extraction for the (transactional) tables in Xtract Universal Designer and in the input
data mapping in Process Mining. Check out Incremental extraction for more information.
Note:
|
*) 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.
