process-mining
latest
false
- 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
- Starting a Task Mining project from Process Mining
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- Loading data
- Customizing process apps
- Publishing process apps
- App templates
- Additional resources
Data model requirements
Process Mining
Data model requirements
A data model can only be saved when it adheres to the following requirements:
- The data model includes no more than 40 tables.
- 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.
Tip:
A direction change is a one-to-many relation followed by a many-to-one relation, or vice versa.
Important:
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.
A data model must have a
Cases
, Event_log
, Tags
, and Due_dates
table.
Note:
Depending on the app template, the
Cases
table has a process-specific name, for example, Purchase_order_items
, or Incidents
.
The
Cases
, Event_log
, Tags
, and Due_dates
table must have the following output fields.
Note:
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
.