Single Selection Field Dependency Tutorial

Prerequisites:

This tutorial assumes you have an application workflow created in SBM Composer and are familiar with basic application tasks, such as adding fields and field selections.
To test this tutorial in the SBM User Workspace, you must have privileges to deploy to a running environment.

The following tutorial explains how to configure field dependencies that tailor the value list for a Single Selection field. You can reproduce this example for other field dependencies as needed.

In this example, you will create a Product field that has two available values: Product A and Product B. You will set dependencies to limit the values available in a Version field depending on the selection made in the Product field. For example, if a user selects Product A from the Product field, a set of available values unique to Product A are listed in the Version field.

This tutorial is configured exclusively in SBM Composer. You can log in to the SBM User Workspace to test the tutorial.

Tip: You can override dependent field values for independent Single Selection fields in projects in Application Administrator. For details, refer to Overriding Dependent Selections for Single Selection Fields in Projects.

To establish a dependency for two Single Selection fields:

In an application primary table in SBM Composer, create a Single Selection field named Product.
Select the Options tab for the Product field. Add the following values:
- Product A
- Product B
In the same table, create a Single Selection field named Version.
Select the Options tab for the Version field. Add the following values:
- 2.0
- 2.5
- 3.0
- 3.1
Select the Product field, and the select the Dependencies tab.
Select the Version field from the fields list to set it as the dependent field.
Select the Edit Value Restrictions link, and then select the workflow that contains the Version field. The Dependencies tab for the workflow opens.
Select Product A in the left pane, and then select the Version field check box in the middle pane. In the right pane, clear the 3.0 and 3.1 check boxes.
Select Product B in the left pane, and then select the Version field check box in the middle pane. In the right pane, clear the 2.0 and 2.5 check boxes.
Save, check in, publish, and deploy your changes.
Log in to the SBM User Workspace as a user who has privileges to view and update items in the application that contains the field dependency you added.
Submit an item into a project associated with the application workflow that contains the field dependency.

Values for the Version field are now dependent on the selection users make for the Product list. In this example, when Product A is selected from the Products list, the user can choose the None, 2.0, or 2.5 selections. When Product B is selected from the Products list, the user can choose the None, 3.0, or 3.1 selections.

Note: You can further enhance the dependency relationship by setting a default value for the dependent field. For example, you can set the Version field to default to 2.5 when Product A is selected in the Product field.