The Default Repository Settings page allows the user to create a settings template for all new repositories created on the Vault Standard server. Changes to default repository settings will not automatically be applied to existing repositories, but may be manually applied to repositories by clicking the "Apply to Existing Repositories" button.
Default access can be assigned to all users in a new repository by selecting either "Access" or "No Access" in the Default User Access dropdown..
The Mergeable Files field lists the file types that can be diffed and merged and therefore can be edited by two users at the same time.
Adding or deleting a file type in this list updates the properties for all files of that type to reflect the values in the list.
For example, if you add a file type of .foo to the Mergeable files list, all existing files of type .foo in the repository are updated to be mergeable. If .foo is deleted from the list, all files of type foo will no longer be treated as mergeable by Vault. File types that were not changed are not affected.
The File Exclusions field lists file name patterns that should not be included by default when adding a folder to Vault Standard.
Changing a file pattern in this list updates the file exclusion list in all Vault clients.
The Folder Exclusions field lists folder name patterns that should not be included by default when adding a folder to Vault Standard. The folder pattern applies to any recursive subfolder of the folder you are attempting to add.
Changing a folder pattern in this list updates the folder exclusion list in all Vault clients.
The EOL Conversion drop-down menu allows you to select the EOL to be applied to mergeable files only. The list includes:
None
Native
Windows CRLF
Unix LF
Mac CR
Note that this does not change existing files in the database. It only affects new files that are added to Vault Standard.
The default EOL type for mergeable files is Native and for binary files is None.
Click Add on the title bar of the Keyword Expansion page to enter the extensions for files in which keywords will be expanded. You can also add the Start and End of History Line.
When keywords are configured, the keywords are expanded on the client machine during the Add and Check In operations. After the commit has completed, the file in the repository and the client machine will be in expanded form.
If a file containing keywords is checked in and there were no modifications made to the file and the option for checking in unchanged files is set to Undo Checkout, then the undo checkout will occur and the keywords will not be expanded. If the unmodified file is checked in and the option is set to force the check in, then the check in will occur and the keywords will be expanded in the new version of the file in the repository.
Keywords are expanded only upon Add and Check In, not during the Get or Check Out of a file. In addition, the file extension of the file in which keywords are to be expanded must be listed in the Mergeable Files list.
Following is a list of supported keywords. This list is identical to the list in Visual Source Safe with the addition of UTCDate and UTCModtime.
|
Type this keyword |
To add the following |
|
$Archive: $ |
Vault Standard archive file location |
|
$Author: $ |
User who last changed the file |
|
$Date: $ |
Date and time of last check in |
|
$Header: $ |
Logfile, Revision, Date, Author |
|
$History: $ |
File history |
|
$JustDate: $ |
Date, without the time addendum. |
|
$Log: $ |
File history, RCS format |
|
$Logfile: $ |
Same as Archive |
|
$Modtime: $ |
Date and time of last modification |
|
$Revision: $ |
Vault Standard version number |
|
$UTCDate: $ |
Same as Date, but time is given in UTC |
|
$UTCModtime: $ |
Same as Modtime, but time is given in UTC |
|
$Workfile: $ |
File name |
|
$NoKeywords: $ |
No keyword expansion for all keywords that follow |
Keywords are case-sensitive and must not include any blank space between the first dollar sign and the colon. Blank space and/or arbitrary text can be included between the colon and the trailing dollar sign.
The History and Log keywords expand to the file’s current repository path. They result in additional lines being inserted in the file on the line following the keyword. These inserted lines are subsequently treated as text, so no further expansion or changes will occur in them (unless they, in turn, contain keywords).You can specify optional start and end strings to be placed before and after the inserted lines. For example, ".c" files could be configured to place /* and */ around inserted lines to make them comments.
Two dollar signs can be placed in front of a keyword to specify that it should be formatted as HTML. For example:
will expand to
This allows the keyword control characters to be hidden in a document as comments like this:
Last edited by: <!-- $$Author: -->Fred<!-- $ -->
Note that this does not apply to history lines inserted into a file.
When a keyword is expanded, the new information is placed between the colon and the trailing dollar sign. Any existing text is replaced. For example:
will expand to (assuming Fred was the last person to change the file)
$Author: Fred $
Preserving Spacing – Blank space can be preserved inside a keyword by using two colons. For example:
will expand to
Note that this does not apply to history lines inserted into a file.
Dates and times are presented in ISO 8601 format. Time zones are always included, but can be displayed as a number offset ("-06:00" for CST) or "Z" (for UTC time). All times are in 24-hour format, so the AM/PM designator is no longer present.
2003-06-30 13:25:57-06:00
2003-06-30 19:25:57Z
The default is Disabled.
Type the file extension to be configured for keyword expansion in the File Extension box. Do not use an asterisk. The file extension is limited to nine characters.
When editing a file extension, you are not allowed to modify this string.
Type the string that will be placed in front of any lines of text that are inserted into a file for the History keyword. This string is limited to 25 characters.
Type the string that will be placed after any lines of text that are inserted into a file for the History keyword. This string is limited to 25 characters.
Once a new keyword file extension has been added, the option of editing the file extension will be included in the table.