Configuring Field Dependencies
Field behavior and properties can be linked to the value of other fields defined for that entity. For example, an object type field can become required when the value in another field in that object type equals the text Critical.
A field can be configured to:
-
Clear when another field changes.
-
Become read only when another field meets a logical condition defined in Table 5-1. Field dependencies.
-
Become required when another field meets a logical condition defined in Table 5-2. Example conditions.
To configure a field dependency:
-
From the Workbench shortcut bar, select Deployment Mgmt > Object Types.
The Object Type Workbench window opens.
-
Open an object type.
The Object Type window opens.
-
Select and edit an existing field or create a new field.
The Field window opens.
-
Click the Dependencies tab.
-
Set the field dependencies, using one of the following options:
-
In the Clear When the Following Changes field, select a field name to indicate that the current field is to be cleared if the selected field changes.
-
In the Display Only When field, select a field name to indicate that, if certain logical criteria are satisfied, the current field is to be read-only.
This field functions with two adjacent lists that contain logical qualifier, and a field which dynamically changes to a date field, list, or text field, depending on the validation of the selected field.
-
In the Required When field, select a field name to indicate that the current field is to be required if certain logical criteria are satisfied.
This field functions with two adjacent lists that contain a logical qualifier, and a field that dynamically changes to a date field, list, or text field, depending on the validation of the selected field.
-
-
Click OK.
This adds the field dependencies to the Fields tab of the Object Type window and closes the field window.
-
Click OK.