Database Reference
In-Depth Information
Items placed on a Global Page are rendered on every page in its related UI for that
application unless conditionally told to do otherwise. This is particularly useful when
you identify the need to display the same region on multiple pages or even on all pages
in your application. Simply move a region to your Global Page, and it's rendered with
every page.
A good example of usage is a breadcrumb region or a region that contains custom
JavaScript code that needs to be available to every page. Region contents from a Glob-
al Page are included on every page of that UI, even when a region doesn't render vis-
ibly.
Although you can assign any page number to a Global Page, the default page num-
ber for a Global Page related to a desktop interface is zero (0). In fact, Global Pages
take the place of what used to be called Page Zero in previous versions of APEX.
You may notice when looking at the definition of a Global Page in the APEX page
editor (
Figure 5-36
)
that there is no Page Processing section. Global Pages are only
used during page rendering. Regions that are added to a Global Page are included even
on the Login page. You need to consider the different page types in an application
when adding content to a Global Page.
Figure 5-36.
A Global Page for a desktop interface, as shown in the APEX page editor
