Using Custom Fields and Custom Field Values

Custom fields provide users who are not system administrators the ability to define fields for capturing project-specific metadata using the client GUI.

Project administrators with appropriate permissions to create or edit an instance of a project backing item can define custom fields. When items are associated with a specific project, those items allow users to specify values for the custom fields defined on the project backing item.

Users with appropriate permissions to edit an instance of an item can modify the custom field values.

For more information, see “Specifying Custom Field Values” in the .

For more information, see Specifying Custom Field Values.

Custom Fields Pre-Requisites

For project administrators to configure custom fields on project backing items, an system administrator must complete the following actions using the GUI:

  1. Define a project backing item type and enable the Back Projects attribute on the type.

  2. Define field visibility for Custom Fields for the project backing item type.

For more information on these pre-requisite actions, see the following topics:

To...

See this section...

Define a project backing item type

Managing Metadata for Workflow and Document Projects

Define field visibility

Setting Field Visibility for Types

In addition to the pre-requisites, project backing items also must be created. system administrators can create a project backing item using the GUI. For more information, see To back a workflow and document project with an Item.

The Custom Fields field can only be visible on a Type that backs projects. The Custom Field Values field can then be set as visible on Types where users set custom field values.

Defining Project-Specific Custom Fields

system administrators can define custom fields on a project backing item using the GUI.

For more information on defining custom fields, see “Defining Project-Specific Custom Fields” in the .

For more information on defining custom fields, see Defining Project-Specific Custom Fields.

Key Considerations

The Custom Fields field is created automatically in an Integrity system, in version 10.9 or later. To enable users to set custom field values on items, a system administrator must complete the following tasks:

  • Make the Custom Field visible on the item type that is backing their project.

  • Make the Project field visible on the target item type.

  • Make the Custom Field Values field visible on the target item type.

Once project administrators have created custom field definitions on the project backing item, users can specify custom field values on items that participate in that project.

Relevance and editability rules apply to the Custom Field field and the Custom Field Values fields as a whole, and not to individual fields or values. For more information, see Setting Field Relevance and Setting Field Editability.

Known Limitations

When working with Custom Fields and Custom Field Values, note the following limitations:

  • Mandatory fields on an item Type cannot include Custom Fields or Custom Field Values.

  • The visible fields on an item Type cannot include both Custom Fields and Custom Field Values.

The following functional areas do not support Custom Fields or Custom Field Values:

  • Trigger rules

  • Type constraints

  • Type attributes

  • Query Backed Relationship (QBR)

  • Item Backed Pick List (IBPL)

  • Field Value Attribute (FVA)