Hi My understanding is the create document validation action and
wait for document validation action and resume must be working together.
what if we have 5 files we iterate using DU then 5 of them is have low confidence and we want them to go to action center then robot will wait for validation ,
what is the best way to approach this ?,
if we add 1 document then wait till human validate and only then we ocntinue for other document it will take too long
Hi @Ahmad_Rais,
Yes, these activities should be paired and used together.
But, it support only one document process for validation.
If you need to customize then you will have to create a customized task for action center but it may not have functionalities present in those built in activities.
You need to use Create Form Task activity to design custom form task, and pair it with Wait for Form Task & Resume. But it’s time consuming and difficult similar to existing validation activity.
On other option you can explore is Action Apps which you can build from Studio Web.
But, I would suggest to have seperate tasks for each document using the existing activities.
i dont think this is what im looking for,
im looking for the best practice on creating multiple action task and validate them
Indeed, thats the challenge with transactional processing models when you have things like HITL, in scenarios like this it breaks down.
The UiPath DU Framework is also grossly over complicated and hasnt adapted to the shifting zeitgeist.
Without knowing more about your overall architecture and if these files are relevant to each other its not super easy to explain the best approach however consider this.
Make a new project that has a simple workflow for the Main, at the top add a queue trigger so the process is set to start whenever a queue item is added. We won’t process that item in a transactional model though, but a linear one.
Add the extraction task and the validation task as required, keeping it simple.
After extraction you can set the queue item to successful etc, and pass on the relevant information.
By refactoring to make the DU linear you remove any blockers from other transactions being ahead in the queue.
so by default right now,
the action center is designed to process 1 file then suspend till it gets confirmed, then continue right ?,
means we cant put the files first in action center so giving time for users to review everything when they have the time right ?
So as per what @Jon_Smith mentioned basically as its linear say one job is in suspended because the queue has more the process gets triggered again ..so instead of single job processing all ..multiple jobs start one after the other just like transactional
Alternately even with transactional process we can use ..here is the explanation on how to do it
Cheers
The action center can have as many tasks in there as you like.
Its all about your structure in the RPA. If you use for example the REFramework as your model, because its transactional processing it won’t pick up the next item until the current one is done, that means that a HITL will suspend the process instead of starting the next one.
Cause of how queue triggers work the process would start again 30 minutes later, so eventually all 5 would get into the action center, but it can take hours.
The UiPath DU framework is, in my opinion, not worth learning. Its designing in an anti pattern way that isn’t fit for an Orchestration approach to designing automations. Its one of those things that can be hard to get people, including the author, to change cause they are too deeply invested.
The best architecture is to build in an orchestration and use a linear process for these steps, trigger by the orchestration jobs as required.
Its still a good idea in my opinion even if you dont use an Orchestration pattern, but I’d need to know more about what happens upstream of these 5 hypothetical files aswell as downstream and if the 5 files are related to each other in this business case.