- If a requested change on a proposed change is "For Minor Revise," a new revision of the
proposed change is connected to the CA as a realized change.
- When a CA is promoted to In Work, all proposed changes with requested
change defined as "For Minor Revise"/"For Revise" are revised and connected as
realized changes with requested change "For Release."
- When you promote a CA to Completed, all proposed changes with requested change For Release and
For Obsolescence are connected as realized changes with the same requested change.
Proposed changes with requested change For Update and None are not connected as
realized changes.
- You cannot edit requested changes of realized changes.
- You cannot remove realized changes because they are tracked through the CA.
- Objects added with a Requested Change 'For Update' have no impact on the proposed changes.
Therefore, a proposed change added as 'For Update', does not have a corresponding
realized change for a completed CO or CR.
- On completing the change to a BOM using Work Under CA, only the parent object will be
automatically added as a realized change.
- Configured objects remain in the
In Work
lifecycle state. Therefore, revisions cannot be released using Enterprise
Change Management.
- You must manage configured object structures using applicability. For information on how to
manage a configured object, refer to the documentation for the application that
manages the object's types.
- When you modify an unreleased, unconfigured object with a CA, the object is released
when the change action is completed.
- When you modify a configured object with a CA, the object is released when the
change action is completed.
|