...
Within a single task workflow, there may be multiple threads of dependent tasks with different prerequisites, and these threads may proceed independently.
It is possible to launch two separate threads and bring them back into alignment by making their last tasks prerequisites of the next task, for instance.
Task templates can be conditional, and if their condition is not met, then they will be marked as not needed when they would otherwise be assigned. When they are marked as not needed, their dependent tasks will be assigned.
This is an important point: tasks that are dependent on conditional tasks are not prevented if the condition is not met. If they should be prevented, then they should also be made conditional based on the same condition as their prerequisite task.
Note that when tasks are launched for a project or a request using a Launch Tasks button, the Status of tasks will be changed to Assigned based on the following logic:
...
Here there are two tasks that will be assigned right away (ID62 and ID61 - those with no prerequisites). The tasks with a sequence value of 2 will be assigned as soon as the Hold Exit interview is completed, so they might get assigned before ID62 is completed. The final task will be assigned as soon as the exit interview is completed and the support and tasks are reassigned. So it is conceivable that ID62, ID160 and ID63 are all in progress at the same time and any may be completed first.
The ability to choose exactly which tasks must be finished before a task is assigned gives a very flexible model for complex task workflows.
The sequence number gives a general impression of the order of tasks, but it is not definitive and does not control any of the processing. It allows the tasks to be sorted more or less in order of assignment.
...