Disconnect Request Tasks
Explanation
Disconnect Request Work Tasks if they are no longer needed, have been completed
but need to be canceled, are irrelevant to the bundle, or should be executed
separately as standalone tasks for future development.
Prerequisites
- The status of the Request Bundle Task must be below Work Done.
- Transactions can exist without any reference to work assignments.
- Clockings associated with the tasks should be considered.
System Effects
When Work Tasks are disconnected from the Request Bundle Task, the following
effects are observed:
- The references to the Request Bundle Task's transaction are removed.
- Clocking references linked to the task are removed
- Transactions that have already been completed remain associated with
the individual tasks.
- The duration and assignments of the Request Bundle Task need manual
adjustment after disconnection.
- Information about the disconnection is cleared, and relevant parties
are notified.
- The task that was previously disconnected can now be allocated and executed
independently as a standalone task.
- An Event log is generated to represent the disconnection process visually.
As a result of this activity, Request Work Tasks can be disconnected from
the Request Bundle Tasks.