process-mining
2023.4
false
- Release notes
- Before you begin
- Getting started
- Integrations
- Managing access
- Working with process apps
- Creating 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 Theobald Xtract Universal
- Customizing process apps
- Data transformations
- TemplateOne app template
- Purchase to Pay app template
- Order to Cash app template
- Basic troubleshooting guide
Process Mining
Last updated Oct 17, 2024
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
