Databases Reference
In-Depth Information
When a user selects the department, a modal window is displayed with a report
listing all the employees in the selected department. The report will include the
employee's name, job, hire date, and salary.
When the user hovers over a report row, the row will be highlighted.
If the user clicks on a row in the report, the employee's number is stored in a
hidden field and the employee name is displayed beside the Employee label.
Right after an employee is selected, the name should be bolded for a few seconds
to emphasize that it has been changed.
Using Dynamic Actions, you'll be able to implement all these requirements. In order to simplify the
solution, it has been broken it up into small sections.
Setup
Before you start working on this example you'll need to modify a few things from the first example. You
will find an application that was configured with the following modifications in the Source
Code/Download area of the Apress web site at www.apress.com . You can skip this section if you import
the application 07_example-2_base_application.sql .
1.
Delete the Show Hide EmpNo dynamic action that was previously created. To
delete the Dynamic Action, edit it and click the Delete button.
2.
Change the P1_EMPNO Read Only attribute to Always as shown in Figure 7-25.
This is a trick to quickly have an item's display value shown and its actual value
hidden without having to create two separate page items.
Figure 7-25. Read Only value
Note Creating a select list item as Read Only will create two HTML elements on the page. The first is a hidden
element which stores the value of the item. This element's id is the same as the page item's name—for example,
P1_EMPNO. APEX will also create a second element which has the display value of the item. This second element
has an id of PX_ITEMNAME_DISPLAY. In the example this is P1_EMPNO_DISPLAY.
Search WWH ::




Custom Search