When the master document of a project copy has changed since the project copy was made, the master document may contain more or less information than the project copy, possibly making the project copy obsolete.
You can reconcile the difference between the two documents by one of the following commands:
-
Discard from Project: This assumes that because of whatever changes were made to the master document, the project copy is now obsolete and the project copy should be destroyed. This command cannot be undone.
-
Confirm Superseded by Master: This assumes that because of whatever changes were made to the master document, the project copy is now obsolete. In this situation, the system retains the project copy and its reference to the master document for future reference, but makes the project copy obsolete. The system also prevents the project copy from being released as a new master document revision. This command can be undone with the Undo Make Obsolete command.
This command is only available if the Advanced Project Workflow Module has been enabled for the vault.
-
Confirm Merged with Master: This assumes that the changes made to the master document have also been made to the project copy. This option should be used after you have physically merged changes in the master document with the project copy. In this situation, the system retains the project copy and its reference to the master document for future reference. The system will allow the project copy to be released as a new master document revision (possibly after additional changes are made to the project copy) after which the project copy becomes inactive. This command can be undone with the Require Merge command.
This command is only available if the Advanced Project Workflow Module has been enabled for the vault.
To perform this task, you must be a member of a group that is assigned to the Contractor, Contributor, Document Controller, Project Owner, or Tenant Administrator role that is assigned to the parent folder.
