OCR services are used for the following purposes:
- At data labeling time, when importing documents into Document Manager. The engines available for this step are UiPath Document OCR, Google Cloud Vision OCR, and Microsoft Read OCR.
- At run time when calling models from RPA workflows. The engines available for this step are all the engines integrated with the UiPath RPA platform including the above, plus Abbyy Finereader, Microsoft OCR (legacy), Microsoft Project Oxford OCR, and Tesseract.
In production, we recommend calling the OCR using the Digitize Document activity in your workflow and passing the Document Object Model as input to the activity calling the ML model. For this purpose, you need to use the Machine Learning Extractor activity (Official feed).
As a quick convenience for testing purposes, you can also configure the OCR directly in AI Center (Settings window), but this is not recommended for production deployments.
The table below shows how to configure the six supported OCR engine types in both Document Manager and AI Center.
ocr.methodargument corresponds to the OCR Engine dropdown in the ML Package creation view in AI Center.
|OCR Engine||OCR Method||OCR Key||OCR URL|
|UiPath||UiPath Document OCR||UiPath Automation Cloud|
Document Understanding API Key
|Google Cloud Vision OCR||GCP Console API Key|
|Microsoft Read 2.0 On-Prem||Microsoft Read OCR||None|
|Microsoft Read 2.0 Azure||Microsoft Read OCR||API Key for your resource from Azure Portal|
|Microsoft Read 3.2 On-Prem||Microsoft Read OCR||None|
|Microsoft Read 3.2 Azure||Microsoft Read OCR||API Key for your resource from Azure Portal|
Updated 7 months ago