BehaviorSaving an object as a duplicate, branch, or revision clones all the aggregated objects owned by the reference object. For example, saving a reference as a duplicate generates a new reference with ports, connection, and children. These operations include a cloning phase and a replacement phase as soon as the object to be saved is used in session. Saving an object as a duplicate, branch, or revision is not allowed if the object is used in session and its instances have configuration effectivities defined. The diagram below shows how the commands work:
Classic and Immediate ModesWhen saving an object as a duplicate, a branch or a revision, you can choose between the classic mode and the immediate mode, depending on your methodology. In classic mode, content is cloned in database, reidentified in session and links are rerouted (Steps 3, 4 and 5 in the above diagram) after you click OK to close the Save with Options dialog box. In immediate mode, content is cloned in database and reidentified in session (Steps 3 and 4 in the above diagram) after you click OK for the first time to close the Save as New, Save as New Branch or Revision dialog box. The links are rerouted (Step 5 in the above diagram) after you click OK for the second time to close the Save with Options dialog box.
Note:
In Step 4 of the above
diagram, if you are using the immediate mode, the old instance of P2 appears as deleted
until you click OK to close the Save with
Options dialog box.
The immediate mode is not available when saving content as a minor revision. LimitationsSaving an object as a duplicate, a branch, a revision, or a minor revision is not compatible with all the functionality provided in the Save with Options dialog box:
|