Mapping a backwards loop in your process can serve many functions. Perhaps you have a task that needs to be completed multiple times before you can move onto the next one. Perhaps certain levels of quality control need to be met before a process can continue.
Whatever the reason, mapping a backwards loop can be very useful and won't take too long to set up.
How do you map a backwards loop?
With the clever use of paths and gateways, you can map a backwards loop. First of all you'll need to place a gateway in your process. From there, instead of mapping a pathway moving forwards, you need to lay down a path to a previous task.
This could be the last completed task in the process. Or, you could loop back further. If you need a set of tasks to be repeated, you can loop your process back to the first task in the sequence that needs repeating.
From there, it's a simple case of setting up the correct expressions and fields to make your loop and gateway work correctly. If you're hazy on how to do so, check out our article on How Gateways and Expressions Work.
How will the user see a backwards loop in Run or Home?
From the user perspective, a task that's part of a backwards loop will display almost no differently to a regular task. The main difference being that the user will need to complete one or more tasks a certain amount until your configured requirements have been met.
One visual indicator that the user is taking part in a backwards loop is the loop indicator. In the home view, you will see an icon showcasing how many times the task has been completed.
When the task is in progress, the user will also be able to see the same information in the right hand sidebar. It's important to remember that this will only show how many times the task has been completed, not just started.