**YouTube** is an American [online video-sharing](https://en.wikipedia.org/wiki/Video_hosting_service "Video hosting service") [platform](https://en.wikipedia.org/wiki/Web_platform "Web platform") headquartered in [San Bruno, California](https://en.wikipedia.org/wiki/San_Bruno,_California "San Bruno, California")

cf3f59da-c081-4fab-99d2-f02e60e183b0.PNG

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

Provides a template workflow that can be used to get transaction data from a queue and create tasks for the user to approve, and continue the task after resuming depending on user decision

5070ea20-c1f4-4d2b-9162-4558ab4d3470.PNG

3774cf50-c74a-4194-b850-2c3784adb37b.PNG

4fb92038-1113-4f72-99bc-3649c99f6ef1.PNG

MIT License Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Long Running Workflow Template for Task Creation