- Overview
- Document Understanding Process
- Quickstart Tutorials
- Framework Components
- ML Packages
- Pipelines
- Document Manager
- OCR Services
- Document Understanding deployed in Automation Suite
- Document Understanding deployed in AI Center standalone
- Deep Learning
- Licensing
- References
- UiPath.Abbyy.Activities
- UiPath.AbbyyEmbedded.Activities
- UiPath.DocumentUnderstanding.ML.Activities
- UiPath.DocumentUnderstanding.OCR.LocalServer.Activities
- UiPath.IntelligentOCR.Activities
- UiPath.OCR.Activities
- UiPath.OCR.Contracts
- UiPath.DocumentProcessing.Contracts
- UiPath.OmniPage.Activities
- UiPath.PDF.Activities
Install and use
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, see Adding a dedicated agent node with GPU support.
Document Understanding requires the FullTextSearch feature to be enabled on the SQL server. Otherwise, the installation fails without an explicit error message.
Check the Document Understanding configuration file here.
Access Form Extractor and Intelligent Keyword Classifier, with the below 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.
As a post-installation operation, you can enable or disable Document Understanding. More details can be found here.
If you want to use the OCR for Chinese, Japanese, Korean endpoint in an offline environment, you need to install the offline bundle by following these instructions, and once the bundle is installed, you have to enable the OCR in ArgoCD.
- When OCR for Chinese, Japanese, Korean is used in Document Understanding, make sure that you've configured the activity with the public endpoint of the OCR, and the Document Understanding API Key.
- OCR for Chinese, Japanese, Korean is only supported in Document Understanding deployed in Automation Suite. This is not supported in Document Understanding deployed in AI Center connected to an external Orchestrator.
Here are the steps that you need to follow in order to enable the OCR in ArgoCD:
- Access ArgoCD.
- Open the Document Understanding framework.
- Click on the Parameters tab and go to
du-cjk-ocr.enabled. - Click on the Editbutton, set the value to
TRUE, and click on the Save button.
{Cluster_FQDN}/du_/cjk-ocr/.
Check the Document Understanding-related issues here.
