A naming pattern provides a way to automatically name record categories, record folders, and records to meet your conventions. When a user creates one of these entities that has an associated naming pattern, the name is automatically supplied on the Set Properties step. The system does not prevent the user from changing that name. Incrementing numbers are assigned and used up as soon as the Set Properties step appears. If you cancel before creating the entity, that number will never be used.
To automatically name categories and folders:
About naming pattern syntax
Your business process might require that folder names should start with the letter A, followed by two digits representing the year, a hyphen, and then a folder number, such as A07-000005. The following pattern creates such names:
A[YY]-[\d\d\d\d\d\d]
In this pattern, A is the first character, YY represents the year, and \d is a numeral. The system automatically provides default values for patterns enclosed by square brackets []. Thus, YY is replaced by the last two digits of the current year. \d is replaced by incrementing digits. You specify the increment value in another field when entering the string.
In another record naming pattern, you might want to create a naming rule for folders in series KX followed by a 2-digit year, period, 2-digit month, hyphen, and two sets of incrementing numerals, such as KX07.06-0004-03. The following pattern would fulfill this requirement:
KX[YY.MM]-[\d\d\d\d]-[\d\d]
You can also use custom patterns to create metadata-based patterns. For instance, your organization policies may require that the record folder naming convention should be year, space, subject (metadata) of the record folder, space, and a 5-digit number, such as "2006 Loan 00005." For this, you can create a naming pattern with following specifications:
[YYYY] [THIS.EmailSubject] [\d\d\d\d\d]The system will provide the default values for year and subject because these are enclosed in []. THIS.EmailSubject is a custom pattern. Therefore, the system will provide the value of the metadata field, EmailSubject that you specify for the parent of the record folder. You need to specify the symbolic name of the property while creating a custom pattern. Also, if there is no value available for the specified property, an error is generated. This custom pattern is applicable for only those entities at level 2 or below (3, 4, and so on) in the file plan. File Plan Level is another field you complete when adding a pattern level.or
[YYYY] [Parent.EmailSubject] [\d\d\d\d\d]
Do not use any characters that are invalid in names. For example, do not use a slash / character when incorporating dates. Invalid characters are:
\ / : * ? " < > |To ensure that users do not exceed the number of characters that you have specified in the naming pattern, delimit the naming pattern using the ^ and $ symbols. For example, if you create the naming pattern, \d\d\d, append the ^ symbol at the beginning of the naming pattern, and the $ symbol at the end of the naming pattern, as shown below:
^\d\d\d$This will ensure that when a user enters a value, the number of characters entered does not exceed the number of characters specified in the pattern string.
To add a naming pattern:
To add a pattern level:
Example
If you want subcategories of a top level record category to be automatically named, create a pattern for level 2 and select Record Category as the type. If you also want record folders in that subcategory to be automatically named, create a pattern for level 3 and select Record Folder as the type. Having both of these pattern levels in the naming pattern results in subcategories at level 2 and record folders at level 3 being automatically named.
To add or modify pattern levels later:
To assign a naming pattern to a file plan (required to activate auto naming):