Configure request field status dependencies

On a request, field behavior can be linked to the status of the request. For example, a request cannot move to the Assigned status unless the Assigned to User field contains a value. You can configure request field status dependencies using Workbench, or in 24.3 and later versions, using the web UI.

In this topic:

Use web UI

Available in 24.3 and later versions

Configure request field dependencies from the Request Type Setting page, Layout tab.

To assign field properties based on request status using web UI:

1. On the PPM menu, click Open > Administration > Manage Request Types to open the Manage Request Types page.

2. Click the name link of the target request type.

3. On the Request Type Setting page, click the Layout tab.

4. Click the field to which you want to assign field properties based on request status. The field properties appear.

5. In the field properties that appear, go to the Status Dependencies area and configure the following field properties. Changes are saved automatically.

   Field property	Description
   Visible	Determines the visibility of the field to users when a request is in the selected statuses. If set to No, the field is hidden when the request is in the selected statuses.
   Editable	If the Editable option for a request field is set to No for a specific status, users cannot edit the field when the request is in that status. In addition, if the Required or Reconfirm option for a request field is set to Yes, the Editable option must also be set to Yes. In certain stages in a request resolution process, you may want to prevent changes to a specific field. For example, when a Vendor Bug request reaches the Patch Applied status , you want to enforce that the Patch Number field remains unchanged. To achieve this, you set the Patch Number field to be read-only for all subsequent request statuses in the workflow. In addition, you would also make the Patch Number field required in an earlier status to ensure it has a valid value before it becomes read-only.
   Required	Specifies whether the field is required when in the selected request statuses. If a field is required, a value must be provided for the field before the request can move to the selected status. During the workflow transition, a "look-ahead" page prompts to user to fill any required fields that are empty.
   Reconfirm	If the Reconfirm option for a request field is set to Yes, the field appears on the "look-ahead" page before the request can be transitioned to this status. The user can review and, if necessary, change the field value.
   Clear	The Clear option is used together with other dependencies to remove the field content. The clear option is used as follows: If set to Yes and either or both the Required and Reconfirm options are set to No, the field is not displayed on the look-ahead page but is automatically cleared when the request moves to the new status. If set to Yes and either or both of the Required and Reconfirm options are also set to Yes, the field is cleared and displayed on the look-ahead page when the request moves to this status. If Required, the user must provide a valid value in the field before the request can complete the transition to the new status. If only Reconfirm, users can choose whether to provide a value before continuing. Note: To display the Reconfirm field on mass update of records, set the Clear field to Yes.

Back to top

Use Workbench

You can configure field dependencies from the Status Dependencies tab in the Request Type Workbench.

To assign field properties based on request status from Workbench:

1. On the PPM Workbench shortcut bar, click Demand Mgmt > Request Types.

2. In the Request Type Workbench, open the target request type and then click the Status Dependencies tab.

3. From the Request Status list, select one or more request status values.

4. In the Field table, select the request field for which you want to configure properties based on the selected request status.

5. Under the Field section, set the options described in the following table.

   Option	Description
   Visible	See Visible.
   Editable	See Editable.
   Required	See Required.
   Reconfirm	See Reconfirm.
   Clear	See Clear.

   Note: You can also control field attribute such as Editable and Visible by configuring an advanced request type rule that includes JavaScript-based logic. For details, see Advanced rules for request types.

   You can configure multiple fields simultaneously by using the Ctrl or Shift keys to select the fields and then change the attribute values. You can also select multiple status values and change the same fields if those states require the same attribute values for the same fields.

6. Click OK.

Back to top

Status dependencies interactions

Table 5-4. Status dependencies interactions shows the results of different combinations of the Required,Reconfirm, and Clear selections. For each request status within a request type, there can be up to a maximum of 250 fields with a required state and 250 fields with a reconfirm state.

Table 5-4. Status dependencies interactions

Dependencies			Results at Given Status
Required	Reconfirmed	Clear	Display	Color	Data Shown
No	No	No	No	N/A	N/A
No	No	Yes	No	N/A	N/A
No	Yes	No	Yes	Black	Current Data
No	Yes	Yes	Yes	Black	None
Yes	No	No	Yes, if NULL Note: If a field is required, it is displayed only if its value is blank (NULL). The user must provide a non-NULL value to proceed. If the field already contains a value, it satisfies the Required dependency and does not need to be displayed on the look-ahead page.	Red	None
Yes	No	Yes	Yes	Red	None
Yes	Yes	No	Yes	Red	Current Data
Yes	Yes	Yes	Yes	Red	None

Back to top

See also:

• Configure request statuses for request types
• Request type rules