An item is part of an HTML form. Examples of page-level item include a check box, a date picker, plain text, a file browse field, a popup list of values, a select list, a text area, and so on.
This section describes what a page-level item is, how to view existing page-level items, how to create new page-level items, and how to edit an item in Page Designer to change its appearance or behavior.
Parent topic: Managing Database Application Controls
Learn how to view page-level attributes in Page Designer.
Item attributes affect the display of items on a page. For example, these attributes can impact where a label displays, how large an item is, and if the item displays next to or below the previous item.
To view page-level attributes in Page Designer:
Parent topic: Managing Page-Level Items
You create page-level items in Page Designer in either the Rendering tab or by adding an item from the Gallery.
Parent topic: Managing Page-Level Items
To create a page-level item from the Rendering tab:
See Also:
Parent topic: Creating Page-Level Items
To create a page-level item by adding if from the Gallery:
See Also:
Parent topic: Creating Page-Level Items
One way to create a static list of values is to edit an item's List of Values definition. Note that this type of list of values is not reusable. As a best practice, create a list of values as a shared component whenever possible.
To create a static list of values:
Parent topic: Creating Page-Level Items
In this example, the list of values has four values (Cow, Dog, Cat, and Lion) that display in alphabetical order. The return value of each entry equals the display value.
STATIC:Cow,Dog,Cat,Lion
Parent topic: Creating a Static List of Values
In this example, the list of values has ten values that display in the order listed in the definition. The return value of each entry equals the display value.
STATIC2:10,15,20,25,50,100,200,500,1000,10000
Parent topic: Creating a Static List of Values
In this example, the list of values has two values: Yes
and No
(the display value Yes
and its return value Y
, and the display value No
and its return value N
).
STATIC:Yes;Y,No;N
Parent topic: Creating a Static List of Values
By creating a cascading list of values (LOV), one item on a page determines the list of values for another item. App Builder includes cascading LOV support for the following item types: Select List, Shuttle, Checkbox, Radio Group, Popup LOV, and List Manager.
You create a cascading LOV by creating two items. To populate the second item, you specify a Cascading LOV Parent Item when running the Create Item Wizard or by editing the item's attributes.
The following example demonstrates how to create two related select lists where the value of the first list populates the second.
To create a cascading list of values:
Create the first item and name it P1_DEPTNO:
Create a select list item.
For Identification, Type, select Select List.
For Identification:
Name - Enter:
P1_DEPTNO
Type - Select Select List.
For Label:
Label - Enter:
Department
For List of Values:
Type - Select SQL Query.
For SQL Query, enter:
SELECT dname as d, deptno as r FROM dept ORDER BY dname
Display Null Value - Select Yes.
Null Display Value - Enter - Select:
- Select Department -
Accept the remaining defaults.
Click Save.
Create the second item named P1_EMPNO
:
Create a select list item.
For Identification, Type, select Select List.
For Identification:
Name - Enter:
P1_EMPNO
Type - Select Select List.
For Label:
Label - Enter:
Employee
For List of Values:
Type - Select SQL Query.
For SQL Query, enter:
SELECT ename as d, empno as r FROM emp WHERE deptno = :P1_DEPTNO ORDER BY ename
Display Null Value - Select Yes.
Null Display Value - Enter - Select:
- Select Employee -
Accept the remaining defaults.
Click Save.
Two select lists appear. Making a selection in the Department select list, determines which individuals display in the Employees select list.
Parent topic: Creating Page-Level Items
This section demonstrates how to create shuttle item type. First, you first create a report and form on the DEPT
table that shows which employees are assigned to a given department. Second, you create a shuttle item that lists employees alphabetically to make it easier to assign employees to a department.
To create a shuttle on the form page:
Parent topic: Creating a Shuttle Item
Developers edit Item attributes in Page Designer to control how items display on a page.
For example, item attributes can determine where a label displays, how large an item is, and if the item displays next to or below the previous item. Item attributes also control item behavior such as the item’s default value, whether the item displays conditionally, or if the item is read-only.
Parent topic: Managing Page-Level Items
To edit item attributes in the Property Editor:
Parent topic: Editing Page-Level Items
You define default values for an item using the attributes under Default on the Edit Page Item page. The default value is used when the item's value is not derived from session state and when the source value is NULL
.
To define a default value for an item:
Parent topic: Editing Page-Level Items
To configure page item security:
Parent topic: Editing Page-Level Items
Quick picks enable users to select predefined values with just one click, rather than typing in text or selecting from a list of available options. If the item type supports quick pick selection, use the Quick Picks attributes to define up to ten selections that display under a give item. Clicking on a quick pick sets the value of item. The following example shows quick picks for 5%, 10%, 15%, and 20%.
To create a quick pick:
Parent topic: Editing Page-Level Items
To display a conditional item:
Parent topic: Editing Page-Level Items
To display a read-only item:
Parent topic: Editing Page-Level Items
To apply a format mask to an item:
Parent topic: Editing Page-Level Items
Developers can use the Warn on Unsaved Changes item attribute to specify if the page item should be included in the unsaved changes check. This check warns the user when they try to navigate away from a page and when the page contains unsaved changes. Items not based on a database column (for example, a search item) may not need to be checked. For those items, set Warn on Unsaved Changes to Do Not Check.
To configure the Warn on Unsaved Changes attribute:
Tip:
The Warn on Unsaved Changes attribute is implemented using the apex.page.warnOnUnsavedChanges
API.
See Also:
"Configuring Page Attributes to Warn Users of Unsaved Changes" and Oracle Application Express API Reference
Parent topic: Editing Page-Level Items
The Utilities page includes Grid Edit pages and reports that enable you to edit items on multiple pages within a selected application.
To access the Utilities page:
Parent topic: Editing Page-Level Items