Change Process Flexibility by Releasing Change Tasks Independently
Typically, a change notice and its tasks are validated and released, with the pending effectivities applied on completion. However, there are situations where individual change tasks must be released before the entire change notice is complete. In such cases, each change task can be validated, released, and have the pending effectivities applied individually.
This enhanced release logic works with a combination of the following workflows:
Change Notice Version 1 Workflow
This new workflow provided out-of-the-box is intended to replace the existing Change Notice Workflow. The existing workflow Change Notice Workflow is updated by adding the workflow variable optInFinishedAndCancelledFilter and the releaseChangeables2 API to set the actual finish date on release of all change activities. For more information on this variable see Use a Workflow Variable to Activate Enhanced Release Logic (Version 1) and Use releaseChangeable2 API to Set the Actual Finish Date.
Change Task Workflow with Release of Change Task Version 1
This new workflow provided out-of-the-box demonstrates how an individual change task is released. It is enhanced with the actual start date and actual finish date. The releaseChangeables2 API is used to set the actual finish date. For more information, see Set Actual Start Date and Actual Finish Date and Use releaseChangeable2 API to Set the Actual Finish Date.
 |
These workflows are provided out-of-the-box. However, they are not enabled. For enabling these workflows, see Enable the Out-of-the-Box Workflows.
|
|
|
PTC recommends that you update your workflows with the new API and variable as soon as possible to adapt to this enhanced logic.
|
Related Topics