Altering Page Attributes
Page attributes control specific characteristics of a page such as the page name, display attributes such as the page title and the associated page template, header text, and the selected authorization scheme. You access page attributes from the Page Definition.
Accessing Page Attributes
To edit page attributes:
-
Navigate to the Page Definition. See "Accessing the Page Definition".
-
To access the Edit Page:
-
Tree view - Under Page Rendering, double-click the page title at the top of the tree.
-
Component view- Under Page, click the Edit All icon.
The Page Attributes page appears. Required values are marked with a red asterisk (*).
-
About Page Attributes
The Page Attribute page is divided into the following sections: Name, Display Attributes, JavaScript, HTML Header and Body Attribute, Header and Footer, Security, Duplicate Submission, Server Cache, Configuration, Error Handling, Help, and Comments.
Description of the illustration pg_att_nav.gif
You can access these sections by scrolling down the page, or by clicking a navigation button at the top of the page. When you select a button at the top of the page, the selected section appears and all other sections are temporarily hidden. To view all sections of the page, click Show All.
The topics that follow describe the specific sections of the Page Attributes page.
Name
Use these attributes to define general attributes for the current page such as a page name, an optional alphanumeric alias, and associated page groups. To learn more, see Table 8-1.
Table 8-1 Page Attributes: Name
| Attributes | Descriptions |
|---|---|
|
Identifies the name of the current page for application developers. This name is used in numerous pages and reports, along with the page number and page title. |
|
|
Enter an alphanumeric alias for this page. This alias must be unique within the current application. For example, if you were working on page 1 of application 100, you could create an alias called f?p=100:home |
|
|
Identify the page group you would like to associate with this page. Page groups do not affect functionality, but help developers manage the pages within an application. To remove a page from a group, select No Group Assigned and click Apply Changes. See Also: "Grouping Pages" |
Display Attributes
Use these attributes to define general display attributes for the current page such as the selected page template, standard tab set, title, and cursor focus. To learn more, see Table 8-2.
Table 8-2 Page Attributes: Display Attributes
| Attributes | Descriptions |
|---|---|
|
Select a page template to control the appearance of this page. Making a selection here overrides the default page template defined within the current theme. |
|
|
Select a standard tab set to be used for this page. A standard tab set is associated with a specific page and page number. You can use standard tabs to link users to a specific page. See Also: "Creating Tabs" |
|
|
Enter a title to display in the title bar of the browser window. The Application Express engine uses the title you specify here in place of the #TITLE# substitution string used in the page template. This title is inserted between the HTML tag |
|
|
Enter the Internet Media Type. An Internet Media Type is two-part identifier for file formats on the Internet. A Media Type is composed of at least two parts: a type, a subtype, and one or more optional parameters. This Media Type is used in the Content-Type HTTP header when rendering the page. The page-level Media type overrides the application-level media type. The default value for this attribute is |
|
|
Specify the cursor focus. Available options include: |
JavaScript
Use these attributes to include JavaScript on the current page. To learn more see Table 8-3.
Table 8-3 JavaScript Attributes
| Attribute | Description |
|---|---|
|
Enter JavaScript code (for example, functions or global variable declarations) for code to be used on this page. If the code is used on multiple pages, consider putting it into an external JavaScript file to avoid duplication. Note: You do not need to include opening or closing script tags. Just include the JavaScript code. Code you enter here replaces the To reference a shortcut, use: "SHORTCUTNAME" |
|
|
Enter JavaScript code to execute when the page loads. The code is executed after the JavaScript code generated by Oracle Application Express. Note: You do not need to add any opening or closing script tags, just the JavaScript code. To reference a shortcut, use: "SHORTCUTNAME" |
|
|
Oracle Application Express typically requires specific JavaScript and CSS files. For some applications, such as mobile applications, you may wish to suppress the inclusion of these files in the HTML header. For Include Standard CSS and JavaScript, select Yes to suppress the inclusion of cascading style sheet (CSS) and JavaScript files in the HTML header. Because suppressing the display of these files breaks typical applications, enabling this attribute is only recommended for advanced developers. |
HTML Header and Body Attribute
Use these attributes to define page header and body header text. To learn more, see Table 8-4.
Table 8-4 HTML Header and Body Attributes
| Attribute | Description |
|---|---|
|
Enter text to replace the
|
|
|
Enter text or HTML you want to appear before the page template footer. |
Header and Footer
Use these attributes to define header and footer text. To learn more, see Table 8-5.
Security
Use these attributes to specify an authorization scheme and authentication requirements for the current page. To learn more, see Table 8-6.
Table 8-6 Page Attributes: Security
| Attribute | Description |
|---|---|
|
Select an authorization scheme to be applied to the page. Authorization schemes are defined at the application level and can be applied to many elements within the application. An authorization scheme is evaluated either once for each application session (at session creation), or once for each page view. If the selected authorization scheme evaluates to true, then the page displays and is subject to other defined conditions. If it evaluates to false, then the page will not display and an error message displays. |
|
|
Specifies whether this page has been defined as public or requires authentication. If a page is identified as public, the page can be viewed before authentication. This attribute only applies to applications requiring authentication. The application's page sentry function can access this page attribute to identify pages that do not require prior authentication to view. The implementation of the authentication scheme's page sentry function determines if this attribute has any effect. See Also: "Establishing User Identity Through Authentication" |
|
|
Page Access Protection |
Note: This attribute only displays if Session State Protection has been enabled for the application. See "Understanding Session State Protection". Select a Page Access Protection level for the current page:
|
|
Setting this attribute to On has no effect on the page. Setting this value to Off generates the following HTML in the FORM tag: autocomplete="off" |
Duplicate Submission
Use the Allow duplicate page submissions list to specify whether users may process a page multiple times in a row. Set this attribute to No to prevent duplicate page submissions from being processed multiple times.
Examples of duplicate page submissions include:
-
A user clicks the Submit button multiple times.
-
You create a branch of type Branch to Page, and the user clicks the browser reload button.
In On duplicate page submissions go to this URL, enter a URL. Use this field if you set Allow duplicate page submissions to No. If you select No and a user attempts to submit the same page twice, Oracle Application Express displays an error message and a link to the URL you specify.]
Cache
Use these attributes to enable caching for the current page. Enabling page caching can improve the application's performance and works well for static pages. To learn more, see Table 8-7.
| Attribute | Description |
|---|---|
|
Specify whether to enable page caching by selecting Yes or No. Page caching can improve performance because the page displays from the cache instead of displaying dynamically. |
|
|
Specify the amount of time for which a cached page remains valid. |
|
|
Specify if the page should be cached by user. If Yes, the page is cached specifically for each user. If No, the same cached page is used for all users. |
|
|
Specify a condition. If the condition returns false, the page is rendered dynamically and is not to be cached. If the condition returns true, the page is displayed from the cache. |
|
|
Displays conditionally based on the selected Cache Page Condition. Enter values in this attribute based on the specific condition type selected. |
|
|
Displays conditionally based on the selected Cache Page Condition. Enter values in this attribute based on the specific condition type selected. |
See Also:
"Managing Cached Regions and Pages" in Oracle Application Express Administration Guide and "Utilizing Region Caching"Configuration
Select a build option for this page. You can use build options to enable or disable functionality. Most application attributes have a build option attribute. Do not specify a build option for the current page unless you plan to exclude the page in certain configurations.
Build options have two possible values: INCLUDE and EXCLUDE. If you specify an attribute as being included, then the Application Express engine considers it part of the application definition at run time. Conversely, if you specify an attribute as being excluded, then the Application Express engine treats it as if it did not exist.
Error Handling
Use the attributes described in Table 8-8 to control or modify how an application logs errors.
In-line Error Notification Text, enter the error text that displays in the #NOTIFICATION_MESSAGE# template substitution string in the event an error occurs on the page.
Table 8-8 Page Attributes, Error Handling
| Attribute | Description |
|---|---|
|
Enter the error text that displays in the |
|
|
Enter the name of a PL/SQL error function to modify the existing error message and display location or log the error if one occurs. This function can reference a package function or standalone function in the database. For example: log_apex_error When referencing a database PL/SQL package or standalone function, use the #OWNER#.log_apex_error You must implement error handling functions using the syntax described in the
function <name of function> (
p_error in apex_error.t_error )
return apex_error.t_error_result
See Also: Note: Error handling specified at the page-level overwrites any error handling function specified at the application-level. See "Editing the Application Definition". |
See Also:
"Page Templates"