Background
During a change process, various objects could be generated and added to the “Realized Changes” of the Change Action. This could be a result of:
- A new revision that has been created when the Change Action was promoted to “In Work”
- Engineering items that have been captured by the Work Under
- Data created manually during the process
In some cases, part of the captured “Realized Changes” needs to be handled separately for the following reasons:
- Accelerating the approval process
This is the case where users need to accelerate the approval process of the data in the change without waiting for the current change to be completed.
For example, in the case of long lead items which must be approved and transferred to production prior to completion of the changes.
1. Design-study data that is not part of the change
This could be data that has been captured in the “Realized Changes” during a study of the certain design use cases. Such data was not meant to be part of the Change Action.
2. New revisions created but not needed
These revisions could be created, but due to business decisions, they should be completely deleted from the platform as they are of no use (for example, if a new revision was created for a customer, but the customer decides not to cancel his order).
How to handle these use cases in the 3DEXPERIENCE platform:
The following table summarizes the high-level process to implement these use cases:
Note:
Deleting data requires this data to be available for deletion (data should be in the right maturity state, without links etc.)
