- Release notes
- Before you begin
- Getting started
- Introduction to Process Mining
- Process Mining (Automation Suite)
- Architecture Overview
- Process Mining Portal
- Uploading app templates
- Migrating apps for use in Process Mining (Automation Suite)
- 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
Migrating apps for use in Process Mining (Automation Suite)
.mvp) and an app (.mvp). Moving to the new technology stack requires the main Process Mining standalone artifacts, apps, and connectors, to be migrated to a process app in Process Mining Automation Suite.
|
Process Mining standalone |
Process Mining Automation Suite |
|---|---|
|
|
Data transformations |
|
|
Dashboards |
.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. See Adding a Custom Connector to DataBridgeAgent and Loading Data Using DataBridgeAgent for a detailed description.
In Process Mining (Automation Suite) an app template contains a predefined set of dashboards and KPIs for process analysis that can be used as the starting point for creating your process apps. If available, an app template can include a built-in connector for a specific combination of a process and source system.
Process Mining offers out-of-the box app templates for several processes and source systems that you can use as the starting point for creating your process apps.
.mvp connectors and the corresponding app templates that should be used to load data from the existing .mvp connectors.
|
.mvp connector for |
App template |
|---|---|
|
TemplateOne |
TemplateOne-MultiFiles TemplateOne-SingleFile |
|
AppOne |
TemplateOne-MultiFiles TemplateOne-SingleFile |
|
Purchase-to-Pay Discovery Accelerator |
Purchase-to-Pay |
|
Order-to-Cash Discovery Accelerator |
Order-to-Cash |
.mvp connector to adjust the data to the data model for the Process Mining (Automation Suite) process app.
.mvp connector, the transformations have to be rewritten in a SQL-based language.
For more information on SQL-based transformations, see Editing data transformations in a local environment in Process Mining.
.mvp) connector in Process Mining (Automation Suite), all custom dashboards can be added step by step. Each custom dashboard can be recreated using the Dashboard Editor in Process Mining Automation Suite. See Creating a New App and Creating dashboards for more information.
.mvp app in the new dashboards in Process Mining (Automation Suite), these KPI expressions must be moved to the .mvp connector. In this way, the KPIs can be loaded into the new process app, in Process Mining (Automation Suite), as input data.
In Process Mining (Automation Suite) the data models of TemplateOne - MultiFiles,Purchase-to-Pay, and Order-to-Cash have custom case and event fields available, that can be used to get more detailed views in the process app.
Cost_per_case, you can use a custom field , such as custom_case_number_1. You can use the value of this field, for example, to calculate an average value in your process app.
