Databases Reference
In-Depth Information
When you display the values in this list, you see only the display values. Because the list is type
STATIC
, the values
are displayed in alphabetical order:
A
B
C
D
Next is an example of a
STATIC2
list. Notice that the entries are specified in the same order as before:
STATIC2:C;1,A;2,D;3,B;4,
However, this time the values are displayed in their order of definition. They are
not
sorted alphabetically:
C
A
D
B
Shared-component static LOVs have more options than item-level static LOVs. Due to their shared nature,
conditions and build option can be configured. These can be edited after the list has been created. Because the lists
are stored differently as shared components, it's possible to use a semicolon in the item value.
Dynamic List of Values
As with static LOVs, dynamic LOVs have a display and return value pair requirement. The difference is that the values
are obtained through a SQL query. The SQL query you write must return two columns. If the columns are the same,
you need to use aliases to distinguish a display value and a return value. You must also use an alias if you're using a
concatenated string as a column. Dynamic LOVs can also use session variables or values currently being used in the
application. This gives dynamic LOVs flexibility to dynamically change what is offered during runtime.
The example application needs two LOVs to support the selection of usernames. In preparation for building your
form pages, create a LOV to support the names of the users and the technicians in your Help Desk system:
1.
Navigate to the
Shared Components
section of the Help Desk application, then go to the
User Interface
section shown in Figure
5-63
, and click the
Lists of Values
link.
Figure 5-63.
User Interface options
