Task Recast vs. Task Rework
Task Recast and Task Rework are both features that enable the user to make changes to a Task after the execution has started. The following table compares both the features.
Task Recast | Task Rework |
|---|---|
No data loss occurs during a Task Recast. | No data loss occurs during a Task Rework. |
Access Rights are required for a Task Recast | No Access Rights are required. Anyone can perform a Task Rework. |
The Task started from one Template version is changed based on another version in a Task Recast. | The Template associated with the Task is not changed in a Task Rework. |
Changes from different versions of the Template are introduced into the Task at runtime. | Changes are made to the Task content in the Task copy only. |
The Template Author can initiate a Mass Recast of Tasks that are based on the same Template. | The Template Author is not involved in a Task Rework. |
The user executing the Task can Recast the Task from a different version of the Template. | The user executing the Task can Rework, i.e. change the content of the current Task as a one-off change. |
A Single Task Recast happens on a Task when the execution is underway. A Mass Recast can occur on any Task that has been started. | A Task must be started for a Task Rework to happen. The execution must be stopped for Task Rework. |
Components embedded inside the Template can be Recast separately. | The Steps of the Component are treated as the Steps of the Task and changes are made to the Step structure in the local copy of the Task. |
A Task Recast can be canceled. | A Task Rework can be canceled. |