Document Understanding
latest
false
- Overview
- Getting Started
- Activities
- Insights Dashboards
- Document Understanding Process
- ML Packages
- Overview
- 1040 - ML Package
- 1040 Schedule C - ML Package
- 1040 Schedule D - ML Package
- 1040 Schedule E - ML Package
- 4506T - ML Package
- 990 - ML Package - Preview
- ACORD125 - ML Package
- ACORD126 - ML Package
- ACORD131 - ML Package
- ACORD140 - ML Package
- ACORD25 - ML Package
- Bank Statements - ML Package
- BillsOfLading - ML Package
- Certificate of Incorporation - ML Package
- Certificate of Origin - ML Package
- Checks - ML Package
- Children Product Certificate - ML Package
- CMS 1500 - ML Package
- EU Declaration of Conformity - ML Package
- Financial Statements - ML Package
- FM1003 - ML Package
- I9 - ML Package
- ID Cards - ML Package
- Invoices - ML Package
- Invoices Australia - ML package
- Invoices China - ML package
- Invoices India - ML package
- Invoices Japan - ML package
- Invoices Shipping - ML Package
- Packing Lists - ML Package
- Payslips - ML Package
- Passports - ML Package
- Purchase Orders - ML Package
- Receipts - ML Package
- RemittanceAdvices - ML Package
- UB04 - ML Package
- Utility Bills - ML Package
- Vehicle Titles - ML Package
- W2 - ML Package
- W9 - ML Package
- Public Endpoints
- Licensing
PREVIEW
Document Understanding User Guide for Modern Experience
Last updated Apr 26, 2024
Monitor
You can check the performance metrics for your automation from the Monitor section.
The Project performance tab provides useful performance metrics for your project, such as the the number of processed documents, the time saved processing documents, or the time saved extracting data from documents. These metrics require Insights to be enabled and are displayed in the form of an Insights dashboard.
Note: Orchestrator data is ingested approximately every 20 minutes.
Robot logs will be ingested every 10-15 minutes, but due to latency this can take up to
2 hours to be displayed in Insights. Please note that all Robot logs are ingested, not
only the last records and errors. For more information, check the Data Ingestion for Insights section from the
Insights User Guide.
The Processed Documents tab provides a list of documents which have been processed with
the selected project, either via APIs or the activities part of the
UiPath.DocumentUnderstanding.Activities package. If the document has at least
been digitized via APIs or in any way processed via the activities referencing the
project, it will appear here. The following metrics are available:
- File name: the name of the processed document. Click the document name to go to the Document Details view.
- Document type: the document type of the processed document.
- Consumer:
- API: consumer which has digitized at least one page using the selected project. Hover your mouse over the field to view the AppId, configured when setting up the external application, to uniquely identify the consumer.
- RPA: Studio Desktop or Studio Web projects containing at least one Document Understanding activity referencing the current project. Hover your mouse over the field to view the process name.
- Modified Date: date when the last operation on the document occurred.
- Validator: username of the user who validated the task. If there is no validation task created for the respective document, N/A will be displayed in the field.
- AI Units: number of AI Units consumed.
Use the search bar to search for a processed document by file name.
Click on a file name from the Processed Documents tab to get to the Document
Details view. This view provides the following information:
- Metrics:
- Total consumption: the number of AI Units consumed by the document.
- Creation date: the date when the document was created.
- Last updated date: the date the last operation on the document occurred.
- Consumer: the name of the workflow created in an RPA project.
- Classification:
- Pre-validation document type: the document type determined automatically by the classifier.
- Post-validation document type: if changed manually, the document type after validation. If the document type was not changed after validation, the value will be N/A.
- Confidence: the confidence score determined by the classifier.
- Extraction:
- Model: the extraction model used.
- Extracted fields:
information related to each field of the document type:
- Predicted value: the value predicted by the model.
- Extraction confidence: the confidence score determined by the extractor.
- OCR Confidence: the confidence score determined by the OCR engine.
- Post-validation value: if changed manually, the value after validation. If the document type was not changed after validation, the value will be N/A.
- Validation:
- Task name: the name of the validation task.
- Task type: the type of the validation task. Possible values: Classification or Extraction.
- Task catalog name: the name of the validation task catalog.
- Assignee: the assignee of the validation task (Unassigned if there is no user assigned yet).
- Criticality: the priority level of the validation task.
- Task creation date: the date when the validation task was created.
- Task completion date: the date when the validation task was completed.
- Valid fields: the number of validated fields after human-in-the-loop (marked as valid).
- Modified fields: the number of modified fields after human-in-the-loop.
- Task outcome: the result of the task.
