Disconnect Work Tasks

 Explanation

Disconnecting Work Tasks is useful when Work Tasks are no longer required, 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 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 Bundle Tasks, the following effects are observed:

• The references to the 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 Bundle Task need manual adjustment after disconnection.
• Information about the disconnection is cleared, and relevant parties are notified.
• The disconnected task becomes allocatable and can be executed independently as a standalone task.
• An Event log is generated to visually represent the disconnection process.

As a result of this activity, Work Tasks can be disconnected from Bundle Tasks.