Migrating apps for use in Process Mining (Automation Suite)

Introduction

This page describes how to migrate apps from  UiPath Process Mining on-premises (standalone) to Process Mining on-premises (Automation Suite). Process Mining standalone and Process Mining Automation Suite are built on a different technology stack. In Process Mining Automation Suite, both data transformations and dashboards are combined in a single process app. In Process Mining standalone, data transformations and dashboards are separated in a connector (.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
connector.mvp	Data transformations
app.mvp	Dashboards

Data transformations

In Process Mining (Automation Suite), an existing Process Mining on-premises (standalone) connector (.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).

DataBridgeAgent

You can add the .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.

App templates

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.

Below is an overview of the .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

Note: Although the data models of the app templates in Process Mining (Automation Suite) are similar to the data models of the app in Process Mining on-premises (standalone), you may have to make small changes in the existing .mvp connector to adjust the data to the data model for the Process Mining (Automation Suite) process app.

SQL-based transformations

To migrate the contents of an existing .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.

Dashboards

After you create a new process app in Process Mining (Automation Suite), that loads data from an existing (.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.

Note: Since Process Mining on-premises (standalone) and Process Mining (Automation Suite) have a different technology stack, there are differences in the types of dashboards that can be created, and the specific features to configure them. It might not be possible to recreate a dashboard exactly as it is in Process Mining on-premises (standalone).

Migrating custom expressions

To use KPI expressions, that were previously defined inside a .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.

Custom Fields

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.

Example: If you need a calculated value for a KPI, for example 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.

• Order-to-Cash input fields.
• Purchase-to-Pay input fields.
• TemplateOne-SingleFile Input Fields.
• TemplateOne-MultiFiles Input Fields.