This option allows you to establish a default for Modified Local File list in the Get Latest Version dialog box and the Check Out dialog box. This option applies only to files that have been modified locally in the working folder or have Unknown status and not to files that are known versions in the repository.
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 – Fortress 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 three 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 a 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.
If checked, a dialog will be displayed before a locally modified file is overwritten by Fortress, verifying the user’s choice for how to handle the file. This prompt will only be displayed for files that have been modified by the user. It does not apply to versions of files that can be re-created by the Fortress server (e.g., files with an Old status).
If checked, any file that Fortress cannot recreate will be backed up into a backup folder. See Cache/Backup Locations for the location of the actual backup folder.
The default is Checked.
This option allows you to establish a default for the Perform Repository Deletions Locally list in the Get Latest Version dialog box as well as the Check In/Commit dialog box.
Select one of the following options.
Remove working copy
Do not remove working copy
Remove working copy only if unmodified
The default is Remove working copy only if unmodified.
This option also for renames and moves and is applied in the following manner.
Do not remove working copy – the file will be copied and renamed or moved.
Remove working copy – the 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.
The default is Remove working copy only if unmodified.
This option allows you to establish a default for the Make Writable list in the Get Latest Version dialog box.
Select one of the following options.
Make binary files read-only
Make all files read-only
Make all files writable
The default is Make all files read-only.
This option allows you to establish a default for the Set File Time list in the Get Latest Version dialog box as well as the Check Out dialog box.
Select one of the following options.
Current – the time the file was downloaded from the server.
Modification – the time the client reports it last modified the file. This does account for time zones, but can not account for incorrect times set on a client machine.
Check In – the server time at the time this version was checked in.
The default is Current.
This option allows you to establish a default for the Local Copy option in the Undo Check Out dialog box. It determines what to do with the local version of a checked out file when that file’s checkout is undone.
Select one of the following options.
Revert – Overwrite the local file with the baseline version (the version of the file that existed at the time of the check out).
Leave – Do not modify the local file after undoing the check out.
Delete – Remove the local file from the file system after undoing the check out.
The default is Leave.
This option allows you to override the current End of Line setting for files that are set to use “Native” EOL. The Native EOL is determined by the operating system the client is currently running on. For example, if this is a Windows client, the Native EOL for a file is CRLF, and text files retrieved from the database will use Windows EOL.
This option allows you to change the Native EOL type for this user to a value other than the current operating system. For example, if this is a Windows client, but retrieves files to a working folder that is actually a Unix disk, you can change this value to Unix when getting files to that folder so it will have the correct End of Line characters.
This value only overrides when the EOL type is Native for a given file. If the file’s EOL type is set to anything else, it will be used instead of this.
Select one of the following options.
Do not override – Don’t override – continue to use the Native EOL type.
Windows (CRLF) – Use CRLF when Native EOL is specified.
Unix (LF) – Use LF when Native EOL is specified.
Mac (CR) – Use CR when Native EOL is specified.
The default is Do not override.
This option allows you to determine whether files have been edited based on their contents instead of using the modification time of the file. A CRC is a computed number that is theoretically unique based on the contents of the file.
Using this option will cause Fortress to be slower than using modification time when determining file status.
Since CRC checks are slower than modification time checks, this option allows you to compute the CRC only when a file is below a certain size, which allows CRC checks to be faster than they otherwise would be. However, any files above the size specified will still use modification time to determine file status.