Configuring User Data Field Dependencies

Field behavior and properties can be linked to the value of other fields defined for that entity. A Report Type field can become required when the value in another field in that report type is Critical.

You can configure a field to:

  • Clear after the value in another field changes.

  • Become read-only after another field meets a logical condition defined in Table 10-2. Field dependencies.

  • Become required after another field meets a logical condition defined in Table 10-2. Field dependencies.

  • Table 10-2. Field dependencies

    Logical Qualifier

    Description

    like

    Looks for close matches of the value to the contents of the selected field.

    not like

    Looks for contents in the selected field that are not close matches to the specified value.

    is equal to

    Looks for an exact match of the value to the contents of the selected field.

    is not equal to

    Is true when no results exactly match the value specified in the field.

    is null

    Is true when the selected field is blank.

    is not null

    Is true when the selected field is populated.

    is greater than

    Looks for a numerical value greater than the value specified.

    is less than

    Looks for a numerical value less than the value specified in the field.

    is less than
    equal to

    Looks for a numerical value less than or equal to the value specified.

    is greater than
    equal to

    Looks for a numerical value greater than or equal to the value specified.

To configure a user data field dependency:

  1. On the PPM Workbench shortcut bar, click Configuration > User Data.

    The User Data Workbench opens.

  2. Open a user data type.

    The User Data Context window opens to the Fields tab.

  3. Select the field, and then click Edit.

    The Field window opens.

  4. Click the Dependencies tab.

  5. Use the following fields to set the field dependencies:

    • To clear the current field whenever the value in another field changes, from the Clear When The Following Changes list, select the field to trigger the clearing of the current field.

    • To make the field become read-only after another field satisfies a logical criterion, from the Display Only When list, select the field which, when changed, is to make the current field read-only.

      The Display Only When list functions with the two lists to the right. One is a list of logical qualifiers (described in Table 10-2. Field dependencies), and the other, a list that dynamically changes to a date, list, or text field, depending on the validation specified for the current field.

    • To make the current field become required after a selected (trigger) field meets the condition selected from the list of logical qualifiers (described in Table 10-2. Field dependencies), from the Required When field, select a trigger field

      The Required When list functions with the two lists to its right. One is a list of logical qualifiers (described in Table 10-2. Field dependencies), and the other, a list that dynamically changes to a date, list, or text field, depending on the validation specified for the current field.

  6. Click OK.

  7. In the Field window, click OK.

  8. In the User Data Context window, click OK.