Setting dependencies
"B doesn't start until A is finished" — this is how you chain work steps together. Where the dependency is set and what happens when you insert one into a chain.
A dependency says: This work step doesn't start until its predecessor is finished. First cutting, then assembly, then finishing. These are exactly the chains Gantway pulls along automatically when things are rescheduled.
How to set a dependency
In the sidebar go to Orders → open the order → tab "Tasks" → expand the work step: the "Dependencies" section, then "Select predecessor task". Connecting by dragging in the Gantt chart is not possible; the chain is always created on the task. By default Admins, Planners and team leads may set dependencies.
The logic is consistently finish → start: the successor starts when the predecessor ends. Gantway has no other variants, so there is nothing you can set incorrectly.
Gantway rejects impossible chains: make A depend on B and B depend on A, and you'll see "Circular dependency detected".
Inserting into an existing chain
If you attach a new step to a predecessor that already has successors, Gantway asks "Adjust successors?":
- "Insert into chain" slots the new step in between. Whatever was attached to the predecessor is now attached to the new step.
- "Keep parallel" lets the new step run alongside the existing successors; both start after the predecessor.
Auch bekannt als: Predecessor, Sequence, Chaining, Successor, Dependency.