The Get Latest Version dialog box allows you to get the latest version of files and folders from the Vault Professional repository.
The Get Latest Version dialog box can be opened:
From the Source menu, select Get Latest Version
Right-click on folder to bring up the Folder Tree Context Menu, select Get Latest Version
Right-click on file to bring up the File List Context Menu, select Get Latest Version
Select Get Latest Version on the Toolbar
Ctrl+G
A working folder must be set to get the latest version of a file or folder. If a working folder is not set for the selected file or folder, the Set Working Folder menu dialog box will appear. Select the working folder and click OK to continue with the Get Latest Version command.
The To box defaults to the working folder but can be changed by typing a new folder in the box or using the Browse button to locate a new folder.
Changing the To: folder does not reset the working folder – it just overrides where files go for a particular Get Latest Version.
The Modified Local File option tells Vault Professional how to handle files that have been modified locally since they were retrieved or exist but have a status of Unknown. This option doesn’t apply to local files that are known versions in the repository. Select one of the following options.
Overwrite Working Copy – This overwrites the local file. If the file is not in your working directory (because you changed the To: field in this dialog), it will simply be overwritten. If the file is in your working folder and has a status of Unknown, it will be backed up in the _sgbak directory before being overwritten
Do Not Overwrite/Merge Later – This will not overwrite an existing file if it has been changed locally. If the download is to the working folder, it will still download a new repository version into the hidden state folder allowing you to manually merge the file later (in which case the file’s status becomes Needs Merge). If the download is not to the working folder, the file will simply not be retrieved.
Attempt Automatic Merge – Vault Professional will attempt to merge the changes from the server copy into the working copy. If it can do so without irresolvable conflicts, then it will do so. All files will be archived so you can examine precisely what was done in the automatic merge step. However, if the file cannot be merged automatically, the behavior is identical to that of the Do Not Overwrite setting above: the working copy is untouched, and you must resolve the conflict later before check in is allowed. A message is written in red in the Messages pane for each file that could not be merged.
If the file is being retrieved to a folder other than the working folder, this option is disabled altogether since the working folder is required for merges. Overwrite becomes the default in this case.
The default is Attempt Automatic Merge.
The Prompt for modified files option tells Vault Professional whether to prompt you before overwriting a file that has been modified locally, or has an Unknown status.
If checked, any file that you have modified locally (has an Edited, Needs Merge, or Merged status), or any file that Vault Professional can’t reproduce (Unknown status) will not be overwritten unless you explicitly tell Vault Professional to do so with a prompt dialog that is displayed during the Get.
If not checked, no dialog will be displayed, and the value of the Modified Local File option will be used to determine whether to overwrite the file, leave the file, or attempt to automatically merge it (if it is currently Edited).
The Set file time list allows you to select the time to be associated with the selected file or folder. Select one of the following options.
Current – The current client time the file is download from the server.
Modification – The time the file was last modified on the client before it was checked in. This time depends on the clock of the client machine where it was checked in.
Check In – The server time the file was checked in on the server.
Select Repository Deletions options to determine when to delete files locally that were deleted in the repositories. This option will apply to folders recursively. This is enabled only when the Get Latest Version is on a folder.
Select one of the following options.
Remove working copy – The local file will be removed if it was deleted in the repository, regardless of the state of the file.
Do not remove working copy – The local file is left untouched.
Remove working copy only if unmodified – The local file is removed only if it is not a known version in the repository.
This option also applies to renames and moves.
Do not remove working copy – the file will be copied and renamed or moved.
Remove working copy – file will be renamed or moved.
Remove working copy only if unmodified – if the file has been edited, the file will be copied and renamed or moved.
Select one of the following options.
Make binary files read-only
Make all files read-only
Make all files writable
Check the Recursive checkbox to get the entire content, files and subfolders, of a folder. This is enabled only when the Get Latest Version is on a folder.
If you select this option, the dialog will be disabled and will not appear unless the shift-key is being held down. The default selections will apply to any item selected. See Local Files Options to change the default selections.
Click OK to retrieve the items.
Click Cancel to close the Get Latest Version dialog box and no action will be taken.