Document Understanding Process 21.10 now in General Availability!

Hello everyone!

:fireworks: :loudspeaker: :sparkler: We are very excited to announce the General Availability release of the studio template for Document Understanding. You can find the Document Understanding Process template on the Official template feed. 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 latest guide is always enclosed when you create a new project and can always be found here.

Below you can find 2 quick overview videos about the Document Understanding Process, and the new Invoice Post Processing workflow. More in-depth videos will come at a later date and posted in this thread as well.

Document Understanding Process Overview:

Invoice Post Processing Overview:

New with 21.10:

  • New workflows for advanced Business Rule validation for Classification and Extraction.

  • New workflow for post processing Invoices based on the OOTB (out of the box) model.

  • Validation Station/Action now only displays the relevant pages instead of the whole file. Removed the PDF splitting functionality.

  • Support for ML Extractor Trainer to use the auto-retrain feature in AI Center.

  • New assets / settings in the config file for skipping classification/extraction training.

  • New assets / settings in the config file to force documents through manual validation (useful in development/UAT especially)

  • New exception type: DocumentRejectedByUserException. This exception is thrown when a user explicitly rejects a document during validation. When setting the transaction status, a DocumentRejectedByUserException is treated the same way as a BusinessRuleException.


  • Exception handling workflows now receive the Exception as an argument instead of an exception message

  • Improved logic for loading Orchestrator assets

  • Improved exception messages

  • Improved comments and annotations

  • Improved logging

General 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.


Thank you for your interest in Document Understanding! If you have any questions or feedback, please use this thread or open an issue here, in our git repository. If you do want to contribute and create a new branch, please be mindful of the naming conventions in the file.


Sergiu and @Alexandru-Luca


Thanks Team, this is great news!