Object names (IDs) and titles

The Name field stores the name of an object instance. If the Title field is enabled for an object type, the Name field has two components: ID (System Fields:Name) and Title (System Fields:Title).

By default, the Title field is not enabled, and the Name of an object instance must be unique within a folder.

When the Title field is enabled for an object type, object names have the following two components:
  • The Name.ID component stores the name, which must be unique within a folder and must meet the requirements for system names.
  • The Name.Title component stores a longer name. The title does not need to be unique and can contain up to 3,748 bytes. Auto-naming updates the ID component only.
Table 1. Components of System Fields:Name
Default (No Title component) Title component enabled
Object names have one component, Name (System Fields:Name). Object names have two components: ID and Title.
Name (System Fields:Name)
  • Must be unique within a folder.
  • Must be 252 bytes or less.
  • Must meet requirements for system names.
 ID (System Fields:Name)
  • Must be unique within a folder.
  • Must be 252 bytes or less.
  • Must meet requirements for system names.
Title (System Fields:Title)
  • Does not need to be unique within a folder.
  • Not restricted to system naming requirements.
  • Can be up to 3,748 bytes.

Enabling the Title field

An administrator can enable the Title field for an object type. Click Open Administration menu Administration menu > Solution Configuration > Object Types, click Edit, and then click Enable Title Component. The values from the Name field are migrated to the ID component.

Tip: Do not enable the Title field for self-contained object types such as Business Entity.

Next, choose how you want the Name field to be displayed: Title only, Title (ID), or ID (Title). This selection determines how the object is referenced throughout the system.

Finally, you can make the Title field required or optional. When Title is required, users must enter a Title before they can save an object record.

When the Title field is enabled, it's displayed to users so they can populate it on records of this object type. The Title component is also available within the Workflow Designer, GRC Calculations, and in the filters for the object type. If the Title field is empty on a record, then the value in the ID component is displayed.

Populating the Title field

You can use a script to populate the Title field with values from another field, such as Description. For more information, see Populating the Title component of objects.

Example of the Title field in a Grid View

The following example shows a Grid View for KRIs. In this example, the Title field is enabled for the KRI object type and the display is set to Title only. The Title displays in the Name column of the grid. Hovering over the entry displays the ID and Title of the object. The ID, Title, and Description are all available for search and filtering within the Grid View.

Figure 1. Example: A Grid View with Title enabled
The Grid View of the KRI object type is displayed. The Filter panel is open. The grid is filtered to show KRIs where Name.Title starts with Client Complaints. In the grid, the Name column displays the Title of the KRIs. The mouse pointer is on the name of a KRI. A tooltip displays both the ID and the Title of the KRI.

If the Title field is empty, the value of the ID component is displayed in the Name column.

Example of the Title field in a Task View

The following example shows a Task View for KRIs. In this example, the Title field is enabled for the KRI object type and the display is set to Title only.

The Title is displayed in the Task View header and within the relationship tree diagram.

Figure 2. Example: A Task View with Title enabled
The Task View of the KRI object type is displayed. The header of the view displays the Title field. The view contains a tree diagram. Within the tree, the Title of the KRI is shown.
When you click the Name field, both the ID and Title are displayed if at least one of them is editable. In this example, the Title is editable and optional.
Figure 3. Example: The Name field with the ID and Title components
The General section of a Task View is displayed. The Name field shows two components: ID and Title. The Title component has a text box that is editable.

Example of the Title field in the View Designer

The following example shows the Name field in the View Designer. When you click the Name field, the ID and Title are displayed. In this example, the Title is editable and optional for this Task View.

Figure 4. Example: A Task View with Title enabled
The View Designer in shown. In the side panel, two toggles are available for the Title component: Read Only and Required. Both toggles are turned off in this example.