Fracttal One allows you to identify and consult dependencies between work orders, showing the sequence of tasks where one WO depends on the completion of another.
Dependencies are indicated with an icon that links to the previous order, facilitating understanding and navigation between related orders. This article explains how to view and interpret these dependencies.
Creating WOs with dependency
From the creation of a Work Order, users can configure dependencies by specifying a "Parent WO" in the "Depends on" field. This practice establishes a sequential execution requirement for the tasks.
Once this dependency is defined and the WO is in "In Progress" status, the hierarchical relationship becomes immediately visible.
In the Kanban view, the dependent order will display a distinctive dependency icon, along with the identification of its Parent WO.
By clicking on the Parent WO option directly from the order card in Kanban, the system will automatically redirect you to the Parent WO.
Cancellation and rescheduling of linked Work Orders
When a WO in "In Progress" status needs to be canceled and rescheduled, it allows maintaining traceability between both.
When proceeding with the cancellation of a work order in progress and its subsequent rescheduling, the system automatically establishes a bidirectional connection between the original (canceled) WO and the newly generated (rescheduled) order. This means that:
The canceled WO will show a reference to the new WO number.
The new rescheduled WO will indicate the number of the original WO that was canceled.
Note: This display does not include a clickable icon nor does it automatically redirect to the linked WO, but provides a clear identification of the task history.
Viewing in List view
In addition to the Kanban view, dependencies between WOs can also be checked in the List view.
Similarly, each dependent WO will show a dependency icon that links to its Parent WO, facilitating navigation.
By clicking on the icon in the List view, the user will be automatically redirected to the corresponding WO, improving navigation experience and traceability in operational flows.