We talk about end-to-end process automation a lot these days. End-to-end automation has human in the loop scenarios. Handling such scenarios will need multiple processes, and Orchestrator queues to process the data in an efficient manner.
When a bot comes across certain transaction data that require human validation, it can easily add the data that require human validation to a separate queue and continue processing the rest of the tasks. This queue can automatically trigger the workflow that creates a task for the user to verify and will be put on hold until the task is verified.
After verification, the process can be configured in a way that the data is being returned to its main process by adding it to the main queue or by other means with the required data to continue depending on user decision.
This workflow template will handle the task creation based on the data in a queue. It will also provide a space where the developer can configure how the workflow should be handled depending on the approval and rejection decision of the user.
Note: The workflow contains comments and annotations to make it easy for you to understand what it does.
Points to note when developing
The input argument "in_TransactionQueueName" should hold the name of the queue which it should get transactions from
The Form Data Collection property contains input arguments passed from the queue. The field identifier of TransactionItem.SpecificContent("FieldIdentifier") has to be changed according to the field identifiers you have on your queue
You can include your own logic to handle how the workflow should handle the user approval and rejections