- Release notes
- Getting started
- Installation
- Configuration
- Integrations
- Authentication
- Working with Apps and Discovery Accelerators
- AppOne menus and dashboards
- AppOne setup
- TemplateOne 1.0.0 menus and dashboards
- TemplateOne 1.0.0 setup
- TemplateOne menus and fashboards
- TemplateOne 2021.4.0 setup
- Purchase to Pay Discovery Accelerator menus and dashboards
- Purchase to Pay Discovery Accelerator Setup
- Order to Cash Discovery Accelerator menus and dashboards
- Order to Cash Discovery Accelerator Setup
- Basic Connector for AppOne
- SAP Connectors
- Introduction to SAP Connector
- SAP input
- Checking the data in the SAP Connector
- Adding process specific tags to the SAP Connector for AppOne
- Adding process specific Due dates to the SAP Connector for AppOne
- Adding automation estimates to the SAP Connector for AppOne
- Adding attributes to the SAP Connector for AppOne
- Adding activities to the SAP Connector for AppOne
- Adding entities to the SAP Connector for AppOne
- SAP Order to Cash Connector for AppOne
- SAP Purchase to Pay Connector for AppOne
- SAP Connector for Purchase to Pay Discovery Accelerator
- SAP Connector for Order-to-Cash Discovery Accelerator
- Superadmin
- Dashboards and charts
- Tables and table items
- Application integrity
- How to ....
- Working with SQL connectors
- Introduction to SQL connectors
- Setting up a SQL connector
- CData Sync extractions
- Running a SQL connector
- Editing transformations
- Releasing a SQL Connector
- Scheduling data extraction
- Structure of transformations
- Using SQL connectors for released apps
- Generating a cache with scripts
- Setting up a local test environment
- Separate development and production environments
- Useful resources
Compliance - Due Dates
The Compliance – Due dates dashboard displays information regarding activities not meeting deadlines.
Due dates table must be loaded in TemplateOne. See Input tables of TemplateOne - Due dates.
In UiPath Process Mining, a due date is defined as an activity that needs to occur before a specified date. Due dates are used to get information regarding cases meeting or not meeting deadlines and the related costs. Due dates can be predefined to set a significant stage or activity deadline in your processes.
A due date checks the difference between the Actual date of the event and the Expected date of the event.
The Actual date is defined as the date when the event actually takes place. To create a proper due date, you should also define the Expected date for the due date, which is the date when the event is expected to take place. The Days late expression calculates the difference between the Actual date and the Expected date.
The context bar at the top of the Compliance - Due dates dashboard displays context information and KPI's.
Below is a description of the elements of the context bar.
|
Element |
Description |
|---|---|
|
Average days late |
The average number of days that it took to complete events after the expected end date. |
|
Percentage of late events |
The percentage of events that were completed after the expected end date within the selected period. |
|
Number of events |
The total number of events. |
|
Number of cases |
The total number of cases. |
Below is a description of the metrics that can be selected in the Is the due date being met on time? dashboard item. See the illustration below.
Below is a description of the metrics.
|
Metric |
Description |
|---|---|
|
Avg. days late |
The average number of days that it took to complete events after the expected end date. |
|
Percentage late |
The percentage of events that were completed after the expected end date within the selected period. |
