Page Property Defined In Oracle Apex Does Not Display
Solution 1:
Troubleshooting Oracle Apex Page Display Settings and Attributes
A mocked up scenario would be where a defined page item is placed in the Page TITLE
field, but the value does not show up when the page is "run".
Excluding more obvious developer errors such as misspelled or inconsistently applied page item names, it is possible that there is nothing wrong at all... except that a custom application template/theme has excluded or accidentally left out the necessary html block from its definition:
<TITLE></TITLE>
. This is easily searchable and confirmed by viewing the Application Theme or Template defined under theSHARED COMPONENTS
section.
Considering the Effect of Custom Developer Assigned Application Templates...
Applying a custom PAGE typed template to an example where the page title does not display, we get an original templated html script, complete with placeholders for all the input data values that are a part of the output display:
<!DOCTYPE htmlPUBLIC"-//W3C//DTD HTML 4.01 Transitional//EN"><head>
#HEAD#
<title>#TITLE#</title></head><body #ONLOAD#>#FORM_OPEN#<aname="PAGETOP"></a>
Note the line: <title>#TITLE#</title>
, without it, there would be no page title if this template were used. To verify, the template script/html is rewritten and the line is deleted. The result:
Modifying a Page Template
Associating the Modified Page Template to the Apex Page
Setting the Value for the Page Item Associated with the page title.
Trying to Set an alternate Value for the Page Item Associated with the page title.
No matter what value is set to the associated page item, the page attribute of "TITLE" does not populate (see the title of the tab associated with the demo pages).
Page templates and output rendering processes are possible places to look first when troubleshooting a missing attribute already defined within the application design.
Using an Alternate Page to Set the HTML TITLE
Page Property
If the problem is not with a custom template or if the template selected is a default or Oracle "standard" template, there are other considerations:
This is the design layout of a "broken" Apex page where the html TITLE property is defined by a page level item that exists on the same page:
- The Display Attribute of the Page is set with a substitution value referencing a page level item defined on the same page:
&P12_PAGE_TITLE.
. - For this example, the page level item
P12_PAGE_TITLE
is defined as a Display Only type.
If the page item SOURCE
value is set to the "title" explicitly, this does not work. I figured out a working solution by setting the item, P12_PAGE_TITLE
by using a COMPUTATION
operation set up on another page.
This is the layout of the "testing" external page that sets the P12_PAGE_TITLE
item value before the target page is redirected and the TITLE html property is rendered.
- Set up a text box for free-form entry:
P14_PICK_PAGE_TITLE
- Make a form Button:
P14_SUBMIT_TITLE_CHOICE
with aSUBMIT
action. - A
COMPUTATION
designedAFTER SUBMIT
transfers the value entered on the test page (P14) and sets the value on the target page, P12. - A
BRANCH
action is defined to runAFTER PROCESSING
(as well asAFTER COMPUTATIONS
andAFTER SUBMIT
) - The
BRANCH
action is set to trigger when the button defined in step (2) is selected.
This is the result:
The form designed on an alternate page for collecting the designated page title.
This is the target page based on the selected title stored in the display-only page item displayed in the TITLE SELECTION region of the final target page.
Additional Discussion:COMPUTATION
fields can assist with ensuring that page level items are assigned their value in advance of other page rendering activities. Otherwise, the source or assigned data value is not read until after most of the page has been rendered.
When a page item value is assigned/set is just as important as the data value put into it.
Post a Comment for "Page Property Defined In Oracle Apex Does Not Display"