hi
Please consider the use-case where part of a query condition should be specified by selecting one of a few options using radio buttons on a page.
For example there could be a JOB_CATEGORY that only has a few valid values, 'jobcat-ad', 'jobcat-fi', 'jobcat-it' or 'jobcat-other', as resulting from a query like this:
SELECT Employees.EMAIL,
Employees.EMPLOYEE_ID,
Employees.JOB_ID,
(case substr(job_id, 1, 2) when 'AD' then 'jobcat-ad' when 'FI' then 'jobcat-fi' when 'IT' then 'jobcat-it' else 'jobcat-other' end) AS JOB_CATEGORY
FROM EMPLOYEES Employees
Sometimes it could be convenient to be able to select a JOB_CATEGORY using a radio button as part of a query action, as illustrated in the screenshot in "
QRBA-executeEmployeesVO.png".
This example application created using JDeveloper 11.1.1.3.0
at http://www.consideringred.com/files/oracle/2010/QueryRadioButtonsApp-v0.01.zip
has an approach using an "executeWithParams" action binding and an approach using an af:query component,
see also the screencast at http://screencast.com/t/PEX8Vh3ieX
Note, the LOV "LOV_JobCategory" has on its "UI Hints" tab for "Default List Type" a value of "Radio Group", but in the af:query component it is shown as a choice-list/drop-box .
Note, the "executeWithParams" action binding page uses an af:selectOneRadio component depending on a list binding that does
not use an LOV defined in the Business Components.
questions
- (q1) Why are the values for JobCategory shown as a drop-box in the af:query component while the "Default List Type" is configured as "Radio Group"?
- (q2) Is it possible to show radio buttons in an af:query component to select a value for one of the "query attributes"?
- (q3) What are the options (when not using af:query) to use an LOV defined in the Business Components to show radio buttons to select a value as query input?
many thanks
Jan Vervecken