- Release notes
- Before you begin
- 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
- Root cause analysis
- Simulating automation potential
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- App Templates
- Migrating apps for the new process graph layout
- Editing apps
- Cloning an app
- Setting data restrictions for a process app
- Deleting an app
- Exporting and importing process apps
- Loading data
- Customizing process apps
- App templates
- Additional resources
- Out-of-the-box Tags and Due dates
- Editing data transformations in a local environment
- Setting up a local test environment
- Designing an event log
- Extending the SAP Ariba extraction tool
- Performance characteristics
Migrating apps for the new process graph layout
New Process Mining process apps now use the new layout technique called TRACY for process graphs. TRACY makes the process graph easy to understand, automatically identifying the main process flow and ordering the rest of the activities based on their execution sequence.
With the introduction of TRACY, all new process apps will use TRACY for the process graph layout. Process apps created with the previous process graph layout will no longer work in Process Mining 2023.10. Recreate or migrate your process apps before installing Process Mining 2023.10, to make sure the process apps are still accessible.
If your current version is Process Mining 2022.10, make sure you first install Process Mining 2023.4 and migrate your process apps using Process Mining 2023.4, before moving to Process Mining 2023.10.
If you have any existing process apps based on TemplateOne, Purchase-to-Pay, or Order-to-Cash app templates for which you have customized the transformations, you can migrate these process apps to use the new TRACY layout. Below is a description of the steps you need to perform if you want to migrate your process apps.
-
Create a new process app (using sample data) based on the same app template as your current process app.
-
Export the transformations from you current process app to download the current, customized app transformations.
-
Edit the transformations as described below.
-
Import the transformations in the new process app created in Step 1. to upload the updated transformation to the new process app.
Export the transformations from the new process app to check out the new default transformations of your process app.
In general, follow the steps as described in Editing data transformations in a local environment. Since specific settings are required when migrating to a new version, pay attention to the steps described below.
Make sure to edit the transformations you exported from your current process app. When done, import the transformations in the new process app based on the same app template as your current process app.
Make changes on the transformations as described below.
- Purchase-to-Pay: Purchase_order_item_end_to_end_events.sql
- Order-to-Cash: Sales_order_item_end_to_end_events.sql
-
Other app templates: Event_log.sql
- Change other logic using Event_throughput_time, if applicable.
- Remove the corresponding test from business_logic.yml file.
- The Event_order will be overwritten with the new version, so either remove the Event_order field completely, or keep using current Event_order field for logic within transformations.
- Add the Activity_order field.
- Remove the Event_order test from business_logic.yml file.
Default location in transformations:
- Purchase-to-Pay: Purchase_order_items.sql
- Order-to-Cash: Sales_order_items.sql
- Other app templates: Cases_log.sql
Steps in transformations:
1. Remove case throughput time and case start fields.
- Remove the following fields:
|
App template |
Field(s) |
|
Purchase-to-Pay |
Throughput_time_end_to_end |
|
Order-to-Cash |
Throughput_time_end_to_end |
|
Other app templates |
Throughput_time Case_start |
- Remove the corresponding tests from business_logic.yml.
2. Remove the Variant field.
- Remove the corresponding test from business_logic.yml file.
Default location in transformations:
- Purchase-to-Pay: Purchase_order_item_end_to_end_edges.sql
- Order-to-Cash: Sales_order_item_end_to_end_edges.sql
- Other app templates: Edges.sql
Steps in transformations:
As an optional step, you can remove the (deprecated) Events table. Note that this is not required to get the new process app working, but it will improve the performance of the new process app.
Default location in transformations:
- Purchase-to-Pay: N/A.
- Order-to-Cash: N/A.
- Other app templates: Events.sql
Steps in transformations:
-
Remove (deprecated) Events table (not available for Purchase-to-Pay and Order-to-Cash app templates).
If you are migrating an earlier version of a process app, for example, a process app created in Process Mining 2022.10, you may need to add tables or fields in your transformations to meet the new format of the app template.
For example, you may need to add a Due dates or a Tags model in your transformations.
Create a new process app based on the same app template as the current process app you want to migrate to test the transformations.
Select the option Use sample data in the Data source step when creating the test process app.
Create a new process app based on the same app template as the current process app you want to migrate and import the transformations.
Select the option Use sample data in the Data source step when creating the new process app.
