 |
|
Oracle Tips by Burleson |
Header
and Footer
The Header and Footer region is used to modify the
look of a region by allowing the user to provide HTML code that will
be inserted upon the region being rendered. A common use for this
feature within HTML DB is to add descriptive text to the top of a
region. For example, the copy region wizard in HTML DB displays
helpful text at the top of the regions and this is done by using the
Header and Footer.
Authorization
Custom authorization schemes can be created within
HTML DB. An authorization scheme may be something like IS_MANAGER or
CAN_EDIT_PRODUCTS. These authorization schemes can be created in
Shared Components ą
Authorization Schemes. The authorization scheme either evaluates to
TRUE or FALSE. If it evaluates to TRUE, the page component will be
rendered. If it evaluates to FALSE, the component will not be
rendered.
A common use for this would be for something such
as create or edit buttons. If the user has authorization to perform
edits, the buttons would be displayed. If not, the buttons would be
unavailable.
Customization
Although not a very technical description, this
feature is really cool! The developer wants to provide a page with ten
regions, which could be reports, forms, or any other type of region,
on the page, but some users may only be interested in any combination
of three or four regions. Instead of creating several pages to
satisfy each application user, all of the regions can be placed on a
single page and it can be made customizable. What this feature will
do is add a Customize link on the page thereby allowing the user to
display a popup with the names of all the regions. The user can then
select the regions they want to see and unselect the regions they do
not want to see.
In each of the regions, the developer can decide
if the region should participate in the customization popup window.
There may be one region to be displayed in any situation; whereas, the
rest of the regions can participate in user customization.
Customized Option Name
By default, the name to be shown in the popup
window will be the Region Title. The Customized Option Name is used
to provide an alternate name in the popup Customize Page.
This requires the developer to be using an
authentication scheme where each user has a separate login to the HTML
DB application. HTML DB must be able to distinguish between users so
it knows which regions to display next time the user renders the page.
Configuration
This region allows a Build Option to be selected.
A Build Option is used to enable or disable functionality within an
application. They are created in Shared Components
ą Build Options. When a
build option is created, it is given a status of INCLUDE or EXCLUDE.
If the status is INCLUDE, the components with that build option will
be rendered by HTML DB as normal. If the status is EXCLUDE, HTML DB
will ignore them during rendering. A build option can be assigned to
application pages, regions, page items, page processing, and other
page components to include them or exclude them from the rendering
process. For example, there may be a build named Version 1.1 that is
set to EXCLUDE. This build option may be assigned to page components
that are not ready to be rendered. Once testing is completed, the
version 1.1 build option could be set to INCLUDE and the page
components would be rendered in the application.
Comments
This is a good location to keep notes about the
report region. This area could be used to keep track of changes made
or perhaps plans to be made in the future.
The above book excerpt is from:
Easy HTML-DB
Oracle Application Express
Create Dynamic
Web Pages with OAE
ISBN 0-9761573-1-4
Michael Cunningham & Kent
Crotty
http://www.rampant-books.com/book_2005_2_html_db.htm
|
