Add a field

You can add a custom field to a topic workflow configuration.

Adding a field adds a column to an Oracle database table, so you must specify the data type (for example, string, integer, or date). You can also make selections that affect how users interact with the field in the user interface, including the field label displayed, how users select values for the field, and whether the field applies to topics, actions, or attachments, or any combination of these contexts.

1. In the left navigation pane, click the Settings icon ().
2. In the Configure System section, click Manage Topic Workflow Configurations.
3. Click the configuration's Row Action menu (), and then click Edit.
4. On the Edit Topic Workflow Configuration page, click the Fields card.
5. To add a field, click the Add Field link.
6. In the Column name field, type the field name to appear in the Oracle database.

   The name must begin with a letter. It must be up to 30 characters in length, and consist of uppercase letters, numbers, and the special characters $, _, and # only.

7. In the Display name field, type the field name to appear in the user interface.

   The display name appears as the label for the field and as a column header, as the hover help text, and as a label above the field information in the Details panel.

8. From the Format drop-down list, select the type of data to be collected: string, integer, or date.

   Note:

   The options described in the steps below do not apply to date fields.
9. For string fields only, in the Length field, specify the maximum length.
10. Specify a type for the field. The type determines how you specify values for the field:
    • Single Value: This is the default field type.
    • Append-only: A multiple values field type in which a previously selected value cannot be removed (string fields only).
    • Multiple Values: A multiple values field type that supports adding and removing values (string fields only).
    • Linked: The subsidiary field in a linked pair.
    • Constrained values based on work team: An append-only field restricted to the work team context.
11. Select a context for the field. The field can appear as and store values for topics, topic actions, topic attachments, or work teams, or any combination of these contexts.
12. To limit the values that can be selected for a field based on the work team membership of the current user, select Work teams in addition to one of the other contexts. See Constrain field values by work team.

    Note:

    A superuser must set the Topic workflow configuration for work team custom fields site option to this configuration and the configuration must be published. If your organization uses more than one topic workflow configuration, you must define custom fields with the work team context identically in each topic workflow configuration.
13. Select Display as filter field to make the field available as a filter on the Topics and Actions tabs on the Topic Management page. See Identify a field as a filter field.
14. Click Save.

    Fields appear in the user interface as value-entry fields unless you explicitly define a valid set of values for them. For example, description fields are typically value-entry fields that allow users the flexibility to enter any value.

    You can define valid values for custom fields that have a format of string or integer, and for certain standard fields. Fields with defined values appear in the user interface as drop-down lists or, if you define a field as Append-only, as a multi-selection list. See Add a drop-down list field and Add a multi-selection list field.