Document Understanding Process - New Studio Template


Hi again, sorry to bother but further down when I ran the process (Attended) I noticed it only gets and processes 1 Transaction Item. In the queue I have a few QueueItems, each one with a filepath.

I want to know how can I loop the process to get every Transaction Item. Thank you a lot in advance for your help!

In order to run this attended, do I need to set the ‘-Attended’ workflow as Main?

I tried to run the project as-in without making any changes, and I get the error:
An extension of type ‘UiPath.Activities.Contracts.Persistence.IPersistenceBookmarks’ must be configured in order to run this workflow.

According to this reply on a related thread, I assume I must be doing something wrong when trying to run it in attended mode.

Because DU Framework is a long running process it is also a linear framework meaning you can only process one queue item at a time (one job for each item in the queue).

1 Like

@Alexandru-Luca @Sergiu.Wittenberger any elegant way to use 2 queues, one that feeds the Classifier with paths to documents that are being classified and split (the split from extraction) and another queue where the classifier pours these items and the Extractor feeds on them?

Thinking on this just for more visibility in terms of queue items, this way you can always link an item in extraction with an item in classifier or be aware if any items did not pass the classifier.

As an example you can have a PDF with 10 invoices in it, this way the classifier queue will contain 10 items that are fed to the Extractor so you have visibility on which item was rejected in Classification or who knows what else :).

I hope what I wrote makes sense.


@carlacarnevali - processing 1 queue item at a time is precisely the intended behaviour; you need to create your own dispatcher mechanism. Please check out the documentation.

@RPAForEveryone - Yes. You also need to disable Persistence. Please check out chapter Settings for Attended Processes in the User Guide.

@ctutu We played around with various scenarios involving multiple DU queues - including the one you mentioned. We found that debugging/managing/scaling become a nightmare very quickly. So, for now, we don’t have any plans to go in that direction.


Cheers Alex, much appreciated !

Short question: Can you explain what the purpose of the Config(“logKey”) is, maybe with an example when that is useful?

Wasn’t included in the previous version…


Hello @Alexandru-Luca can you also share the template as zip file? I am not able to find this template even after checked the Include Prerelease or is this available only in enterprise license?

Hello, i can’t fide this template on my Uipath . Why?


Hi all!

It seems that older versions of Studio don’t properly access/read the public templates feed. Sorry about that. You can find the Document Understanding Process template here. Just download the latest zip and extract the nupkg in the local templates feed - C:\Users<YOUR_WIN_USER>\Documents\UiPath\.templates

@MG2237 - this is done in order to make it very easy to find/filter all the logs coming from a certain job. Especially if you are using the Orchestrator GUI


Thanks for this :slight_smile:

Hi @jeevith!

Sorry for the late reply, I somehow missed your post until now.

1. Arguments lack documentation/annotations

Agreed. However, this release is not GA, it is a Preview release. While the functionality is all there, there are things to be added.

2. Workflow names

There is a mandatory execution order: Digitize, Classify, Validate, Extract, Validate, Export. It makes much more sense to have the workflows arranged like this than leave them in an alphabetically-sorted mess.

I would also like to point out that being familiar with Document Understanding itself is a prerequisite for using the template - I strongly recommend going through the Academy courses for that.

Hi @Alexandru-Luca,

I wanted to leave some constructive feedback to improve the template and as you requested in the release post.

I guess I was a little too excited to try this out. We will wait for the GA version. Meanwhile, as you rightly mentioned it’s probably good to invest some time and go through the academy course on Document Understanding.

That said, I do not see the following being mentioned anywhere in the release post

I would also like to point out that being familiar with Document Understanding itself is a prerequisite for using the template

If UiPath wants more enterprises to adopt DU then such statements will only deter developers who like to get their hands dirty (learning by doing) and figure the rest during the process of learning.

I am facing this error while running the attended robot
Is there a solution ?

@Amani_Boukadidaaa , Can you check the folder in the orchestrator where the asset resides? If it is different from the default folder you have to mention the folder name in the config file.

1 Like

does anyone explain to me why the Orchestrator version become a matter?

@irahmat I guess it is because the queue items are not abandoned after 24H . For the old orchestrator when we are creating a task with the action center and if the people from business takes more than 1 day to validate the same it will abandon the queue item.


My Queue Items still seem to get abandoned, even on Cloud Orchestrator (21.8). Is there a specific setting we need to enable?

@senne.symons did you triggered the bot manually? If it is a manual trigger then it will be abandoned. Try to create a trigger so that whenever there is a new queue item it will run DU process in a non-production robot. For me, this worked.

1 Like