Product Documentation

Allowed Value Lists give you the opportunity to have certain field lists and their values be dependent on other values in other list fields; for example, a list of specific Platforms may only be displayed if the connected parent Product is first selected. The following Parent Child relationships would be set up so that OS 9 or 10 platforms would only appear for Mac products, and Red Hat only appear for Linux.

In the above example, when you select the product named Macintosh Client, the ExtraView Add Issue or Edit Issue screen will refresh, and the field titled Platform will have the two values OS 9.x and OS 10.x.

This feature can be used both to ensure data entered is valid, and that data entry can be accomplished with a minimum of searching. Allowed Values can be “chained” together, providing a cascading set of values. Common examples of allowed values are:

1. Product name Module
2. Module Owner
3. Category Module Release (example of a cascading list)
4. Category Product name

You may create chains of any length of allowed values; in concept, think of a grandfather father child grandchild type relationship.

With some limitations it is also possible to build multiple allowed value relationships where the same child field may have two or three other fields, each of which is a parent in the allowed value relationship you are building. In this case, the child field is rendered using the intersection of the allowed values from each of the parents.

Not every combination of fields is allowable to be created as allowed values. For example, it is not possible to create an allowed value with a combination of MODULE_ID or MODULE_NAME and PRODUCT_NAME, as another inbuilt mechanism exists to handle this requirement.