- 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
- 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
Out-of-the-box Tags and Due dates
Below is an overview of the Tags that are available for Order-to-Cash related app templates.
The Sales order item with late payments tag identifies Sales order items that have an invoice linked to them which in turn was paid late.
Actual date
or Expected date
cannot be determined, the Expected payment due date will not show up in the Due dates dashboard.
Payments.Payment_is_complete = true
) are taken into account.
Below is an overview of the Due dates that are available for Purchase-to-Pay related app templates.
Actual date
is based on moment of the Create payment or Create outgoing payment event. The Expected date
for the due date is defined based on the Invoices_base.Baseline_date
with the Invoices_base.Net_payment_period
added to it.
Actual date
or Expected date
cannot be determined, the Expected payment due date will not show up in the Due dates dashboard.
Payments.Payment_is_complete = true
) are taken into account.
The PR to PO throughput time due date allows you to analyze the time it takes to between creating a purchase requisition and the creation of the purchase order item.
Actual date
is the Create purchase order item event, the Expected date
is based on the Create purchase requisition event combined with the standard deviation of all known throughput times between PR and PO.
Below is an overview of the Due dates that are available for Order-to-Cash related app templates.
Actual date
is based on moment of the Create incoming payment event. The Expected date
for the due date is defined based on the Invoices_base.Baseline_date
with the Invoices_base.Net_payment_period
added to it.
Actual date
or Expected date
cannot be determined, the Expected payment due date will not show up in the Due dates dashboard.
Payments.Payment_is_complete = true
) are taken into account.
The Expected delivery due date allows you to analyze whether deliveries are done in time or not.
Actual date
is based on the Deliveries.Delivery_date
and the expected date is the Deliveries.Planned_delivery_date
.
Actual date
or Expected date
cannot be determined, the Expected delivery due date will not show up in the Due dates dashboard.