What is the UiPath Document Understanding (DU) Process template purpose role?
A.
To allow deploying a new Document Understanding process as an Unattended implementation already tailored to your business use case Further development is optional and only required when the business presents additional requirements. The testing debugging and scaling are easy and the template is bum with the community's best practices in mmd.
B.
To allow one generic implementation to address all business needs without further development testing and debugging The DU template can be deployed immediately used as is without any performance concerns and following the best practices pertaining to RPA Document Understanding Orchestration Processes and Long-running workflows.
C.
To allow deploying a new Document Understanding process as an Attended implementation already tailored to your business use case making the lasting debugging and scaling easy and following the community best practices II also makes development optional the template being ready for production deployment out of the box (needed only when the business comes with extraordinary requirements)
D.
To allow a seamless start for any new Document Understanding process that is suitable for all use cases, production-ready has a common architecture tor both Attended and Unattended implementations makes development lasting deployment debugging, and scaling easy and follows the best practices pertaining to RPA Document Understanding Orchestration Processes and Long-running workflows
The UiPath Document Understanding Process template is a fully functional UiPath Studio project template based on a document processing flowchart. Its aim is to offer a Document Understanding tool at hand that is easy to use and easy to execute for any developer who wants to start working either on a simple demo or on large-scale implementation. 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. The process is preconfigured with a series of basic document types in a taxonomy, a classifier configured to distinguish between these classes, and extractors to showcase how to use the Data Extraction capabilities of the framework. It is meant to be used as a best practice example that can be adapted to your needs while displaying how to configure each of its components. The workflow 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 architecture is common for both attended robots and unattended robots running Document Understanding and having human-in-the-loop validation via Action Center. Items are not processed in bulk. Instead, there is one job for each input file. Indeed, a dispatcher is required every time but this flexible approach makes it simpler to get started, to develop, debug, and scale Document Understanding processes. The process supports Visual Basic flavored projects. The default dependencies in a Document Understanding Process are: UiPath.DocumentUnderstanding.ML.Activities, UiPath.Excel.Activities, UiPath.IntelligentOCR.Activities, UiPath.PDF.Activities, UiPath.System.Activities, and UiPath.UIAutomation.Activities. (123)
References:
1: Document Understanding Process: Studio Template - UiPath
2: Document Understanding Process: Studio Template
3: Activities - About Document Understanding Process: Studio Template - UiPath
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit