Migrating apps for use in Process Mining

Introduction

This page describes how to migrate apps from  Process Mining on-premises (standalone) to Process Mining Automation Cloud^TM. Process Mining on-premises (standalone) and Process Mining Automation Cloud^TM are built on a different technology stack. In Process Mining Automation Cloud^TM, 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 Cloud^TM.

Process Mining standalone	Process Mining Automation CloudTM
connector.mvp	Data transformations
app.mvp	Dashboards

Data transformations

In Process Mining, 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.

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, 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 Process Mining on-premises (standalone) .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	Event log Custom process
AppOne	Event log Custom process
Purchase-to-Pay	Purchase-to-Pay
Order-to-Cash	Order-to-Cash

Note: Although the data models of the app templates in Process Mining Automation Cloud^TM 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 Cloud^TM 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. In this way, Process Mining standalone is not needed anymore for editing data transformations.

For more information on SQL-based transformations, see Editing data transformations in a local environment.

Dashboards

After you create a new process app, that loads data from an existing (.mvp) connector, all custom dashboards can be added step by step. Each custom dashboard can be recreated using the Dashboard Editor. See Creating a new app and Creating dashboards for more information.

Note: Since Process Mining on-premises (standalone) has 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 Cloud^TM, these KPI expressions must be moved to the .mvp connector. In this way, the KPIs can be loaded into the new process app as input data.

Custom Fields

If you need a calculated value for a KPI, for example Cost_per_case, you can add a custom field. You can use the value of this field, for example, to calculate an average value in your process app.