Defining Allowed Values

You can specify the values allowed for the Parameter in several ways, found in the List of Values drop-down list. The system displays the appropriate interface for defining each after you make a choice.

• None. No list of allowable values is associated with the Parameter. The user can enter any value. You can define a Program to validate the value; see Defining Programatically Generated Lists of Values and Value Validation.

  You can specify a default value. To force the user to set a value at runtime, select Required and do not set a default value.

  The system validates that the default value conforms to the Parameter's data type and length (defined in the source Variable). If the data type is Date, the system checks that it is in the format specified in User Preference.

• Static List of Values. Create a list of specific values you want to allow for the Parameter. These values will appear as the only possible choices for the Parameter. Click Add Value to enter each value you want to allow. The system will display them in the list of values in the order in which they appear here.

  You can select one value to be the default value if you want to. To force the user to set a value at runtime, select Required and do not set a default value.

  The system validates that each value you define conforms to the Parameter's data type and length (defined in the source Variable).

  Note:

  Do not enter a comma (,) in the Parameter value string. The system interprets a comma as a delimiter between two different Parameter values.

• Classification List of Values. This option results in a list of allowable values that comprises the values at a particular level of a classification hierarchy.

  Select a classification hierarchy and level. The system generates a list of values equal to the set of values defined for that hierarchy level. For example, if you choose the Project, Study, and Site hierarchy and the Study level, the list of values includes all the Study names.

  If you define two Parameters in the same Program and base their allowed values on the same classification hierarchy, on two adjacent levels, the allowable values for the Parameter associated with the lower level are limited to those with a relation to the value chosen for the Parameter associated with the higher level.

  For example, if you define two Parameters whose possible values are linked to the Project, Study, and Site hierarchy, with one associated with the Project level and the other associated with the Study level, the possible values for the Project level Parameter include all the Project values in the hierarchy. However, the possible values for the Study level Parameter are limited to those related to the particular Project value selected. If the value for the Project-level Parameter is Project 1, the list of values that appears for the Study-level Parameter includes only those studies that are part of Project 1. If you change the value of the Project level Parameter to Project 2, the list of values for the Study level Parameter changes to studies that are part of Project 2.

  The same is true for Parameters linked to each lower level. In this example, you can define a third Parameter associated with the Site level whose values are limited to sites that are part of the particular study selected.

• Program Generated List of Values. You can define an Oracle LSH Program, or Source Code within a Program, specifically for the purpose of dynamically generating a list of values for a Parameter. You must check in and install the Program.

  You must write the source code in PL/SQL and use the following syntax to generate a list of values:

  FUNCTION <function name> (pi_paramRef IN CDR_PARAMETER_OBJ_TYPE,  
  pi_paramColl IN CDR_PARAMETER_COLL)
  RETURNS CDR_VALS_COLL;
  

  Click the Search icon and specify the Program and Source Code you want to use to generate the list of values for the Parameter.

  See Defining Programatically Generated Lists of Values and Value Validation for further information.