Benefits of Change Process Flexibility
This summary highlights the benefits and new features designed to enhance efficiency in managing and releasing change tasks independently using two processes:
Change Process Flexibility (Enhanced Release Logic) and
Change Additional Process Flexibility (Stages).
Implementing Change Tasks with Sequence (No Staging)
Here are the benefits when you implement the change task with sequence and without stages:
• You can set the actual start date for any newly started change task and begin its implementation.
• The sequence continues to execute in numerical order in parallel with the blank (zero) sequence.
• Any cancelled change tasks no longer start their implementation and get skipped. This makes the overall workflow more efficient.
|
|
You can cancel the implementation of change tasks using the set state option.
|
Executing Change Tasks with Sequence and Stage
Here are the benefits when you implement the change task with sequence and stages:
• Stage support—You can design the change notice workflows to use stage
• Preferences: Sequenced Plan Execution Order and Staged Plan Execution
◦ You can implement the change tasks by setting the stage and sequence options. These preferences allow implementation options for sequence only, stage only, or both.
◦ You can design the workflow to execute a single stage using a synch robot.
◦ These preferences support the implementation of change tasks in numerical order in parallel with the blank (zero) sequence.
◦ The actual start date is set when a change task begins its implementation.
• Enhanced release logic
Here are the benefits when you implement the change task with the enhanced release logic:
◦ A new releaseChangeable2 API used for releasing changeable objects for a stage.
◦ The releaseChangeable2 API combines approval of unincorporated changes for the stage.
◦ Only change tasks assigned to the stage (or blank for special cases) are processed for the release.
◦ Individually released change tasks within the stage are skipped.
◦ The final stage that is Post Release release uses the releaseChangeable2 API to release the entire change notice.
◦ The API releases all remaining change tasks and sets the actual finish date of the change tasks and change notice.
◦ The pending effectivities are processed for a single stage.
Validating Change Tasks
Validation can occur for a single change task, a change notice Stage, or the entire change notice. With the enhanced release logic enabled:
• Any change notice workflow uses the workflow variable to enable the enhanced release logic.
• Previously released change tasks (the actual finish date set) or any cancelled change tasks are skipped during validation.
Releasing Change Tasks
Here are the benefits when you release the change task with the enhanced release logic:
• The actual finish date is set for any change task that are released, regardless of the release method (individual, stage, or full change notice).
• The releaseChangeable2 API sets the actual finish date for releasing change tasks.
• The releaseChangeable2 API combines the approval of unincorporated changes into the API.
Processing Pending Effectivities
Here are the benefits when you process the pending effectivities using the enhanced release logic:
• Processing can occur in the context of a single change task, a change notice stage, or the entire change notice.
• A change task is released (actual finish date set) before the pending effectivities can be applied.
• Cancelled change tasks are skipped.
• Previously applied pending effectivity will not be processed again.
Setting the Resolution Date
You can set the resolution dates for the change tasks and the change notice using the enhanced release logic:
• The resolution date can be set for a change notice and a single change task or all change tasks scheduled for the stage.
• If the resolution date has been previously set, it will not be overwritten.
• The resolution date will reset on a new revision of the change notice and any revised change task.
• The actual finish date will reset on a new revision of the change notice and any revised change task.