Property template properties (General tab)

The General tab on the properties page describes the basic attributes of a property template.

Name
The name assigned to the property template. The name can contain any 64 characters (upper- or lower-case letters, numbers, spaces, and symbols.) If you change the name, the change propagates to subclasses.
Symbolic name
The symbolic name can be used as a programmatic identifier. The symbolic name is created by the Create Property Template wizard, using the value of the Name and removing any spaces and ensuring that the first character is alphabetic (the rest of the name can be alphanumeric). You can change the symbolic name, but you must also change any code that is using this value. The symbolic name must be unique within a class family only. A class family is defined by a root class (for example, Document, Folder, and CustomObject) and all of its descendants. 

Starting with the 4.5.1 release, a metadata prefix-naming convention for class and property symbolic names has been defined for the Content Engine. All new classes and properties introduced in this release or later, by any IBM ECM product that produces its own Content Engine add-on feature, or by new system properties in the Content Engine server, are required to adhere to this naming convention. This naming convention applies to class and property symbolic name values only; there are no constraints on the values chosen for display names.

Details of the prefix-naming convention are as follows:

Starting with the 4.5.1 release, any IBM ECM product that produces its own add-on feature must conform to a prefix-naming convention. These add-on features use a prefix of "Cm???", in which "???" represents a short product-name abbreviation. However, any IBM ECM products that have already established their own prefix-naming convention before this release continue to use it instead.

The following add-on metadata prefixes are reserved:

When you create a class or custom property, avoid assigning its symbolic name with a value beginning with one of these reserved prefixes; as long as you do so, you will not be subject to name collisions in this release or in any future upgrades.

Description
Use the description to further explain the property template. The description is optional and can include any information you find useful. If you change the description, the change propagates to subclasses.
Data Type
The data type defines the data the property template contains. You can use the following data types: string, integer, object, float, date/time, Boolean, binary, and primary ID. The data type cannot be changed.
Cardinality
Cardinality defines whether the property value is a single value or a list. This attribute cannot be changed. The allowed values are Single Value or Multi Value.
Single identifies a property that has only one value. An example of a Single Value is Name if only one name, with multiple words, is allowed. Multi identifies a property that can have more than one value. For example, if the property is Borrowers and more than one borrower is listed, the property should be a List. The property Author should be a List because a book can have more than one author.

NOTE  Multi-value uses more space in the system. Individual items within a multi-value property are selectable in a query.

Primary ID
The property template's GUID.
Alias IDs
Enter the GUIDs of properties in other object stores that can be used as alias IDs. For example, if Name in this object store refers to Author in another object store, Click Assign and enter the Primary ID of Author. Click Unassign to remove the Alias ID.

NOTE  Any alias IDs you add to a property template that has already been assigned to a class are not applied to the class. You must assign the alias ID to the class.