Define the Value Set and Behavior Set Values

You can add values to dynamic data sets (DDSs) manually one a time, or by importing multiple values from a CSV file. The following describes adding DDS values manually.

Fields defined with a Value Set have values limited by the master data element (DE). For example, a Country master DE can control the values that display for a State field.

To define the value set and behavior set combination:

  1. Go to the Company Workspace tab, and switch to Admin mode.
  2. In the left Navigator, select Data Structure Setup, and then select Dynamic Data Sets. The Dynamic Data Sets log opens.
  3. Select the DDS, and select Open. The dynamic data set log opens for the selected set.
  4. Select New. The Add/Edit <set name> window opens.
  5. Complete the window. The fields on the window will depend on how the set was designed. It may include a value set, a behavior set, or both:
    • Value Set: These are the data elements that will be controlled by master data element selection at runtime. The Master data element is the first element on the list.

      Select the drop-down list, and select a value for each data element. The drop-down list values are based on the data set values defined under the base data definition.

      In the example in the following figure, the value set is Country and State. At runtime on the form, when the user selects a Country, the State field will populate with the states that are associated with that country. These value sets determine the combinations of Country-State that display.

    • Behavior Set: The behavior of these data elements (Required, Disabled, Disabled and Clear) will be controlled by the master data element selection at runtime.

      Select the drop-down list, and select Required (Field displays a *), Disabled (Field is read-only), or Disabled and Clear (Field is cleared and disabled, becoming read-only). If you leave the selection blank (or "Select" on the drop-down), there will be no change in behavior for the element.

      For classic Payment Application and General Spends Change Commit detail forms, the SOV Line Picker (uuu_sovlinum) can be included in a behavior set. You can set it to Required, Disabled, or Disabled and Clear. At runtime, its behavior changes when the user changes the master DE value. If you select Disabled and Clear, the system clears the selected SOV Line Picker value and makes the field read-only. This capability is not supported for Summary Payment Application (SPA) Change Commit business processes (BPs).

      In the example in the following figure, the behavior set is Mail Stop and Zip Code. In this case, at runtime, depending on the Country chosen, either Mail Stop or Zip Code will become a required field, or will be disabled.

  6. To add another Value Set and Behavior Set combination, select Add, which will save the combination you just entered and let you add another.
  7. When you are done adding combinations, select OK. The set displays on the dynamic data set log.

Data Elements that You can Set as Disabled and Clear

The behavior set fields of all data types can be set as Disabled and Clear. Exceptions are mentioned below:

  • Status
  • Due_Date
  • Creator_ID
  • Record_No
  • Data elements starting with “uuu,” except for the SOV Line Picker (uuu_sovlinum) when it is configured as a behavior-set element on a classic Payment Application or General Spends Change Commit detail form
  • Data definitions starting with “SYS,” and the ones not of the following input types:
    • Text
    • Textarea
    • Picker
    • Date Picker
    • Date Only Picker
    • Bitemid