In order to obtain an API Key for Document Understanding, yes you need to create a cloud account. Alternatively, you can also request an on-premise trial. If you’re not making use of any activity that requires a key, then you don’t need one, of course.
The difference between the two Main workflows is only regarding how the robot interacts with the Human-in-the-Loop: via local Classification/Validation Station for attended robots or via UiPath Action Center for unattended robots (Action Center licenses being required in this case).
For pre-requisites - please take the Academy course on Document Understanding to get started
Hey @Alexandru-Luca, on the same note, how could we use this implementation with queueitems? Invoking this process in REF would actually suspend the entire performer if it creates a validation station task, is there any workaround here
I’m just theorizing assuming that I have understood this correctly. A Queue abandonment problem is something generic, and we have to deal with it somehow regardless of what is being processed.
But in this scope, can the solution using Queues be a bit simpler?
Let’s suppose this scenario:
The Dispatcher adds a file path to a Queue that is tied to a Queue Processer automation
Queue Processer automation triggers, it consumes the file and initiates the DU Process by passing the file name
As soon as it triggers the DU process, the Queue Processor automation marks that transaction successful and exits
If it fails, then that transaction is marked as failed (the unprocessed file on this transaction can be fed back into this queue via a different mechanism)
This way, the responsibility of the Queue Processor remains minimal, with a small footprint. The transaction is limited only to trigger the DU flow, not to ascertain if the file has succeeded/failed DU processing. I think that responsibility lies majorly with the DU Process as long as it has been triggered successfully and has a file to process.
At least in the Community Edition, this will need to be tested because we have only 1 Unattended Robot license to work with, and two Unattended Processes - one being the Queue Processor Automation, and another being the DU Automation.
In this scenario, will the Queue Processor fail to trigger the second Unattended DU Automation?
Or will will the triggered DU Automation wait in line for the Queue Process to release the Unattended Robot?
Just my thoughts. I hope I get the opportunity to test this out. If anyone in the Community does, please let us know!