The General tab on the properties page describes the basic attributes of a property template.
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.
NOTE For monetary values, use integer as the data type and hold or round up the cents amounts according to your company policy. Another option is to create two integer properties; one for dollars and one for cents.
NOTE You cannot perform a query on binary multi-value properties.
NOTE Multi-value uses more space in the system. Individual items within a multi-value property are selectable in a query.
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.