This chapter provides project management workflows that enable Microtasks microtasks to automatically update when new schedule is loaded.
...
When an XML is imported into Fuzor, Microtasks are created instead of macrotasks. A Macrotask needs to be selected in order to add a microtask to the schedule | |||||||
 | Adds a construction Microtask to the currently selected Macrotask. Other Task Types also Create Macrotasks, by default. | ||||||
When a microtask is created it is created as the child of the selected task. This allows users to clearly evaluate the relationship between the microschedule and the macroschedule. By default, the user cannot edit the Macroschedule and Task names and dates of macrotasks appear grey instead of black. This enables the user to easily distinguish between the two. When a XML update is made microtasks update durations and dates based on the offset that is introduced to an associated macrotask with the XML update. | |||||||
 | |||||||
When a schedule update is made to ‘Macrotask’ that changes the start date ‘Microtask 1’, ‘Microtask 2’ and ‘Microtask 3’ will all have their start dates adjusted by the same amount. | |||||||
There are two ways to create multiple microtasks linked together | |||||||
 | Creates multiple Microtasks linked together in a chain as children of the currently selected task. | ||||||
Microtasks can also be created separately and manually linked together. | |||||||
Relinking Microtasks
| Anchor | ||||
|---|---|---|---|---|
|
Leran how to relink a micro task to a new macro task.
In some situations a user may need to relink a micro task to a new macro task. this may happen due to changes in the construction methodology or because of a mistake. Additionally during schedules updates some tasks may become orphaned. Orphaned tasksneed to be relinked to a new macrotask before continuing. | |||||||
 | Selected to relink a micro task. All micro tasks contain the icon in the relinking column allowing you to relink them at any time. | ||||||
 | Selected to relink an orphaned micro task. | ||||||
After the relinking column in the micro task is selected a macro task is needed to relink the micro task too. The same column is used to select the macro task. A different Icon is used to denote a macro task. | |||||||
 | Selected to denote the macro task that the micro task is being relinked too. | ||||||
Chains of micro tasks are always linked together. only a sequential chain can be relinked at a time. a microtask with multiple predecessors or successors cannot be relinked. Predecessors and successors may need to be temporarily removed before relinking a specific chain of tasks. | |||||||
Editing the Macroschedule
...
In some situations the user may need to edit task data in the macroshedule. The user also may be creating a schedule entirely in Fuzor and does not need to use the Macro-Micro relationship. The Micro and Macro radio button toggle between macro and micro scheduling modes. When in Micro schedule mode the user can only create and edit microtasks. When in Macroscheduling mode The user can edit any task, but can only create Macrotasks. When an XML is imported, the mode is always switched to macro mode. | |||||||
 | |||||||
| A Construction task is the only task type than can be created as a macrotask. However the task type be changed after it is created to any Fuzor task type. | ||||||
Orphaned Tasks
| Anchor | ||||
|---|---|---|---|---|
|
Learn how to handle microtasks that are associated with macrotask that is deleted in a schedule update.
Sometimes tasks are deleted when a schedule update is made. This means that there are Macrotasks in Fuzor that do not exist in the updated XML. When Using Merge By ID there is an option to delete tasks with assigned objects. Macrotasks that have no objects assigned will always be deleted if not included in the XML update. | |||||||
When a macrotask is deleted the user is prompted to decide whether they would like Microtasks with deleted macrotask to automatically relink to another Macrotask with the closest date or if they would like to manually relink microtasks back to the macroschedule. |  | ||||||
If manually relinking is desired any microtasks that are children of deleted macrotasks will become Orphaned. Orphaned Microtasks always appear at the top of the gantt chart. In order to continue working the microtasks need to be remapped to new macrotasks. The relinking column is used for to remap the microtask to a new macrotask | |||||||
 | Selected to relink a microtask. All microtasks contain the icon in the relinking column allowing you to relink them at any time. | ||||||
After the relinking column in the microtask is selected a macrotask is needed to relink the microtask too. The same column is used to select the macrotask. A different Icon is used to denote a macrotask. | |||||||
 | Selected to denote the macrotask that the microtask is being relinked too. | ||||||
an orphaned Microtask. for more information see Relinking Microtasks. | |||||||