- Overview
- Getting started
- Activities
- Insights dashboards
- Document Understanding Process
- Document Understanding Process template
- 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
- 1040x - ML package
- 3949a - ML package
- 4506T - ML package
- 709 - ML package
- 941x - ML package
- 9465 - 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 Hebrew - 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
- 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
- Traffic limitations
- OCR Configuration
- Pipelines
- OCR services
- Supported languages
- Deep Learning
- Licensing
Document Understanding User Guide
Document Understanding Process template
Document Understanding Process is a fully functional UiPath® Studio project template based on a document processing flowchart. You can use it to get started with working on either a demo, or a large-scale implementation of Document UnderstandingTM.
The process provides logging, exception handling, retry mechanisms, and all the methods that should be used in a Document Understanding workflow, out of the box.
- Windows – This framework uses the IntelligentOCR activity package, designed for Windows projects.
- Cross-platform – This framework uses the DocumentUnderstanding activity package, designed for Cross-platform projects.
The process has an architecture decoupled from other connected automations:
- It does not matter where the files to be processed are coming from or what triggers the execution, this is the responsibility of an upstream process;
- It does not matter where the extracted information should be used, this is the responsibility of a downstream process.
The process has the same architecture for scenarios using both attended robots, and unattended robots running Document Understanding, that have human in the loop validation via Action Center.
Items are not processed in bulk. Instead, there is one job for each input file. A dispatcher is required for processing every item, but this flexible approach helps you get started, develop, debug, and scale Document Understanding processes.
The Document Understanding Process template only supports Visual Basic projects.
- Windows:
- Cross-platform:
You can find the Document Understanding Process template on the official template feed. Navigate to the Templates tab and click the Document Understanding Process card.
Select Use Template.
Enter a Name for your process and choose a Location on your PC. For Compatibility, select the type of project compatibility you want the template to have. Each compatibility type uses a different activity package for its framework. Lastly, select Create to open the process.
The process comes with detailed documentation included in the project folder. We recommend you to read the enclosed User Guide even if you are familiar with the Document Understanding solution.
You can contribute directly to the project by making a pull request or by opening an issue in our repository here. If you want to create a new branch, please be aware of the naming conventions in the README.md file.
