Action Center helps to scale an organization’s journey from task automations to process automations, through seamless hand-off between Robots and Human at multiple stages of a workflow. If you are new to UiPath Action Center , here are some useful links to begin with.
We are starting this blog series to enable our RPA developer community with some quick starter templates based on all the feedback and queries that we have gathered so far.
To begin with, here are some sample workflow templates to demonstrate variants of UiPath Persistence activities usage that creates form-based tasks and resumes a workflow based on human input through UiPath Action Center
Modified ReFramework Template with “Create Form Task” & “Wait for Form Task”
This workflow demonstrates the usage of create form task and wait for form task activities in RE Framework template in-order to inject human actions during transaction processing. This creates form task for each transaction as per business requirement (successful or business exception or failures ), allows it to process all transactions in that batch and then wait for all the created form tasks just before terminating the workflow. It also takes additional input argumentsor configurations for TransactionBatchSize, ActionIDStoreQueueName and WaitForExistingActions as discussed below.
TransactionBatchSize : It is highly recommended to batch number of Actions that will wait in Parallel For Each from a single job in cases of large number of Actions created by each process execution. By default, Orchestrator supports 1000 such wait tasks in parallel.
ActionIDStoreQueueName : This queue stores Action Ids in case the current job terminates due to some technical errors without invoking ‘Wait for Task’. By tracking Action Ids in this queue, it could enable scenarios that requires a different job to wait for actions or query actions for further processing. This queue can later be used in the recovery workflow in case of failed jobs so that user input for already created actions are still routed back to Robots.
WaitForExistingActions : As mentioned above, this workflow can as well just wait on already created Actions, say for example as a recovery workflow in-case of unexpected technical errors in the original job execution that created all Actions. To use it as recovery workflow or a workflow that waits for already created actions , mark this boolean flag as True.
ReFrameworkWithActionCenter.zip (1022.1 KB)
- TransactionBatchSize & ActionIDStoreQueueName argument or update in configuration file.
- WaitForExistingActions argument or update in configuration file. Default value for WaitForExistingActions is false.
Sample Flowchart based workflow to wait for already created Actions
This flowchart based sample demonstrates how to wait for already created Actions from a different workflow to cover cases where Actions have been already created but the original job terminated without waiting for all the tasks to complete, thus resulting in scenario where the user input might not be routed automatically to any Robot. This workflow ensures to route user input without needing a Robot to explicitly poll specific set of actions periodically, thus making it much resource optimized.
This workflow demonstrates you following steps
- How to get the task ids in batches?
- How to create task objects for these task Ids?
- Wait for tasks
- Invoke logic post resumption
TransactionBatchSize : This attribute decides the number of Actions for which a job can wait in parallel. By default Orchestrator supports 1000 such wait tasks in parallel from one job.
ActionIDStoreQueueName : This keeps track of Action Ids in case the current job terminates due to error without waiting for each of the tasks to complete. This can also enable scenarios that requires a different job to wait for actions or query actions for further processing. This queue can later be used in the recovery workflow in-case of unexpected technical errors.
WaitForExistingActions.zip (25.8 KB)
TransactionBatchSize & ActionIDStoreQueueName to be passed as arguments.
How can we engage better with our community?
We are eager to hear from you on the use cases that your organization have automated (or planned) with Action Center.
Here is an interesting case study from telecom industry on how synergies between AI Center and Action Center brought together a great automation opportunity
We look forward to have an engaging conversation on the features we released in our latest LTS release and any specific areas that you would like us to focus on as part of best practice guides as well as top missing features that made you defer consumption of Action Center based scenarios.
Keep watching this space for our next set of enhancements as part of a new Persistence activity package version focused on enabling RPA developers with additional activities to build wider range of long running workflows.