- Release notes
- Before you begin
- Managing access
- 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
- Starting a Task Mining project from Process Mining
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- Loading data
- Transforming data
- Data models
- Adding and editing processes
- Customizing process apps
- Publishing process apps
- App templates
- Notifications
- Additional resources

Process Mining
Data models
Currently, multi-process Process Mining is only available for newly created apps. Apps created before multi-process Process Mining was released will not see Object and Event tables.
Table type |
Description |
Example |
Object | Things that a process interacts with. | Invoices, Incident tickets, Products. |
Events | Steps performed on objects. | "Create invoice", "Assign ticket", "Assemble product" |
If you define multiple Event tables in your data model, the events will be available in Data Manager in a single Events table.
- The data model includes no more than 40 tables.
-
The data model contains at least one object table and a related events table.
-
Each Events, Tags, and Due date table is connected to only one related object table.
- All tables are connected to the overall data model.
- There are no circular relations in the data model.
- A maximum of four direction changes are allowed in one relation path.
A direction change is a one-to-many relation followed by a many-to-one relation, or vice versa.
If you require a larger data model than the "Max four direction changes" limitation allows, contact UiPath® Customer Support to turn off the limitation for your organization.
Note that turning this limitation off might have a performance implication for your dashboards.
Object tables
Each object in your data model has its own Object table in Data Transformations. An Object table contains the fields that have been defined specifically for that object.
Process tables
Each process defined in your data model has its own Process table with the projected events for that process. The following fields are always present in the event tables:
-
Process_event_ID
, unique ID for each record in the process table. -
Event_ID
, unique for each individual event, regardless of in which process it's used. In the example below,event_ID 1
occurs twice in the process table. -
Throughput_time
, time from previousEvent_end
to the currentEvent_end
. -
Cycle_time
*, time fromEvent_start
toEvent_end
.
Cycle_time
is only available if the events have an Event_start
defined.
The following illustration shows an example Process table containing the events for the P2P_process.
PO_ID
).
Tags table
Tags
table contains the tags data for all the tags in your dataset. Depending on your data model, one or more ID fields can be
available in the Tags
table. If your data model consists of multiple objects that each have an associated Tags
table, these Tags
tables are consolidated in a single Tags
table in Data Manager
.
-
Tag_ID
-
Tag_name
-
Tag_type
-
<Object>_ID
Due dates table
Due dates
table contains the due dates timestamps for all the due dates in your dataset. Depending on your data model, one or more
ID fields can be available in the Due dates
table. If your data model consists of multiple objects that each have an associated Due dates
table, these Due dates
tables are consolidated in a single Due dates
table in Data Manager
.
-
Due_date_ID
-
Due_date
-
Due_date_type
-
Actual_date
-
Expected_date
-
On_time
-
Cost
-
Difference
-
<Object>_ID
The information in this section is only applicable to apps that employ a single process, in other words, apps that were created before the release of multi-process Process Mining.
Cases
, Event_log
, Tags
, and Due_dates
table.
Cases
table has a process-specific name, for example, Purchase_order_items
, or Incidents
.
Cases
, Event_log
, Tags
, and Due_dates
table must have the following output fields.
All the fields are required. However, some fields are allowed to contain only NULL values.
Table |
Required output field |
|
Case_ID *
|
|
Case_ID *
|
| |
| |
| |
| |
| |
| |
| |
|
|
Case_ID *
| |
| |
| |
|
Case_ID *
|
| |
| |
| |
| |
| |
| |
|
Case_ID
can be called differently, for example, Purchase_order_item_ID
, or Incident_ID
.
Always make sure your data model adheres the requirements. Check out Data model requirements.
-
Locate the Output section in Data transformations and select Data model to view the data model of your process app.
Check out Editing data transformations for more information on how to change the data model.
Refer to Data model requirements for details.
Make sure there is an input table for the object you want to add and that the object is defined in models -> 2_objects in the Transformations section of Data transformations.
Follow these steps to add a table.
-
Select + Add table. The Add table dialog is displayed.
-
Select the type of table that you want to add from the Type list.
-
Select the Table that defines the new output table.
-
Select the Primary key for the new table.
-
Define the additional properties for the table.
Note:Depending on the type of the table, different properties may be requested.
-
Add the relations for the table and select Add table.
Additional properties for Events tables
It is advised to either have a separate Events table per activity or an Events table per object. For example, opportunity_create_events, and opportunity_approve_events, etc, or opportunity_events table.
The following table describes the properties you need to specifiy when adding an Events table.
Property |
Description |
Mandatory Y/N |
|
The unique identifier of the event. |
Y |
| The field that contains name of the event. This describes the step in the process. |
Y |
| The fields that contains timestamp associated with the start of executing the event. |
N |
| The field that contains the timestamp associated with the end of executing the event. |
Y |
| The field that contains the user who executed the event. |
N |
| The field that contains indicates whether the event is manually executed or automated. |
N |
| The field that contains the order of the events.
|
N |
| The field that contains t
he time for executing the event (in milliseconds). |
N |
| The fields that contains the costs for executing the event. |
N |
| The fields that is used to define a parent-child relationship between events, that can be used to create a structured process hierarchy. |
N |
Make sure there is an input table for each event table and that the events are defined in models -> 3_events in the Transformations section of Data transformations.
Follow these steps to delete a table.
-
Select the table that you want to delete in the data model editor.
The Edit table panel is displayed.
-
Select Delete table.
A confirmation message is displayed.
-
Select Delete to continue.
The table and the relations are deleted from the data model.
-
Select the table that you want to relate to another table.
The Edit table panel is displayed.
-
In the Edit table panel, locate the Relations section.
-
Select + Add new to create a new relation.
-
Select the field that you want to use in this table from the Key list.
-
Select the Table you want to connect to and select the field that use to connect from the Key list.
-
Select Apply.
Follow these steps to delete a relation.
-
Select the table for which you want to delete an outgoing relation.
The Edit table panel is displayed.
-
In the Edit table panel, locate the relation you want to delete and select Delete relation.
-
Select Apply.
-
Select the table for which you want to change the primary key.
The Edit table panel is displayed.
-
In the Edit table panel, locate the relation for which you want to change the primary key.
-
Select the new field that is to be used as the Primary key to join the tables.
-
Select Apply.
null
.
Follow these steps to make the changes to the data model available in dashboards.
-
Select Save to save the data model.
-
Select Apply to dashboards to run the transformations and make new the table available for use in dashboards.
Note:This may take several minutes. If the run finishes successfully, the changes to the data model will show up in the Data Manager.
The Save option is only enabled, after you made any changes to the data model.
You can select a table to see the fields and the data contents in the Preview panel. The data preview enables you to check if the data looks as expected.
The Preview panel shows the data of the last data run in which this table was recalculated. If you have made recent changes, then start a new data run to view its results, refer to Editing data transformations.
Selecting visible columns
You can select the columns you want to display in the Preview panel.
Follow these steps to change the visible columns.
Step | Action |
---|---|
1 |
Select Columns to display the list of columns. |
2 |
Select the columns you want to display in the Preview panel from the list. |
- Data model requirements
- Types of tables
- Required output tables
- Viewing and editing the data model
- Validation checking
- Filtering types of tables
- Adding tables
- Deleting a table
- Adding relations
- Deleting a relation
- Changing the primary key for a table
- Making the updated data model available in dashboards
- Preview panel