- Overview
- Document Understanding Process
- Quickstart tutorials
- Framework components
- ML packages
- Overview
- Document Understanding - ML package
- DocumentClassifier - ML package
- ML packages with OCR capabilities
- 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
- Bills Of Lading - 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
- Passports - ML package
- Payslips - ML package
- Purchase Orders - ML package
- Receipts - ML Package
- Remittance Advices - ML package
- UB04 - ML package
- Utility Bills - ML package
- Vehicle Titles - ML package
- W2 - ML package
- W9 - ML package
- Other Out-of-the-box ML Packages
- Public Endpoints
- Hardware requirements
- Pipelines
- Document Manager
- OCR services
- Deep Learning
- Document Understanding deployed in Automation Suite
- Document Understanding deployed in AI Center standalone
- Licensing
- Activities
- UiPath.Abbyy.Activities
- UiPath.AbbyyEmbedded.Activities
- UiPath.DocumentProcessing.Contracts
- UiPath.DocumentUnderstanding.ML.Activities
- UiPath.DocumentUnderstanding.OCR.LocalServer.Activities
- UiPath.IntelligentOCR.Activities
- UiPath.OCR.Activities
- UiPath.OCR.Contracts
- UiPath.OmniPage.Activities
- UiPath.PDF.Activities
About pipelines
Document UnderstandingTM ML packages can run all three types of pipelines:
Once completed, a pipeline run has associated outputs and logs. To see this information, in the Pipelines tab from the left sidebar, click a pipeline to open the Pipeline view which consists of:
- the Pipeline details such as type, ML Package name and version, dataset, GPU usage, parameters, and execution time
- the Outputs pane; this always includes a
_results.jsonfile containing a summary of the Pipeline details - the Logs page; the logs can also be obtained in the ML Logs tab from the left sidebar
Training pipelines or Full pipelines can also be used to:
- Fine-tune ML models with data from Validation Station
Training:
Training a model from scratch, i.e. using the DocumentUnderstanding ML Package in AI Center.
Retraining:
Training using a pre-trained base-model, i.e. using one of the other document extraction ML packages in AI Center such as Invoices, Receipts, Purchase Orders, etc.
Auto-retraining:
This is the name of an environment variable which can be set when creating a Pipeline in AI Center which enables the pipeline to automatically use the most recent exported dataset for training. This variable is independent of whether that dataset includes data from Validation Station or not.
Fine-tuning:
Training or retraining a model using a dataset which includes data coming from Validation Station.
Auto-Fine-tuning:
Using the Auto-retraining environment variable feature to automatically train a model using data fed in from Validation Station using the Scheduled Export feature of Document Manager.
