As our team works with business analysts around the world, we find out that some of them are new to workflow and concepts within workflow that are achievable.  If the latter is the case, we wanted to share some insight into introducing some of the basic concepts of workflow task routing. We hope you find these helpful!  

A Task is an item that is routed to a single user or # of users to complete.  Within FlowWright, a task has many options for users to choose from when building out a process:

• Route to user(s)
• Route to a role
• Wait for all to respond or just have one person out of multiple people respond
• Set an expiration
• Set a priority
• Send an email notification about the task
• Send an acknowledgement link within the email
• Provide custom names for the approval/reject buttons
• Hide the reject button

As you can see the task can be configured with many options.  Here's an example of a simple task, the workflow starts and routes a task to the user.  

Serial tasks: Serial tasks are connected in a serial fashion, where after completing one task the next task will start.

Parallel tasks: Parallel tasks are a group of tasks that will start at the same time, but each one might get completed at different times.

In the above example, task1 and task2 will start at the same time and wait for the  assigned users to complete.

Parallel tasks with synchronize: Let's say you want to have a task3, but only start task3 once task1 and task2 are completed. 

As shown above, the synchronize step is used before task3, synchronize step will wait until task1 and task2 are completed before moving on to task3. These are the 3 main basic concepts when working with workflow tasks.  Using just these 3 concepts, you can automate very simple to complex manual processes into automated digital processes. If you have questions on how to create or assign tasks our support team would be happy to help.