Propagate changes to a master operation or process to its clones

You can propagate changes made to a master operation or process to any or all of its clones within or across work packages. You can also control whether a released, cloned object can be revised and edited directly or only initiated via propagation from the master source.

By default, propagation is executed in asynchronous mode, so you must set up a dispatcher with asynchronous mode in the environment. Only a limited scope of occurrence level properties, assignments, and attachments can be propagated.

Such propagation is available only:

• For classic BOPs.

• From the master to the first level of clones. Propagation from clone to clone is not supported.

• If both the master and clones are in a released state.

Prerequisites

You must define the relevant preference. Key preferences include the following.

ME_EditClonedReleasedBOPObjectOnlywithPropagate	Controls revision and update of clones only via propagation from master.
EP_ShowSelectionCheckboxforClonedPropagate	Enables you to select one or more clones to which you want to propagate master changes.
MEReleaseStatusForSkipCheckForRevisingClonedObject	Controls whether a cloned, revised object can be independently revised and edited, and whether it is exempt from changes propagated from the master.
MEReleaseStatusListForAutoRevise	Controls the release status to be considered for triggering the revision of a released, cloned object.
EP_ShowClonelndication	Enables the Sync Clone command, which lets you view and then click on the clone indication to further access the Propagate command.
TC_CLONE_CREATE_BASED_ON	Controls the relation created between master and clones. For clones with this specific relation only, propagation is enabled.

Procedure

1. If you have not already done so, navigate to the Process Planning task page.

2. In the Process panel, click Sync Clone . Clone indication icons are displayed in the Process list.

3. In the Process list, click a clone indication icon.

4. In the resulting information window, in the Cloned From section, note the name of the Work Package master object and click Cancel.
   If you start from a master bill of process (BOP), the Cloned From section is blank and only a Cloned To section is populated. Propagation can only be initiated from the master.

5. Search for the master BOP object noted in step 4 and navigate to the master Process Planning page.

6. In the Process panel, select the master BOP object and click Sync Clone .

7. In the resulting information window, in the Cloned To section, review the object strings and work packages to which changes will be applied from the master.
   Note If the target work package is associated to a manufacturing change notice (MCN) that is still open, and one that the user is a participant in, change propagation can be tracked via any change notice selected from the Change Notice list.

8. If the preference EP.ShowSelectionCheckboxforClonedPropagate is enabled, you can select one or more clones for propagation. If the preference is not enabled, all clones are propagated.Note Master and clones must be released to initiate propagation. Clones will be auto-revised during propagation. Clones with a release status listed in the preferences MEReleaseStatusForSkipCheckForRevisingClonedObject and MEReleaseStatusListForAutoRevise are exempt from propagation.

9. Click Propagate. Once propagation is completed, the Alerts section in the Active Workspace page displays an alert message. If propagation has failed, the alert is still displayed and clicking on the alert will display an instruction to review the syslog to analyze further failure related details.