- Overview
- Getting started
- Building models
- Consuming models
- Model Details
- Public endpoints
- 1040 - document type
- 1040 Schedule C - document type
- 1040 Schedule D - document type
- 1040 Schedule E - document type
- 1040x - document type
- 3949a - document type
- 4506T - document type
- 709 - document type
- 941x - document type
- 9465 - document type
- ACORD125 - document type
- ACORD126 - document type
- ACORD131 - document type
- ACORD140 - document type
- ACORD25 - document type
- Bank Statements - document type
- Bills Of Lading - document type
- Certificate of Incorporation - document type
- Certificate of Origin - document type
- Checks - document type
- Children Product Certificate - document type
- CMS 1500 - document type
- EU Declaration of Conformity - document type
- Financial Statements - document type
- FM1003 - document type
- I9 - document type
- ID Cards - document type
- Invoices - document type
- Invoices2 - document type
- Invoices Australia - document type
- Invoices China - document type
- Invoices Hebrew - document type
- Invoices India - document type
- Invoices Japan - document type
- Invoices Shipping - document type
- Packing Lists - document type
- Payslips - document type
- Passports - document type
- Purchase Orders - document type
- Receipts - document type
- Receipts2 - document type
- Receipts Japan - document type
- Remittance Advices - document type
- UB04 - document type
- US Mortgage Closing Disclosures - document type
- Utility Bills - document type
- Vehicle Titles - document type
- W2 - document type
- W9 - document type
- Supported languages
- Insights dashboards
- Document Understanding deployed in Automation Suite
- Data and security
- Logging
- Licensing
- How to
- Troubleshooting
Document Understanding Modern Projects User Guide
This page describes how to deploy and configure Document UnderstandingTM, as well as special instructions on how to use Document UnderstandingTM on Automation Suite.
Document Understanding has a dependency on AI Center, meaning that AI Center always needs to be installed if Document Understanding is installed.
Also, Orchestrator must be activated before using Document Understanding.
Before starting the Document Understanding installation, make sure to check and satisfy all requirements for Automation Suite for single-node and for multi-node here.
A GPU is strongly recommended for Document Understanding in one of the following scenarios:
-
If you retrain the Document Understanding models (DocumentUnderstanding - the general model, Invoices, Receipts, etc.) on AI Center.
Training on CPU is 5-7 times slower and model performance degrades compared to training on GPU.
-
If you run UiPathDocumentOCR (non-edge version) on AI Center to process more than 2 million pages a year.
If you do not use a GPU, slow performance may impact the product experience.
For more details about how to provision a GPU, check the Adding a dedicated agent node with GPU support page.
Document Understanding requires the FullTextSearch feature to be enabled on the SQL server. Otherwise, the installation fails without an explicit error message.
Configuration file
Check the Document Understanding configuration file here.
Access to the models
Access Form Extractor and Intelligent Keyword Classifier, with the following public URL:
<FQDN>/du_/svc/formextractor<FQDN>/du_/svc/intelligentkeywords
<FQDN> placeholder with the actual environment information.For example <FQDN>/du_/svc/formextractor becomes https://servicefabricserver.domain.com/du_/svc/formextractor when used in a workflow.
Enable or disable Document Understanding
As a post-installation operation, you can enable or disable Document Understanding. More details can be found here.
Enable or disable UiPath Extended Languages OCR
To enable or disable the Extended Languages OCR, check the instructions from the Automation Suite Admin Guide.
Troubleshooting
Check the Document Understanding-related issues here.
