Databases Reference
In-Depth Information
LOVs can be defined either as shared components at the application level or at the item level. Figure
5-62
shows
an item-level definition. An LOV used more than once should be written as a shared component. This allows the
maintenance of that LOV to be centrally located with the shared components. If an LOV is created at the item level,
it's easy to convert it to a shared LOV by using a utility that APEX provides. When you view a component with an
item-level LOV, the page contains a Tasks menu with the Convert LOV option. Choosing this option makes the LOV a
shared component.
Figure 5-62.
An item-level LOV with static options
Static List of Values
A static list of values is simply a set of display and return value pairs. This type of list is normally short and
unchanging. When you define a static list of values at the item level, there are two types of data options:
•
STATIC
: Entries are automatically alphabetized.
STATIC2
: Entries render in the order in which they're entered.
The syntax for specifying a static LOV is as follows:
•
TYPE:DISPLAY;RETURN,DISPLAY;RETURN,...
The
TYPE
may be either
STATIC
or
STATIC2
.
If you wish the display value and the return value for a given entry to be the same, omit the semicolon and specify
only one value. For example, the second item in the following example is a single value for both display and return:
TYPE: VALUE,VALUE,VALUE,...
The return value in a LOV is saved as the value of the associated form item. In static lists, using the semicolon as the
value of an entry may cause issues with parsing the list.
The following is an example of a static list. Commas separate the list items. Each list item is composed of a display
value and a return value, with a semicolon separating those two values:
STATIC:C;1,A;2,D;3,B;4,
