We are very excited to announce the new studio template for Document Understanding. You can find the Document Understanding Process template on the Official template feed - make sure Include Prerelease is checked. To get started, simply create a new project in UiPath Studio and select it.
We recommend to carefully read the enclosed User Guide, even if you’re already familiar with the solution. The Guide can be found here.
We are working on new intro & quick-start videos. In the mean time, while a little dated, the existing quick-start video is still relevant for an overview and dispatcher setup.
Features of the Document Understanding Process:
Queue Integration (Requires Orchestrator 20.10.8 or newer): Default for unattended, and optional for attended mode. Please do note that AutoRetries should not be activated on queues and that the Document Understanding Process was designed with the idea of ONE file per QueueItem!
Try / Catch and Error management: All important activities have a retry mechanisms or Try/Catches over them. If something goes wrong, it will be caught and reported in either ERR_Abortprocess.xaml or ERR_HandleDocumentError.xaml
Business and RPA friendly overview of the project: At a glance you are able to understand what happens where. This adds value by being easier to explain to business users what actually happens in the process, yet at the same time it simplifies the structure for ease of access in case of errors or feature requirements
Ability to use an attended or unattended bot with this process by selecting the correct main.xaml
Classification retraining implemented directly in the workflow: It just works!
ReusableWorkflows folder with 2 implementations for Classification retraining:
Lock/Unlock file – default, already implemented.
Get/GiveUp Write Permission – requires manual implementation with a queue in Orchestrator.
If you managed to read up until here, I congratulate you and ask to provide any feedback either in this thread or directly making a pull request or opening an issue in our repository here. If you do create a new branch there, please be mindful of the naming conventions in the README.md file.
Alex and @Sergiu.Wittenberger