- 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
- Loading data
- Customizing process apps
- Publishing Dashboards
- 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
Data model requirements and structural constraints for process apps in Process Mining on Automation Suite, including table limits and relation rules.
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 15 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.
Required output tables
A data model must have a Cases, Event_log, Tags, and Due_dates table.
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.
All the fields are required. However, some fields are allowed to contain only NULL values.
| Table | Required output field |
|---|---|
Cases | Case_ID* |
Event_log | Case_ID* |
Event_start | |
Event_end | |
Activity | |
Activity_order | |
Automated | |
Event_cost | |
Event_processing_time | |
Tags | Tag_ID |
Case_ID* | |
Tag | |
Tag_type | |
Due_dates | Case_ID* |
Due_date | |
Due_date_type | |
Actual_date | |
Expected_date | |
On_time | |
Cost | |
Difference |
*) Depending on the app template, Case_ID can be called differently, for example, Purchase_order_item_ID, or Incident_ID.