Add a Custom Field

Home > selected Project > menu or right-click > Settings > Custom Fields > New Custom Field
Project > Settings drop-down > Project Settings >Custom Fields> New Custom Field

Home > selected Organization > menu or right-click > Settings > Custom Fields > New Custom Field
Project > Settings drop-down > Organization Settings > Custom Fields > New Custom Field

Users in a role with the appropriate permissions can add a Custom Field to the Project or Organization Custom Fields list or Custom Fields template. At the Project level, you can use Custom Fields in Metadata Search and Metadata View templates because existing Custom Fields are available along with the predefined metadata fields.

Add Custom Field Options

• Name The unique name of an item. For many items, the name can have up to 100 characters. Some items, such as a Connector name, can have up to 255 characters. An Excluded Content Block name is limited to 32 characters. (required) - The unique name for the Custom Field. Custom Fields are automatically prefixed with drcustom- and converted to all-lowercase, for example drcustom-mailheaderid. The name can include alphanumeric characters and some supported characters (such as a hyphen, underscore, and apostrophe), as well as characters from some foreign languages (for example, Korean ). However, spaces as well as the following characters are not supported for Custom Field names: ! " # $ % & * + . / : ; < = > ? @ [ \ ] ^ { | } ~ “ ”

• Description Provides a helpful description of an item. A description can have up to 255 characters. (optional) - This is optional, but it is a good practice to identify the purpose of each Custom Field you create, since you cannot edit or delete an existing Custom Field.

Custom Field Attributes

The following defaults apply to a Custom Field:

• The field database type is set to string.

• The field database length is set to 2147483647.

• The field token type would be untyped.

• The tokenization type would be standard with wildcard support. This means that the field content is lowercase and tokenized (that is, broken into words/terms, where each word is searchable, and you can use wildcards such as * or ?).

• The field content is stored in the index.