...
There are four possible ways to connect tasks:
End end to start - the end date of a task dictates the ASAP start of a target task.
...
| Info |
|---|
The direction of the dependency is based on how you create a dependency (the direction of an arrow when connecting tasks). |
In other words - , dependency in ASAP mode always schedules target task as soon as possible based on dependency type. There are no restrictions on how many dependencies are created for each source or target task as long as they are not creating circular relationship. If a task is moved to a prohibited position (based on dependency type and mode) it is moved back/forward to the appropriate position.
...
The Lag time is the minimum time between the tasks, but if you set a 3 day lag time and a task ends on Wednesday, effectively, the gap will last 4 days (Saturday is counted as the 3rd day, but it is not possible for the next task to start on Sunday).
...
ASAP "on" vs "off"
...
ASAP mode on
With ASAP mode "on" there is only one possible position for the target date. position in which a task can be placed by a dependency. The lag time is respected. With ASAP mode "on", the date of the target task should be the same as the date of the source task.
In the example below (no lag time), end date of PP-326 dictates the start date of PP-332. The target start date can't be manually overridden - it will always be the next possible day after the source end date.
...
ASAP mode off
When ASAP mode is "off", there is more than one way to position a task. The lag time is respected.
With ASAP mode is "off", the date of the target task cannot start before the source end date, but it can start at any point after it. should be the same or later than the date of the source task.
There is more than one possible start date for the PP-332 task (any date after August 6th will work).
...