This section provides important background information about creating and managing pages within and application.
This section contains the following topics:
A Page Definition is the basic building block of a page. Each page can have buttons and fields (called items), which are grouped into containers called regions. Pages can also have application logic (or processes). You can branch from one page to the next using conditional navigation; perform calculations (called computations); perform validations (such as edit checks); and display reports, calendars, and charts. You view, create, and edit the controls that define a page by accessing the Page Definition.
Topics in this section include:
You can view, create, and edit the controls that define a page through the Page Definition.
To access the Page Definition for an existing page:
On the Workspace home page, click the Application Builder icon.
The Application Builder home page appears.
Select an application.
The Application home page appears.
Select a page.
The Page Definition appears.
A Page Definition is the basic building block of a page. You use the Page Definition to view, create, and edit the controls and application logic that define a page. The sections that follow describe the different parts of the Page Definition.
Topics in this section include:
A navigation bar appears directly beneath the breadcrumb trail.
Available controls on the page navigation bar include:
Page. Displays the current page number. To view another page, enter the page number in the Page field and click Go.
Previous and Next. These buttons resemble less than (<) and greater than (>) signs. Click these buttons to move to the previous or next page.
View. Controls the current page view. To view alternative reports, make a selection from the list and click Go. See "Using the View List on the Page Definition".
The following buttons appear to the right of the navigation bar:
Run. Submits the current page to the Application Express engine to render viewable HTML. See "Running a Page or Application".
Copy. Creates a copy of the current page. You specify a page number and page name.
Create. Links to a wizard for creating a page. See "Creating a Page from the Page Definition".
The Run Page, Shared Components, Comment, Lock, Export Page, and Find icons display on the Action bar.
The Run Page icon resembles a small, light green traffic light. Click this icon to render the current page into viewable HTML. When you run a page, the Application Express engine dynamically renders the page based on data stored in the database. See "Running a Page or Application".
The Shared Components icon resembles a small mechanical gear. Click this icon to view a list of shared components and user interface controls that can display or be applied on every page within an application. See "Working with Shared Components".
The Developer Comment icon resembles a green balloon. Use this icon to add comments to an application, a page, or a group of pages. See "Adding Developer Comments".
The Lock icon indicates whether a page is available for editing. If a page is unlocked, the icon appears as an open padlock. If the page is locked, the icon appears as a locked padlock. Click this icon to change the lock status. See "Locking and Unlocking a Page".
The Export Page icon resembles a downward arrow. Click this icon to export the current page. See "Exporting a Page in an Application".
The Find icon resembles a flashlight. Click this icon to search for items, pages, queries, tables, PL/SQL, images, and cascading style sheets (CSS) within the current application or the schemas associated with the workspace. See "Using the Find Icon".
Every Page Definition is divided into three sections:
Page Rendering. Page rendering is the process of generating a page from the database. The Page Rendering section lists user interface controls and logic that execute when a page is rendered. See "About Page Rendering".
Page Processing. Page processing occurs once a page is submitted. Typically a page is submitted when a user clicks a button. The Page Processing section lists logic controls (such as computations and processes) that are evaluated and executed when the page is processed. See "About Page Processing".
Shared Components. The Shared Components section lists common components that can be used by one or more pages within an application. See "About Shared Components".
You can use the View list to quickly switch from a Page Definition to the Page Events, Database Object Dependencies, History, Export, Groups, and Referenced Components pages.
Topics in this section include:
To access other pages using the View list:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
Select a page.
The Page Definition appears.
From the View list, select one of the following:
Definition. See "Editing a Page Definition".
Events. See "About Page Events".
History. See "About History".
Export. See "About Export".
Groups. See "About Groups".
Referenced. See "About Referenced".
Page Events details all currently defined page controls and processes. This page provides a chronological view of how and in what order the Application Express engine renders the page, invokes logic, and runs processes.
A navigation bar appears directly beneath the breadcrumb trail. Available controls include:
Page. Displays the current page number. To view another page, enter the page number in the Page field and click Go.
View. Controls the current page view. To view alternative reports, make a selection from the list and click Go. See "Using the View List on the Page Definition".
Show All displays all possible page controls and processes, including those not currently defined.
Show Used displays currently used page controls and processes (Default).
Previous and Next. These buttons resemble less than (<) and greater than (>) signs. Click these buttons to move to the previous or next page.
To view details about a specific page control or process, click the appropriate hypertext link. Alternately, you can create page controls and processes by clicking the small icons to the left of each entry.
The Database Object Dependencies page displays a list of database objects referenced by the current page.
A navigation bar appears directly beneath the breadcrumb trail. Available controls include:
Page. Displays the current page number. To view another page, enter the page number in the Page field and click Go.
View. Controls the current page view. To view alternative reports, make a selection from the list and click Go. See "Using the View List on the Page Definition".
Previous and Next. These buttons resemble less than (<) and greater than (>) signs. Click these buttons to move to the previous or next page.
The History page displays a history of recent changes to the currently selected page by developer (or user), application, page number, modification date, component, and action.
A navigation bar appears directly beneath the breadcrumb trail. Available controls include:
Page. Displays the current page number. To view another page, enter the page number in the Page field and click Go.
View. Controls the current page view. To view alternative reports, make a selection from the list and click Go. See "Using the View List on the Page Definition".
Display. Determines how many pages display. To change the number of pages that appear, make a selection from the Display list and click Go.
Previous and Next. These buttons resemble less than (<) and greater than (>) signs. Click these buttons to move to the previous or next page.
Use the Export page to export the current page and its referenced components. A navigation bar appears directly beneath the breadcrumb trail. Available controls include:
Page. Displays the current page number. To view another page, enter the page number in the Page field and click Go.
View. Controls the current page view. To view alternative reports, make a selection from the list and click Go. See "Using the View List on the Page Definition".
The Groups page displays all pages that are part of the same page group as the current page. Click a page number to edit the page group. Click a page name to view the page definition.
A navigation bar appears directly beneath the breadcrumb trail. Available controls include:
Page. Displays the current page number. To view another page, enter the page number in the Page field and click Go.
Display. Determines how many pages display. To change the number of pages that appear, make a selection from the Display list and click Go.
View. Controls the current page view. To view alternative reports, make a selection from the list and click Go. See "Using the View List on the Page Definition".
The Referenced Components page lists page components and shared components associated with the current page.
A navigation bar appears directly beneath the breadcrumb trail. Available controls include:
Page. Displays the current page number. To view another page, enter the page number in the Page field and click Go.
View. Controls the current page view. To view alternative reports, make a selection from the list and click Go. See "Using the View List on the Page Definition".
Previous and Next. These buttons resemble less than (<) and greater than (>) signs. Click these buttons to move to the previous or next page.
A page is the basic building block of an application. Each page has a page number, a name, and typically some text attributes such as a header, title, and footer. You add content to your page by creating page controls (regions, items, and buttons). Page templates and page region templates control the exact look and feel of each page.
Topics in this section include:
Each Page Definition is divided into three sections: Page Rendering, Page Processing, and Shared Components. Each of these sections is broken into subsections with headings that identify the type of control, component, or application logic.
You can edit all controls, components, or logic within a given subsection by clicking the Edit All icon that displays to the right of the subsection title. The Edit All icon resembles a small grid with a pencil on top of it.
Clicking the Edit All icon displays pages that enable you to edit or delete multiple controls, components, or application logic simultaneously or view a history of recent changes.
For example, selecting the Edit All icon under Regions displays a summary report of all currently defined regions on the current page. You can use this summary view to:
Edit the multiple attributes at once by making selections from the available fields and select lists.
Link to a definition page by clicking the Edit icon.
You can access similar summary views on the next or previous page by clicking the Next and Previous buttons at top of each page. To save your edits to any summary view, click Apply Changes.
You can also view the attributes of a specific control or component by selecting its name on the Page Definition. For example, suppose your Page Definition contains a region named Customers. Clicking the region name Customers would display an attributes page for that region.
You can copy or create controls or components by clicking the Copy and Create icons. The Copy icon resembles two small overlapping pages. Click the Copy icon to make a copy of an existing control or component.
The Create icon resembles a plus (+) sign overlapping a small page. Click the Create icon to create a control or component.
You can quickly change the order in which regions, button, and items display using the Reorder icon on the Page Definition. The Reorder icon displays as a light green downward arrow and upward arrow.
To reorder page components, click the Reorder icon. When the Reorder page appears click the up and down arrows and then click Apply Changes.
Page rendering is the process of generating a page from the database. Use the Page Rendering section to modify controls that impact the rendering of a page, including page attributes, regions, buttons, items, page rendering computations, and page processes.
You can quickly navigate to a specific subsection by clicking the icons beneath the heading. When you select one of these icons, the subsection appears and all other subsections are temporarily hidden. To restore the view, click Show All. The Show All icon resembles an inverted triangle.
Topics in this section include:
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 to name just a few. You access page attributes from the Page Definition.
A region is a area on a page that serves as a container for content. Each page can have any number of regions. The content of a region is determined by the region source. For example, a region may contain a report based on a SQL query you define, or it may contain static HTML.
You control the appearance of a region through a specific region template. You can use regions to group page controls (such as items or buttons). You can also create simple regions that do not generate additional HTML, or create elaborate regions that frame content within HTML tables or images.
|
See Also:
|
As you design your application, you can use buttons to direct users to a specific page or URL, or to enable users to submit a page. When you submit a page, the Application Express engine posts or processes information. A button can be implemented as an HTML button, an image, or by using a template. Buttons can be placed in predefined region template positions or among items in a form.
Items are HTML form elements such as text fields, select lists, and check boxes with an associated session state. Item attributes affect the display and behavior of items on a page. For example, these attributes can impact where a label displays, how large an item will be, and whether the item will display next to, or below the previous item.
There are two categories of items: page items and application items. Page-level items are placed on a page and have associated user interface properties, such as Display As, Label, and Label Template. Application-level items are not associated with a page and therefore have no user interface properties. An application item can be used as a global variable.
Computations are units of logic used to assign session state to items. You can use computations to assign a value to an identified item when a page is submitted or displayed.
Application-level computations assign a value to an item each time a page is rendered. A page-level computation assigns a value to an identified item when a page is displayed or submitted (rendered and processed).
Processes are logic controls used to execute data manipulation language (DML) or PL/SQL. For example, you can use a process to populate session state at the time a page is rendered, to execute some type of logic (for example, using PL/SQL), or to make a call to the rendering engine. Typically a process performs an action. A process may be hand coded PL/SQL, or the invocation of a predefined process.
Page processing is the process of submitting a page. A page is typically submitted when a user clicks a button. Use the Page Processing section of the Page Definition to specify application logic such as computations, validations, processes, and branches. In general, the Application Express engine runs this logic in the order it appears on the Page Definition.
You can quickly navigate to a specific subsection by clicking the icons beneath the heading. When you select one of these icons, the subsection appears and all other subsections are temporarily hidden. To restore the view, click Show All. The Show All icon resembles an inverted triangle.
Topics in this section include:
Computations are units of logic used to assign session state to items and are executed at the time the page is processed.
Validations enable you to create logic controls to verify whether user input is valid. For example, a validation can check whether a value has been entered into a mandatory field.
Processes are logic controls used to execute data manipulation language (DML) or PL/SQL. Processes are executed after the page is submitted.
The Shared Components section of the Page Definition contains common elements that can display or be applied on any page within an application.
You can quickly navigate to a specific subsection by clicking the icons beneath the heading. When you select one of these icons, the subsection appears and all other subsections are temporarily hidden. To restore the view, click Show All. The Show All icon resembles an inverted triangle.
Topics in this section include:
Tabs are an effective way to navigate between pages of an application. Application Builder includes two types of tabs: standard tabs and parent tabs.
An application having only one level of tabs uses a standard tab set. A standard tab set is associated with a specific page. You can use standard tabs to link users to other pages within your application. A parent tab set functions as a container to hold a group of standard tabs. Parent tabs give users another level of navigation and context (or sense of place) within the application.
A list of values (LOV) is a static or dynamic definition used to display a specific type of page item, such as a radio group, check box, or select list. LOVs can be static (that is, based on a set of predefined display and return values) or dynamic (based on SQL queries that select values from tables). Once created, an LOV can then be referenced by one or more page items.
You define LOVs at the application level by running the LOV Wizard and adding them to the List of Values repository.
A breadcrumb is a hierarchical list of links that is rendered using a template. For example, you can display breadcrumbs as a list of links or as a breadcrumb path.
A list is a collection of links that is rendered using a template. For each list entry, you specify display text, a target URL, and other attributes that control when and how the list entry displays. You control the display of the list and the appearance of all list entries by linking the list to a template.
A theme is a named collection of templates that defines the application user interface. Each theme contains templates for every type of application component and page control, including individual pages, regions, reports, lists, labels, menus, buttons, and list of values.
Templates control the look and feel of the pages in your application. As you create your application, you specify templates for pages, regions, reports, lists, labels, menus, buttons, and popup lists of values. Groups of templates are organized into named collections called themes.
You can provide security for your application by specifying an authorization scheme. Authorization is a broad term for controlling access to resources based on user privileges.
Use a navigation bar to link users to various pages within an application. Typically a navigation bar is used to enable users to log in, log out, or link to Help text. The location of a navigation bar depends upon the associated page template. A navigation bar icon enables you to display a link from an image or text. When you create a navigation bar icon you can specify an image name, text, display sequence, and target location (a URL or page).
Use page computations to assign a value to an identified item when a page is submitted or displayed. You can also use application-level computations to assign values to items. Most application-level computations are performed for every page in an application. In contrast, computations created at the page-level only execute when that page is rendered or processed.
Topics in this section include:
A page computation assigns a value to an identified item when a page is displayed or submitted (rendered and processed).You create a page computation by running the Create Page Computation Wizard. For each computation, specify the item for which you are creating the computation and a computation type.
To create a page computation:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
Under Computations, click the Create icon.
For Item Location, select where the computation will execute and click Next. Location options include:
Item on this Page
Item on Another Page
Application Level Item
For Item, select the item and computation point at which you would like to perform the computation:
Compute Item - Select the item the computation will update.
Sequence - Select the order of evaluation.
Computation Point - Select the point at which the computation executes. The computation point On New Instance executes the computation when a new session (or instance) is generated.
Computation Type - Select the method of computation you want to create.
Click Next.
In Computation, enter a computation that corresponds to the selected computation type and click Next.
On Condition, you can choose to make the computation conditional. To make a computation conditional, make a selection from the Condition Type list and enter text in the expression fields.
Click Create.
A good example of using computations can be illustrated by a page containing form fields for entering phone numbers. In this example, the phone number is stored in one database column; however, the data entry form breaks the phone number into three components: area code, prefix, and line number. In this example, the page items are called P10_AREA_CODE, P10_PREFIX, and P10_LINE_NUMBER.
Next, suppose you need to combine the values stored in these items into a single string. You could accomplish this by using an After Submit computation and store the combined values in an item called P10_PHONE_NUMBER.
To create a computation to store the combined values of P10_AREA_CODE, P10_PREFIX, and P10_LINE_NUMBER in new items:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
Create a item named P10_PHONE_NUMBER to store the combined values of P10_AREA_CODE, P10_PREFIX, and P10_LINE_NUMBER. See "Differences Between Page Items and Application Items".
Under Computations, click the Create icon.
For Item Location, select Item on this Page and click Next.
For Computation, select P10_PHONE_NUMBER.
For Sequence, select the order of evaluation.
For Computation, you have the option of creating one of the following computation types:
Static Assignment:
For Computation Type, select Static Assignment and click Next.
Enter the following computation:
(&P10_AREA_CODE.) &P10_PREFIX.-&P10_LINE_NUMBER.
Click Next.
PL/SQL Function Body:
For Computation Type, select PL/SQL Function Body and click Next.
Enter the following computation:
DECLARE
l_return_value VARCHAR2(300) DEFAULT NULL;
BEGIN
l_return_value :=
'('||:P10_AREA_CODE||')'||:P10_PREFIX||'-'||:P10_LINE_NUMBER;
RETURN l_return_value;
END;
Click Next.
SQL Query:
For Computation Type, select SQL Query and click Next.
Enter the following computation:
SELECT '('||:P10_AREA_CODE||')'||:P10_PREFIX||'-'||:P10_LINE_NUMBER FROM DUAL
Click Next.
PLSQL Expression:
For Computation Type, select PLSQL Expression and click Next.
Enter the following computation:
'('||:P10_AREA_CODE||')'||:P10_PREFIX||'-'||:P10_LINE_NUMBER
Click Next.
Click Create.
Once you create a computation, you can edit it on the Edit Page Computation page.
To edit a page computation:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
Under Computations, select the computation name.
The Edit Page Computation page appears.
Edit the appropriate attributes.
Click Apply Changes.
You control when a computation executes under the Computation Point attributes by specifying a sequence and a computation point. The computation point On New Instance executes the computation when a new session (or instance) is generated.
Under Source, enter an expression or query to compute an item's value. In the event a computation fails, you can optionally define an error message in the Computation Error Message field.
You can define a validation declaratively by selecting a validation method. You enter the actual validation edit check in the Validation Messages field. Be aware that if a validation fails, subsequent page processes or computations will not occur. Also remember that the validation you enter must be consistent with the validation type you selected. For more information about validation types, see online Help.
Topics in this section include:
To create a validation:
|
Note: Text entered for validations may not exceed 3,950 characters. |
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
Under Validations in Page Processing, click the Create icon.
Select a validation level:
Item level validations are specific to a single item.
Page level validations do not apply to any single item, but apply to an entire page.
If you selected Item level validation, select the item to be validated and click Next.
Select a validation method as described in Table 5-1.
Table 5-1 Validation Methods
| Validation Method | Descriptions |
|---|---|
|
SQL |
Compares item values to data in the database. For example, you can use a SQL validation to verify whether a last name typed into a field exists in the database. In the following Exists SQL validation, the field is named SELECT 1 FROM customers WHERE last_name = :P1_LAST_NAME |
|
PL/SQL |
Useful if you need complex logic to validate entered data. For example, suppose you need to create a validation for an address form that requires the user to enter a province if the address is not in the United States. You could create the validation as a Function Returning Boolean, using the following PL/SQL:
BEGIN
IF :P1_COUNTRY = 'US' AND :P1_PROVINCE IS NULL THEN
RETURN FALSE;
ELSE
RETURN TRUE;
END IF;
END;
You could also create the same validation implemented as a PL/SQL Expression as follows: NOT (:P1_COUNTRY='US' AND :P1_PROVINCE IS NULL); |
|
Item Level Null |
Checks if an item's value in session state is null. For example, you could validate that the user enters a value in a field by creating an item validation and then selecting the validation method Item Not Null. |
|
Item String Comparison |
Compares the value of an item to a specific string. There are several string comparison validations that compare the value of an item to a literal string. For example, you select the validation type Item in Expression 1 is contained in Expression 2 to validate a user entry in a field against a list of values you provide. In Expression 1, enter the name of the item you want to validate without a colon. For example: P1_VALUE In Expression 2, enter a string of values you want to validate against. For example: ABC/DEF/GHI |
|
Regular Expression |
Regular expressions provide a method to describe text patterns. Use a Regular Expression validation to perform data validation. For example, you could use the following regular expression validation to verify that a string of entered data always consists of groups of six numbers separated by commas and followed by a comma:
^([[:digit:]]{6},)+$
This regular expression would find the following entries valid:
However, the following would not be valid:
|
For SQL, PL/SQL, and Item String Comparison validations, select the type of validation you want to create and click Next.
Specify the sequence and validation name and click Next.
Depending upon the validation method, enter the validation or message text that displays if the validation fails. Click Next.
Define conditions that apply to this validation and click Create.
You can choose to have validation error messages display inline (that is, on the page where the validation is performed) or on a separate error page.
To define how a validation error message displays:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
Under Validations, select the appropriate validation.
The attributes page for the validation appears.
Scroll down to Error Message.
In Error Message, enter your error message text.
From Error message display location, select a display location.
This attribute identifies where a validation error message displays. Validation error messages can display on an error page or inline within the existing page. Inline error messages can display in a notification area (defined as part of the page template) or within the field label.
To create a hard error that stops all processing (including validations), you must display the error on an error page.
If you select Inline with Field or Inline with Field and in Notification, you must associate an item with the error message. To associate an item with the error message, select the item from the Associated Item list.
Click Apply Changes.
|
Tip: If you select Inline with Field or Inline with Field and in Notification, be aware that the Application Express engine does not execute computations or processes during the re-rendering of the page when the validation error messages appear. |
You can control when and if a validation is performed under Conditions.
To create a condition for an existing validation:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
Under Validations, select the appropriate validation.
The attributes page for the validation appears.
Scroll down to Conditions.
To have a validation performed when a user clicks a particular button, make a selection from the When Button Pressed list.
Make a selection from the Condition Type list.
Depending upon the selected Condition Type, enter values in the Expression attributes. The validation will be rendered or processed if the specified condition is met.
Click Apply Changes.
A page process performs an action at a specified point during the rendering or submission of the page. For example, you can create a page process to execute logic or to make a call to the Application Express engine. A page process is a unit of logic that runs when a specific event occurs, such as loading or submitting a page.
From a functional perspective, there is no difference between page-level and application-level processes. The difference between these two process types is where the process is defined, that is at the page-level or at the application level.
Topics in this section include:
You create a process by running the Create Process Wizard. During the wizard, you define a process name, specify a sequence and the point at which the process will execute, and select a process category. You can change nearly all of these attributes on the Edit Page Process page.
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
Under Processes, click the Create icon.
Select a category. Table 5-2 describes available page process categories.
Table 5-2 Process Categories
| Process Category | Description |
|---|---|
|
Data Manipulation |
Data Manipulation process types are frequently used by wizards to support data manipulation language (DML) actions. Application Builder supports the following declarative data manipulation processes:
|
|
Close Popup Window |
Applies to processes running within a popup window. Upon execution, this process type closes the current popup window. |
|
Form Pagination |
Implements pagination through the detail records associated with a master detail form. Most often used in master detail forms (such as in the Master Detail Wizard), this process checks the master table to determine which set of detail records you are in and determines what the next detail record should be. See Also: "Creating a Master Detail Form" |
|
On Demand |
Creates an application-level process that can only be executed when called from a specific page. When you create this process type at the page-level, you are creating reference to an existing application-level process. See Also: "About On Demand Application Processes" |
|
PL/SQL |
Runs the PL/SQL you provide. Use this process type to execute a block of PL/SQL entered directly into the process or to simply call an existing API. |
|
Reset Pagination |
In Report regions, resets pagination back to the first result set. The Application Express engine keeps track of where the user is within a given result set. This process category returns the user to the beginning result set. In other words, this category resets the counters associated with the report region to return the first part of the result set the next time the result set displays. |
|
Session State |
Sets the values of existing session state items to null. Select this process type to clear the cache for applications, sessions, or items and to clear existing user preferences. See Also: "Managing Session State Values" and "Managing User Preferences" in Oracle Application Express Administration Guide |
|
Web Services |
Implements a Web Service as a process on a page. Running the process submits a request to the service provider. See Also: "Invoking a Web Service as a Process" |
Follow the on-screen instructions.
Once you create a process, you can control when the process executes and what the process does by editing attributes on the Edit Page Process page.
To edit an existing page process:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
Select the process name.
The Edit Page Process page appears.
You control when a process executes by specifying a sequence number and a process point under Process Point. You can prevent a process from running during subsequent visits to a page by selecting one of the following options under Run Process:
Once for each page visit
Once for each session or when reset
Enter the appropriate code for PL/SQL process types. For PL/SQL anonymous block processes, enter the appropriate code under Process. For Clear Cache processes, enter the appropriate code under Source. In the event a process fails, you can optionally define an error message in the Process Error Message field.
You can make a process conditional by selecting a condition type and entering an expression under Conditional Processing.
Additionally, you can also make a selection from the When Button Pressed attribute. When you select a button from this list, the process only executes if a user clicks the selected button.
A branch is an instruction to go to a specific page, procedure, or URL. For example, you can branch from page 1 to page 2 after page 1 is submitted.
You create a branch by running the Create Page Branch Wizard and specifying Branch Point and Branch Type. The Branch Type defines the type of branch you are creating. For more information about Branch Types, see online Help.
Topics in this section include:
When you click a standard tab in an application, the Application Express engine sets session state, executes computations, and then links you to the target page. It does not run any processes or explicitly defined branches. In cases where the page is submitted without clicking a tab, the Application Express engine explicitly defines branches to direct users to a subsequent page.
You can control when a branch executes by making a selection from the Branch Point list. Available options include:
On Submit: Before Computation - Branching occurs before computations, validations, or processing. Use this option for buttons that do not need to invoke any processing (for example, a Cancel button).
On Submit: Before Validation - Branching occurs after computations, but before validations or processing. If a validation fails, page processing stops, a rollback is issued, and the page displays the error. Because of this default behavior, you do not need to create branches to accommodate validations. However, you may want to branch based on the result of a computation (for example, to a previous branch point).
On Submit: Before Processing - Branching occurs after computations and validations, but before processing. Use this option to branch based on a validated session state, but before performing any page processing.
On Submit: After Processing - Branching occurs after computations, validations, and processing. This option branches to a URL or page after performing computations, validations, and processing. When using this option, remember to sequence your branches if you have multiple branches for a given branch point.
On Load: Before Header - Branching occurs before a page is rendered. This option displays another page instead of the current page or redirects the user to another URL or procedure.
Depending upon the Branch Type you select, you can specify the following additional information in the Action attributes:
The page number of the page to which you want to branch
PL/SQL procedure which ultimately renders a branch target page
A URL address
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.
Topics in this section include:
To edit page attributes:
Navigate to the Page Definition. See "Accessing a Page Definition".
Under Page Rendering, locate the Page section.
The Page Attributes page is divided into categories that control specific page attributes such as the Page Name, Title, HTML Header, HTML Body, Help Text, Templates, and so on.
To edit page attributes you can either:
Click the Edit page attributes icon to access the entire Page Attributes page. This icon resembles a small page with a pencil on top of it.
Click a specific link. The specific information appears.
|
Tip: Clicking the Edit page attributes icon is the only way to view all page attributes at once. |
The Page Attributes page appears. Required values are marked with a red asterisk (*).
The Page Attribute page is divided into the following sections: Name, Display Attributes, Header and Footer, HTML Header, HTML Body Attributes, Security, Duplicate, Cache, Configuration, Error, Help, and Comments.
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.
Use these attributes to define general attributes for the current page such as a page name, an optional alphanumeric alias, and associated page groups. Table 5-3 describes these attributes.
Table 5-3 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" |
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. Table 5-4 describes these attributes.
Table 5-4 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 | |
|
Specify the cursor focus. Available options include: | |
|
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 |
Use these attributes to define page header, body header, body footer, and page footer text. Table 5-5 describes these attributes.
Use HTML Header to replace the #HEAD# substitution string in the page template header. The values entered here are inserted after the HTML <HEAD> tag. Common uses of these attributes:
Code page-specific inline cascading style classes
Add additional style sheets for a specific page
Code page-specific meta tag page refresh
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.
Use this attribute to add events when the page is being loaded, such as calls to JavaScript. In the Page HTML Body attribute, enter JavaScript or text to be substituted for your page template's #ONLOAD# substitution string. To use this feature, your page template must include the #ONLOAD# substitution string.
You can use the Page HTML Body attribute to write into the contents of the opening <body> tag. A typical page template might use #ONLOAD# within the opening <body> tag as shown in the following example:
<html> <head> ... </head> <body #ONLOAD# >
Use these attributes to specify an authorization scheme and authentication requirements for the current page. Table 5-6 describes these attributes.
Table 5-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" | |
|
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" |
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.]
Use these attributes to enable caching for the current page. Enabling page caching can improve application's performance and works well for static pages. Table 5-7 describes these attributes.
Table 5-7 Cache Attributes
| Attribute | Description |
|---|---|
|
Specify whether to enable page caching by selecting Yes or No. Page caching can improve performance because the page displays from 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 be cached. If the condition returns true, the page is displayed from cache. | |
|
Enter values in this attribute based on the specific condition type selected. | |
|
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" |
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.
Use this attribute to specify the error text that displays in the #NOTIFICATION_MESSAGE# template substitution string in the event an error occurs on the page.
Use this attribute to enter Help text for the current page.
Help text is displayed using a help system that you must develop. To show the Help for a specific page, call the APEX_APPLICATION.HELP procedure from a page that you create for displaying Help text. For example, you could use a navigation bar icon similar to:
f?p=4000:4600:&APP_SESSION.::&DEBUG::LAST_STEP:&APP_PAGE_ID.
Page-level help supports shortcuts using the following syntax:
"SHORTCUT_NAME"
The Application Express engine dynamically renders and processes pages based on data stored in database tables. To view a rendered version of your application, you run or submit it to the Application Express engine by clicking the Run icon.
When you run an application from within the development environment, the Developer toolbar appears at the bottom of the page. The Developer toolbar offers a quick way to edit the current page, create a page, region, or page control, view session state, or toggle in and out of Debug mode. You can control whether the Developer toolbar displays by changing the Status attribute on the Edit Definition page.
The Developer toolbar consists of the following links:
Home links you to the Workspace home page. See "About the Workspace Home Page".
Application links you to the Application home page. See "Application Builder Concepts".
Edit Page accesses the Page Definition for the current running page. See "About the Page Definition".
Create links to a wizard for creating a page, region, page control (item, button, branch, computation, process, or validation), or a shared control (navigation bar icon, tab, list of values, list, or breadcrumb). See "Building an Application".
Session links you to session state information for the current page. See "Viewing Session State".
Activity links you to the Activity reports page. See "Activity Reports".
Debug toggles the page between Debug and No Debug mode. See "Accessing Debug Mode".
Show Edit Links toggles between Show Edit Links and Hide Edit Links. Clicking Show Edit Links displays a small orange icon next to each editable object on the page. Each icon is orange and contains a triangle with two rules beneath it. Clicking the link displays another window in which to edit the object.
Shared components are common elements that can display or be applied on any page within an application. You can use the tools and wizards on the Shared Components page either at the application-level or on specific pages.
Topics in this section include:
To access the Shared Components page:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
On the Application home page, click Shared Components.
The Shared Components page appears.
To create a shared component, select the appropriate link.
You can also access the Shared Components page by clicking the Shared Components icon on the Action bar. The Action bar resembles a small mechanical gear and displays beneath the Utilities tab in the upper right corner of most pages in Application Builder.
The following sections describe each link on the Shared Components page.
The following section describes the links under Application.
Links to the Edit Application Definition page. Use this page to edit attributes that determine the application name, application availability, and static substitution strings. You can also use this page to define other attributes such as build options or an application logo and view associated templates and component defaults. See "Configuring the Application Definition".
Use Application Comments to enter comments specific to the currently selected application. See "Adding Application Comments"
The following section describes the links under Logic.
Application-level items do not display, but are used as global variables to the application. Commonly, you set the value of a page-level item using an application or page computations. See "Understanding Application-Level Items".
Use application processes to run PL/SQL logic:
At specific points for each page in an application
As defined by the conditions under which the process is set to execute
Upon the creation of a new session
Note that On Demand processes execute only when called from a page-level On Demand process. See "Understanding Application Processes".
Use application-level computations to assign values to application and page-level items for each page displayed or upon the creation of a new application session. You can also create an application-level computation and execute it conditionally on multiple pages. See "Understanding Application Computations".
Web service references in Application Builder are based on the Simple Object Access Protocol (SOAP). You can create a reference to a Web service and then incorporate it into an application to process data submitted by a form, or to render output in the form or report. See "Implementing Web Services".
Use build options to conditionally display or process specific functionality within an application. You can use build options to control which features of an application are turned on for each application deployment. See "Using Build Options to Control Configuration".
The following section describes the links under Security.
Authentication is the process of establishing each user's identity before they can access your application. Authentication may require a user to enter a user name and password or may involve verification of a user's identity or use of a secure key. See "Establishing User Identity Through Authentication".
Authorization restricts user access to specific controls or components based on predefined user privileges. See "Providing Security Through Authorization".
Session State Protection is a built-in functionality that prevents hackers from tampering with the URLs within your application. URL tampering can adversely affect program logic, session state contents, and information privacy. See "Understanding Session State Protection".
Use the Edit Security Attributes page to configure general security attributes for all pages within an application. See "Configuring Security Attributes".
The following section describes the links under Globalization.
You can develop applications in Oracle Application Express that can run concurrently in different languages. A single Oracle database and Oracle Application Express instance can support an application in multiple languages. Translating an application involves multiple steps. See "About Translating an Application and Globalization Support" and "Understanding the Translation Process".
Text messages are named text strings that can be called from the PL/SQL code you write. This PL/SQL can be anonymous blocks within page processes and page regions, or in packages and procedures. See "Translating Messages".
You can develop applications that can run concurrently in different languages. Click this link to specify globalization options such as the Application Primary Language and Application Language Derived From attributes. See "Configuring Globalization Attributes" and "About Translatingqd an Application and Globalization Support".
The following section describes the links under Navigation.
Tabs are an effective way to navigate users between pages in an application. You can create two types of tabs: standard tabs or parent tabs. A standard tab set is associated with a specific page and page number. A parent tab set functions as a container to hold a group of standard tabs. See "Creating Tabs".
A list is a shared collection of links. You control the appearance of a list through list templates. Each list element has a display condition that enables you to control when it displays. See "Creating Lists".
Breadcrumbs provide users with hierarchical navigation. A breadcrumb is a hierarchical list of links that display using templates. You can display a breadcrumb as a list of links or as a breadcrumb path. See "Creating Breadcrumbs".
A tree is an effective way to communicate hierarchical or multiple level data. See "Creating Trees".
Navigation bar entries offer users a simple navigation path for moving between pages in an application. The location of a navigation bar depends upon the associated page template. Navigation bar entries can display as a link from an image or text. A navigation bar entry can be an image, an image with text beneath it, or text. See "Creating a Navigation Bar Entry".
The following section describes the links under User Interface.
A theme is a named collection of templates that defines the application user interface. See "Managing Themes".
Templates control the look and feel of specific constructs within your application, such as pages, regions, items, and menus. See "Customizing Templates".
User interface defaults enable you to assign default user interface properties to a table, column, or view within a specified schema. When you create a form or report using a wizard, the wizard uses this information to create default values for region and item properties.
Because user interface defaults are associated with a table, you can use them with applications created using the form and report wizards. See "Managing User Interface Defaults".
A list of values (LOV) is a static or dynamic set of values used to display a popup list of values, select list, check box, or radio group. See "Creating Lists of Values".
Use shortcuts to avoid repetitive coding of HTML or PL/SQL functions. You can create a shortcut to define a page control such as a button, HTML text, a PL/SQL procedure, or HTML. Once you define a shortcut, it is stored in a central repository so you can reference it from various locations within your application. See "Using Shortcuts".
The following section describes the links under Reports.
Use the Report Queries link to view a report of stored queries within the current application. See "About Report Queries".
Use Report Layouts with a report or shared query to render data in a printer-friendly format, such as Adobe Portable Document Format (PDF), Microsoft Word Rich Text Format (RTF), or Microsoft Excel (XLS) format. See "About Report Layouts".
The following section describes the links under Files.
Application Builder includes themes that contain templates that reference their own cascading style sheets (CSS). Use the Cascading Style Sheets link to upload cascading style sheets to your workspace. See "Using Custom Cascading Style Sheets".
Use the Static Files link to upload static files to your workspace. See "Managing Static Files".
You can export shared components and page components on the Component Export page. You can also use this wizard to back up a component before editing it or to create an export that functions as a patch to another Oracle Application Express instance.
Topics in this section include:
To export shared components from the Shared Components page:
Navigate to the Export page:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Export/Import.
On the Export/Import page, click Export and click Next.
On the Tasks list, click Component Export.
The Component Export page appears. See "Exporting Application Components".
To export shared components from the Shared Components page:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
On the Application home page, click Shared Components.
The Shared Components page appears.
On the Tasks list, click Export Application Components.
The Component Export page appears. See "Exporting Application Components".
To access the Shared Components reports:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
On the Tasks list, click Application Reports.
The Application Reports page appears.
Click Shared Components.
A variety of application reports appear and are divided into the same categories that appear on the Shared Components page, including:
Application
Logic
Security
Globalization
Navigation
User Interface
Reports
Files
Note that you can also navigate to these reports by clicking View Application Reports on the Tasks list on the Application home page.
Application processes are blocks of PL/SQL logic that are set to run at specific points using processes from multiple pages of an application. By default, application processes execute at the same point for every page in the application. However, you can apply conditions for specific pages to control when the process executes.
Topics in this section include:
A special type of application process is the On Demand process. An On Demand application process has a Process Point of On Demand and executes when called from a page-level On Demand process. On Demand processes are useful when you have PL/SQL logic that you would like to run from different execution points across multiple pages.
You can have a page request run an On Demand process by using the following syntax:
f?p=application_id:page_id:session:APPLICATION_PROCESS=process_id
Where:
application_id is the application ID or alphanumeric alias
page_id is the page number or alphanumeric alias
session is the session ID
APPLICATION_PROCESS=process_id is the keyword APPLICATION_PROCESS= followed by either the process ID or an alphanumeric name of an application-level process having a Process Point of On Demand
When you use this syntax, the Application Express engine recognizes the request and processes it using the following rules:
The page number in the URL can be any page number or alias. A page number or alias is required in the request only as a syntactic placeholder because no specific page is accessed for this type of request.
The process authorization scheme, the application's authorization scheme, and the process conditions are supported.
Session state (that is, item names and values) may be set in the URL, but clear cache options are ignored.
Any failures of authentication, authorization, or process conditions do not result in visible error messages or other indicators of such failures and most often result in a blank page being displayed.
Specifying the process by name locates the first process with the specified (case-preserved) name.
A shopping cart application is a good example of when you might use an application process. For example, suppose you need to display the contents of a user's shopping cart with each page view. To accomplish this, you create a region on page zero of your application that displays the values of the application-level items TOTAL_CART_ITEMS and TOTAL_PURCHASE_PRICE.
Instead of writing a process for each page to set the values of TOTAL_CART_ITEMS and TOTAL_PURCHASE_PRICE, you could write an application process of type On Load: Before Header to compute these values. Then, the Application Express engine would execute the process on each page as it renders the application. As a result, each page, would display the most current values for TOTAL_CART_ITEMS and TOTAL_PURCHASE_PRICE.
To create an application process:
Navigate to the Shared Components page:
On the Workspace home page, click Application Builder.
Select an application.
On the Application home page, click Shared Components.
The Shared Components page appears.
Under Logic, select Application Processes.
Click Create.
For Identification:
Name - Enter a name for the application process.
Sequence - Specify the sequence number for this process. The sequence number determines the order in which the process will be evaluated relative to other processes.
Point - Identify the point at which this process executes.
Click Next.
For Source:
Process Text - Enter the text that is to be the source of your process.
Error Message - Enter the error message that displays if the process raises an error.
Click Next.
For Conditionality:
Condition Type - Select a condition type that must be met in order for this process to execute.
Expression 1 and Expression 2 - Use these attributes to conditionally control whether the process executes. Enter values in this attribute based on the specific condition type you select. The process will execute if the specified condition is met.
Click Create Process.
Once you create an application process, it appears on the Application Processes page. You control how the page displays by making a selection from the View list. Available options include:
Icons (the default) displays each process as a large icon. To edit a process, click the appropriate icon.
Details displays each application process as a line in a report. To edit a process, click the name.
After you create an application process, you can access the Utilization and History reports.
To access application processes reports:
Navigate to the Workspace home page.
Click Application Builder.
Select an application.
On the Application home page, click Shared Components.
Under Logic, select Application Processes.
Select one of the following tabs at the top of the page:
Utilization
History
Follow the on-screen instructions.
Click Utilization to display the Application Process Utilization page. This page displays application processes used in the current application.
Application Computations are units of logic that set the value of a single page or application-level item and are run at the same point across multiple pages in an application. Like page-level computation, application computations can be based on static values, item values, PL/SQL, or SQL.
Topics in this section include:
A common use of an application item is to store the value of the last page viewed in the application. By storing the value in an item, you can add a back button and then redirect the user to the page number captured by the computation. This type of computation works well, for example, when you need to enable users to back out of an error page.
The following is an example of a computation that stores the last page visited. In this example, the computation:
Stores the last application page visited to an item named LAST_PAGE
Checks that the value of a CURRENT_PAGE_ITEM is of type PL/SQL Function Body with a Computation body of:
BEGIN :LAST_PAGE := nvl(:CURRENT_PAGE,:APP_PAGE_ID); :CURRENT_PAGE := :APP_PAGE_ID; RETURN :LAST_PAGE; END;
Typically an application computation runs at the same point across multiple pages in an application. The exception is computations having a Computation Point of On New Instance. This type of computation only runs when a user first accesses your application. This type of computation is useful when you need to only retrieve information once within a user's session (for example, to retrieve a user's job title).
To create an application computation:
Navigate to the Shared Components page:
On the Workspace home page, click Application Builder.
Select an application.
On the Application home page, click Shared Components.
The Shared Components page appears.
Under Logic, select Application Computations.
Click Create.
Under Item:
Sequence - Specify the sequence for this component. The sequence determines the order of evaluation.
Computation Item - Select the item this computation affects.
For Computation Point, select a process point at which this computation should be performed. Selecting After Submit causes the computation to be performed only after the page is displayed and then submitted.
Under Computation:
Computation Type - Select the manner in which this computation will be performed.
Computation - Enter the computation logic that corresponds to the computation type.
Computation Error Message - Enter the error message that displays if the computation fails.
For Authorization Scheme (optional), select an authorization scheme which must evaluate to True in order for this computation to execute.
Under Conditions:
Condition Type - Select a condition type that must be met in order for this computation to execute.
Expression 1 and Expression 2 - Use these attributes to conditionally control whether the computation executes. Enter values in this attribute based on the specific condition type you select. The computation will execute if the specified condition is met.
For Build Option (optional), select a build option for this component. See "Using Build Options to Control Configuration".
Click Create.
Once you create an application computation, it appears on the Application Computations page. You control how the page displays by making a selection from the View list. Available options include:
Icons (the default) displays each computation as a large icon. To edit an computation, click the appropriate icon.
Details displays each application process as a line in a report. To edit a computation process, click the name.
Once you create an application computation, you can view the Application Computation History report.
To access the Application Computation History report:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
When Application Builder appears, click Shared Components.
Under Logic, select Application Computations.
Select the History tab at the top of the page.
This Application Computation History report displays a history of recently changed application computations by date.
Application Builder User's Guide
Release 3.2
E11947-02
April 2012
Oracle Application Express Application Builder User's Guide, Release 3.2
E11947-02
Copyright © 2003, 2012, Oracle and/or its affiliates. All rights reserved.
Primary Author: Terri Jennings
Contributors: Marco Adelfio, Carl Backstrom, Christina Cho, Michael Hichwa, Christopher Jones, Joel Kallman, Sharon Kennedy, Syme Kutz, Sergio Leunissen, Anne Romano, Kris Rice, Marc Sewtz, Scott Spadafore, Scott Spendolini, Jason Straub, Simon Watt, and Steve Fogel
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
This section offers a quick introduction to using Oracle Application Express. It is assumed you have completed the installation process.
This section contains the following topics:
Oracle Application Express is a hosted declarative development environment for developing and deploying database-centric Web applications. Thanks to built-in features such as user interface themes, navigational controls, form handlers, and flexible reports, Oracle Application Express accelerates the application development process.
The Application Express engine renders applications in real time from data stored in database tables. When you create or extend an application, Oracle Application Express creates or modifies metadata stored in database tables. When the application is run, the Application Express engine then reads the metadata and displays the application.
To provide stateful behavior within an application, Oracle Application Express transparently manages session state in the database. Application developers can get and set session state using simple substitutions and standard SQL bind variable syntax.
The sections that follow describe key features of Oracle Application Express.
Reporting
With Oracle Application Express, you can quickly generate HTML reports that display the results of SQL queries. You can also download and print reports in HTML, an Adobe Portable Document Format (PDF), Microsoft Word Rich Text Format (RTF), or Microsoft Excel format (XLS), or XML.
You can declaratively link reports together to provide drill-down reporting and use bind variables to pass information from session state to a report. Reports support declarative column heading sorting, control breaks, sums, and pagination. Report sorting and pagination can use Partial Page Refresh (PPR) technology to avoid refreshing the entire page. You can also add declarative links to a report to download the report data to CSV or XML formats. Plus, you can customize the report appearance using templates. See "About Bind Variable Syntax" and "Creating Reports".
Interactive Reporting Regions enable end users to customize reports. Users can alter the layout of report data by choosing the columns they are interested in, applying filters, highlighting, and sorting. They can also define breaks, aggregations, different charts, and their own computations. Users can create multiple variations of the report and save them as named reports, output to comma-delimited files, and print them to PDF documents. See "Editing Interactive Reports".
Forms
Using wizards, you can easily create forms on tables or on a stored procedure. For example, when creating a form on a table, these wizards provide automatic management of insert, update, and delete as well as lost update detection. Once you create a form, you can rearrange form fields (called form items) using a visual representation, enabling you to quickly achieve the layout you want. Form items offer a variety of display options including text fields, text areas, radio groups, select lists, check boxes, date pickers, and popup list of values. See "Creating Forms".
Charting
You can also use wizards to create HTML, SVG, or Flash charts. You can create charts that enable users to drill down from one chart to another chart or report. Charts can also be refreshed using Partial Page Refresh (PPR) technology, avoiding the need to refresh an entire page. You can also configure a chart to refresh at defined intervals. Additionally, you can take advantage of report column templates to add simple HTML bar charts to any report. See "Creating Charts".
Spreadsheet Upload
Use the Create Application from Spreadsheet Wizard to quickly upload spreadsheet data directly into the database. You can choose to store the data in a new database table or add it to an existing database table. Once the data is uploaded, you can quickly create an application. This handy wizard enables you to go from spreadsheet to a shared application in just a few clicks. See "About the Create Application from Spreadsheet Wizard".
Session State Management
Oracle Application Express transparently manages session state (or application context) in the database. Forms automatically save session state, remembering your application context over your session. Referencing session state within SQL and PL/SQL is as simple as using bind variables. For example, consider the following SELECT statement:
SELECT * FROM EMP WHERE EMPNO = :P1_ID
In this example, the value in the item P1_ID is automatically bound when the query is run. You can also reference session state within a static context by prefixing the item name with an ampersand (&) and suffixing it with a period(.), for example:
&P1_NAME.
For management of two dimensional data sets, Oracle Application Express provides a robust collections infrastructure. Best of all, session management is stateless and does not consume any memory. See "Managing Session State Values" and "About Bind Variable Syntax".
User Interface Themes
Oracle Application Express separates presentation (or user interface themes) from the application logic. You can design your application in one theme, change to another supplied theme, or create and use your own custom theme. By separating the application logic (such as queries, processes, and branches) from the HTML rendering, your application can take advantage of new designs and other technological advances without an application rewrite. See "Managing Themes".
Flow Control and Navigation
Every Web application needs navigation and dynamic applications need flow control. Oracle Application Express provides built-in components to simplify the development and maintenance of navigational controls. Navigation is controlled using declarative tabs (one or two levels), breadcrumbs, tree controls, and lists of links. Flow control is performed using declarative branches which can take effect at specific events and under certain conditions. The appearance of navigation controls are managed through templates, making it easy to change from one look to another. See "Adding Navigation" and "Controlling Navigation Using Branches".
Conditionality on All Components
When creating dynamic Web applications, many application components and processing are conditional. In other words, you only show or process certain pieces of information based on the application context, the data, an event, or a privilege. Oracle Application Express enables you to declaratively specify conditionality of all components. This gives you exact control over what users see or do not see on a tab, button, item, list entry, and so. See "Understanding Conditional Rendering and Processing".
External Interfaces and Extensibility
Even though Oracle Application Express provides a robust declarative environment for building applications, you also have the option of developing custom interfaces or controls. For example, if a component does not meet the needs of your environment, you can generate your own custom HTML using PL/SQL. See "Rendering HTML Using Custom PL/SQL". You can also call external services using Web services. See "Implementing Web Services". Oracle Application Express also includes APIs to easily integrate email alerts into an application. See "Sending Email from an Application". Plus, because Oracle Application Express resides in the Oracle database, you can take advantage of inherent database capabilities, including external tables, PL/SQL, database links, gateways, and database Java to extend the functionality of your application.
Security
With Oracle Application Express, you can create public applications that do not require a user log in, or you can create secure applications that require authentication. Oracle Application Express provides a number of built-in authentication schemes including Single Sign On, Database Account Credentials, and an easy-to-use user management system. You can also use custom schemes that interface with just about any authentication service including Microsoft Active Directory and Oracle Applications.
Additionally, you can customize authorization to meet the needs of your environment and apply authorization selectively to an entire application, a page, or a page component. Finally, you can also take advantage of an innovative session state protection feature to prevent URL tampering and built-in features to protect an application form SQL Injection and cross-site scripting (XSS) attacks. See "Managing Application Security".
SQL Workshop Tools
SQL Workshop provides tools to enable you to view and manage database objects from a Web browser. Use SQL Commands to run SQL and PL/SQL statements. See "Using SQL Commands" in Oracle Application Express SQL Workshop and Utilities Guide.
Query Builder enables you to define queries by dragging and dropping tables and easily create relationships between objects. See "Building Queries with Query Builder" in Oracle Application Express SQL Workshop and Utilities Guide.
Object Browser provides an easy-to-use graphical user interface for viewing, creating, modifying, browsing, and dropping database objects. See "Managing Database Objects with Object Browser" in Oracle Application Express SQL Workshop and Utilities Guide.
Finally, you can use SQL Scripts to create, edit, view, run, and delete script files. See "Using SQL Scripts" in Oracle Application Express SQL Workshop and Utilities Guide.
Supporting Objects Utility
You can simplify the steps needed to export, install, upgrade, and deinstall an application in another Oracle Application Express instance by creating a packaged application. Using the Supporting Objects utility, you can bundle the application definition with scripts for creating the database objects, seed data, images, cascading style sheets, and JavaScript.
Creating a packaged application provides application users with an installer-like experience and automates the process of importing and installing an application in another development, test, or even production instance. See "How to Create a Packaged Application".
Performance
Oracle Application Express provides application developers and application users with an extremely high level of performance. Because Oracle Application Express resides in the Oracle database, it has minimal impact on network traffic. Plus, Application Builder includes a large number of monitoring reports to enable you to identify and tune application performance. See "Debugging an Application".
Hosted Development
Oracle Application Express enables a single database to host large numbers of users. Users work in a dedicated work area called a workspace. A workspace is a virtual private database that enables multiple users to work within the same Oracle Application Express installation while keeping their objects, data and applications private. This flexible architecture enables a single database instance to manage thousands of applications.
You determine how the process of provisioning (or creating) a workspace works. For example, in email verification provision mode, users request a workspace using a link on the login page. After the workspace request has been granted, users receive an email containing a link that they must click to verify the validity of their email address. Then they receive an email with their login credentials. To see an example of email verification provision mode, go to:
http://apex.oracle.com
See "Configuring Your Oracle Application Express Environment" and "Oracle Application Express Hosted Instance Administration" in Oracle Application Express Administration Guide.
Oracle Application Express installs with your Oracle database and is comprised of data in tables and PL/SQL code.
Whether you are running the Oracle Application Express development environment or an application you built using Oracle Application Express, the process is the same. Your browser sends a URL request that is translated into the appropriate Oracle Application Express PL/SQL call. After the database processes the PL/SQL, the results are relayed back to your browser as HTML. This cycle happens each time you either request or submit a page.
The application session state is managed in the database tables within Application Express. It does not use a dedicated database connection. Instead, each request is made through a new database session, consuming minimal CPU resources.
About Oracle HTTP Server (Apache) and the Embedded PL/SQL Gateway
The version of Oracle Database you use determines how the URL is translated:
Versions prior to Oracle Database 11.1 require Oracle HTTP Server (Apache) with mod_plsql. The following graphic illustrates the three-tier architecture.
With Oracle Database 11.1 or later or Oracle Database 10g Express Edition, you can remove Oracle HTTP Server and mod_plsql from the architecture and replace it with the embedded PL/SQL gateway. The following graphic illustrates the two-tier architecture using the embedded PL/SQL gateway.
The embedded PL/SQL gateway provides the Oracle database with a Web server and also the necessary infrastructure to create dynamic applications. The embedded PL/SQL gateway runs in the XML DB HTTP server in the Oracle database and includes the core features of mod_plsql, but does not require the Oracle HTTP Server powered by Apache. Inclusion of the embedded PL/SQL gateway simplifies the architecture and eliminates the middle tier entirely.
About the Application Express Engine
The Application Express engine renders and processes pages. It also performs these tasks:
session state management
authentication services
authorization services
page flow control
validations processing
Different Oracle Application Express Environments
When you install Oracle Application Express, you can install two different environments:
To access the Oracle Application Express development environment, users log in to a shared work area called a workspace. Users are divided into four primary roles:
Developers are users who create and edit applications
Workspace administrators are users who perform administrator tasks specific to a workspace such as managing user accounts, monitoring workspace activity, and viewing log files
End users have no development privileges and are defined to provide access to applications that do not use an external authentication scheme.
Oracle Application Express administrators are superusers that manage an entire hosted instance using the Application Express Administration Services application
When you log in to Oracle Application Express you log in to a workspace. A workspace is an area within the Oracle Application Express development environment where developers can create applications.
How you log in to Oracle Application Express depends upon whether you have configured your development environment:
If you have recently installed Oracle Application Express, you must configure your development environment
If you are a developer logging into a previously configured development environment, an administrator must grant you access to a workspace
Topics in this section include:
You open the Oracle Application Express home page in a Web browser. To view or develop Oracle Application Express applications, the Web browser must support Java Script and the HTML 4.0 and CSS 1.0 standards. Ensure also that cookies are enabled. The following browsers meet this requirement:
Microsoft Internet Explorer 6.0 or later
Mozilla Firefox 1.0 or later
How you set up Oracle Application Express depends upon your user role. If you are a developer accessing a hosted development environment, an administrator must grant you access to a workspace. If you are an Oracle Application Express administrator, you must perform the following steps:
Log in to Oracle Application Express Administration Services. Oracle Application Express Administration Services is a separate application for managing an entire Oracle Application Express instance. You log in using the ADMIN account and password created or reset during the installation process.
In a Web browser, navigate to the Oracle Application Express Administration Services application. By default, Oracle Application Express Administration Services installs to the following location:
If your setup uses the embedded PL/SQL gateway, go to:
http://hostname:port/apex/apex_admin
Where:
hostname is the name of the system where Oracle XML DB HTTP Server is installed.
port is the port number assigned to Oracle XML DB HTTP Server. In a default installation, this number is 8080. See "Verifying the Oracle XML DB HTTP Server Port" in Oracle Application Express Application Builder User's Guide.
apex is the database access descriptor (DAD) defined in the configuration file.
If your setup uses Apache and mod_plsql, go to:
http://hostname:port/pls/apex/apex_admin
Where:
hostname is the name of the system where Oracle HTTP Server is installed.
port is the port number assigned to Oracle HTTP Server. In a default installation, this number is 7777.
pls is the indicator to use the mod_plsql cartridge.
apex is the database access descriptor (DAD) defined in the mod_plsql configuration file.
On the Login page:
In Username, enter admin.
In Password, enter the Oracle Application Express administrator account password you specified when you installed Oracle Application Express.
Click Login.
|
See Also: See "Logging in to Oracle Application Express Administration Services" in Oracle Application Express Administration Guide. |
Specify a provisioning mode. In Oracle Application Express Administration Services you must determine how the process of creating (or provisioning) a workspace will work. See "About Workspace Provisioning" in Oracle Application Express Administration Guide.
Create a Workspace. A workspace is a virtual private database allowing multiple users to work within the same Oracle Application Express installation while keeping their objects, data and applications private. Each workspace has a unique ID and name. An Oracle Application Express administrator can create a workspace manually or have users submit requests. See "Creating Workspaces" and "Managing Workspace Requests" in Oracle Application Express Administration Guide.
Log in to a Workspace. Once you create a workspace in Oracle Application Express Administration Services, return to the Oracle Application Express Login page and log in to that workspace. See "Logging In to Oracle Application Express as a Developer".
When you log in to Oracle Application Express, you log in to a workspace. If you are a developer, an administrator must grant you access to a workspace.
|
Note: Before users can request a workspace or change their passwords, an Oracle Application Express administrator must configure Oracle Application Express environment preferences. |
Topics in this section include:
|
Note: This section applies only if your Oracle Application Express administrator has configured Oracle Application Express to support workspace requests. |
Before you can log in to Oracle Application Express, an administrator must grant you access to a workspace. Each workspace has a unique ID and name.
To request a workspace:
In a Web browser, navigate to the Oracle Application Express Login page.
If you do not know the URL for logging in to Application Express, see "Logging in to a Workspace".
The Login page appears.
Under Tasks, click Request a Workspace.
The Request Service Wizard appears.
Click Next and follow the on-screen instructions.
After an Oracle Application Express administrator approves a workspace request, an e-mail arrives with your login credentials (the workspace name, user name, and password).
Note that if your administrator selected Email Verification as the automated method for handling new workspace requests, you might first receive an email containing a verification link. This step ensures that your email is a valid one before the workspace request is approved.
To log in to Oracle Application Express:
In a Web browser, navigate to the Oracle Application Express Login page. By default, Oracle Application Express installs to the following location:
If your setup uses the embedded PL/SQL gateway, go to:
http://hostname:port/apex
Where:
hostname is the name of the system where Oracle XML DB HTTP Server is installed.
port is the port number assigned to Oracle XML DB HTTP Server. In a default installation, this number is 8080. See "Verifying the Oracle XML DB HTTP Server Port".
apex is the database access descriptor (DAD) defined in the configuration file.
For users who have upgraded from earlier releases, or who have a custom configuration, this value may be htmldb or something else. Verify your DAD with your Oracle Application Express administrator.
If your setup uses Oracle HTTP Server (Apache) and mod_plsql, go to:
http://hostname:port/pls/apex
Where:
hostname is the name of the system where Oracle HTTP Server is installed.
port is the port number assigned to Oracle HTTP Server. In a default installation, this number is 7777. You can find information about your Oracle HTTP Server installation's port number from either of the following files:
ORACLE_BASE\ORACLE_HOME\install\portlist.ini ORACLE_BASE\ORACLE_HTTPSERVER_HOME\Apache\Apache\conf\httpd.conf
Be aware that if you change a port number, it is not updated in the portlist.ini file. You can only rely on this file immediately after installation.
pls is the indicator to use the mod_plsql cartridge.
apex is the database access descriptor (DAD) defined in the mod_plsql configuration file.
For users who have upgraded from earlier releases, or who have a custom configuration, this value may be htmldb or something else. Verify your DAD with your Oracle Application Express administrator.
|
See Also: "Managing Oracle Database Port Numbers" in Oracle Database Installation Guide andORACLE_BASE\ORACLE_HTTPSERVER_HOME\Apache\modplsql\conf\dads.readme for more information on database access descriptors |
The Login page appears.
Under Login, enter the following:
In the Workspace field, enter the name of your workspace.
In the Username field, enter your user name.
In the Password field, enter your case-sensitive password.
Click Login.
Note that, depending on your setup, you might be required to change your password when you log in for the first time.
To verify the port number where the Oracle XML DB HTTP Server is running:
Start SQL*Plus and connect the database where Oracle Application Express is installed as SYS:
On Windows:
SYSTEM_DRIVE:\ sqlplus /nolog
connect sys as sysdba
On UNIX and Linux:
$ sqlplus /nolog connect sys as sysdba
When prompted, enter the appropriate username and password.
Enter the following statement to verify the port number:
SELECT DBMS_XDB.GETHTTPPORT FROM DUAL;
If the port number returns 0, the Oracle XML DB HTTP Server is disabled.
If you cannot remember your workspace name, you can request a list of all workspace names associated with your email address.
To find your workspace name:
On the Login page, click Find My Workspace on the Tasks list.
Enter your email address and click Find Workspace.
An email with the list workspace names is sent to you.
You can reset your password by clicking the Change Password link on the Workspace home page.
To reset your password from the Workspace home page:
Log in to Oracle Application Express. See "Logging In to Oracle Application Express".
From the Administration list, click Change Password.
The Change Password page appears.
In Change Password, enter the following:
Enter Current Password - Enter your current password.
Enter New Password - Enter your new password.
Confirm New Password - Enter your new password again.
Click Apply Changes.
|
Tip: You can also reset your password on the Login page by clicking the Reset Password link. |
When you log in to Oracle Application Express, the Workspace home page appears. A workspace is a virtual private database allowing multiple users to work within the same Oracle Application Express installation while keeping their objects, data and applications private.
Your user name and workspace name display in the lower left corner of the page. The following three large icons display in the center of the page:
Application Builder. Use Application Builder to assemble an HTML interface (or application) on top of database objects such as tables and procedures. See "Application Builder Concepts" and "Using Application Builder".
SQL Workshop. Use the SQL Workshop to access tools for viewing and managing database objects. Click SQL Workshop to access the following database tools:
Object Browser. View, create, modify, browse, and drop database objects. Use the PL/SQL editor to edit and compile packages, procedures, functions, and triggers while taking advantage of error reporting. See "Managing Database Objects with Object Browser" in Oracle Application Express SQL Workshop and Utilities Guide
SQL Commands. Run SQL commands and anonymous PL/SQL, scripts, and saved queries. See "Using SQL Commands" in Oracle Application Express SQL Workshop and Utilities Guide.
SQL Scripts. Use SQL Scripts to create, edit, view, run, and delete script files. You can also upload and download scripts from your local file system. See "Using SQL Scripts" in Oracle Application Express SQL Workshop and Utilities Guide.
Query Builder. Use Query Builder's graphical user interface to search and filter database objects, select objects and columns, create relationships between objects, view formatted query results, and save queries with little or no SQL knowledge. See "Building Queries with Query Builder" in Oracle Application Express SQL Workshop and Utilities Guide.
Utilities. Use Utilities to load and unload data from the database, generate DDL, view object reports, restore dropped database objects, and monitor the database. See "Using Oracle Application Express Utilities" in Oracle Application Express SQL Workshop and Utilities Guide.
An Administration list appears on the right side of the Workspace home page. Use the following links to administer your application development environment:
Administration links to the Application Administration page. Use this page to perform administrative tasks. See "About the Application Administration Page" in Oracle Application Express Administration Guide.
Manage Services links to the Manage Services page. Use this page to manage session state, log files, preferences, and application models. See "About the Manage Services Page" in Oracle Application Express Administration Guide.
Manage Application Express Users links to the Existing Users page. Use this page to manage existing Application Express users and user groups. See "Managing Application Express Users" and "Using Groups to Manage Application Express Users" in Oracle Application Express Administration Guide.
Monitor Activity links to the Monitor Activity page. Use this page to monitor page views and view application changes. See "Monitoring Activity within a Workspace" in "Oracle Application Express Administration Guide.
Change Password links to the Change Password page. Use this page to change your workspace password. See "Resetting Your Password" in Oracle Application Express Administration Guide.
About Application Express links to the About Application Express page. This page displays version and configuration information for both Application Express and the Oracle database. See "Viewing the Application Express Product Information Page" in Oracle Application Express Administration Guide.
Use the Application Migrations link to migrate a Microsoft Access application and generate an Oracle Application Express application. See Oracle Application Express Migration Guide.
The Workspace Schemas list displays beneath the Administration list. It displays the database schemas that are associated with, and therefore accessible to, this workspace.
The Links list displays on the lower side of the Workspace home page. Use this list to access the following Application Express resources:
Oracle Technology Network links to the Oracle Application Express section of Oracle Technology Network. Use this page to access additional information and resources about using Oracle Application Express.
Discussion Forum links to Oracle Application Express Discussion Forum. Use this page as a resource for research and for posting your own questions or answering those of other users.
User's Guide links to an HTML-based online Help system. You can also access online Help by clicking the Help link in the upper right corner of any page in Oracle Application Express. See "About Procedural Online Help".
This section describes alternative methods for navigating between pages in the Application Express user interface.
Navigating Using Icons or Drop Down Menus
You can move between pages in Oracle Application Express by clicking large graphical icons. When using these icons, you have two navigation options:
Primary Navigation (drill-down). Click a large icon to drill-down to the appropriate page.
Secondary Navigation (drop down menus). Click the down arrow on the right side of the icon to view a drop down menu. Select an option from the menu.
|
Note: For the purposes of consistency, this document uses the primary navigation path (or drill-down approach) when explaining navigation. |
Navigating Using Breadcrumbs
Breadcrumbs (also called locator links) appear at the top of every page within the Oracle Application Express user interface. Each breadcrumb entry indicates where the current page is relative to other pages within the user interface. You can use breadcrumbs to instantly link to a previous page. For example, clicking on Home takes you to the Workspace home page.
The Application Express user interface features three types of online help: Procedural Online Help, Page-level Help, and Field-Level Help.
About Procedural Online Help
You can access an HTML-based online Help system by clicking the Help link in the upper right corner of the window.
When you click the Help link, a help topic appears that describes the current page. To view the table of contents of another help set, select it from the list in the upper left side of the window.
You can browse through help topics by:
Expanding and collapsing the table of contents. To view a topic, simply select it.
Clicking the breadcrumb links at the top of each help topic.
Clicking the Previous and Next buttons within a topic. Click these buttons to access the previous and next help topic within the structure of the help set.
The top of the window features a gray bar. Click Back and Forward to return to a previously viewed page. These controls work similarly to the Back and Forward controls in a Web browser.
Click Find to perform a keyword search of the entire help system. When the search field appears, enter a case insensitive query in the field provided and click Find. To search for an exact phrase, enclose the phrase in double quotation marks.
|
Tip: With Oracle Database 11g, you must enable network services in order use the Find link. See "Enabling Network Services in Oracle Database 11g" |
About Page-level Help
Many pages with in the Application Express user interface include Page-level Help. Page-level Help displays in a text box on the right side of the page and offers a brief description of the page functionality.
About Field-Level Help
Most select lists, check boxes, items, and fields within the Application Express user interface include Field-level Help. Items within the user interface that have Field-level Help have a light gray underline. When Field-level Help is available, the item label changes to red when you pass your cursor over it and the cursor changes to an arrow and question mark.
Click the item label to display a description in a separate window.
This section describes how to run the two demonstration applications provided with Oracle Application Express. It also explains how to modify the demonstration application called Sample Application that installs with Application Builder. Running and analyzing how an application works is an effective way to better understand how you can use Application Builder to build your own applications.
This section contains the following topics:
|
See Also: "Next Steps" in Oracle Database 2 Day + Oracle Application Express Developer's Guide to learn more about other resources to expand your knowledge of Oracle Application Express |
Application Builder includes two demonstration applications you can install. Use these applications to learn more about the different types of functionality you can include in your applications.
To install the demonstration applications:
From the Workspace home page, click the down arrow on the right side of the Application Builder icon.
From the menu, select Demonstrations.
The Demonstration Applications page appears, displaying the following applications:
To install a demonstration application, locate the application you want to install, and click Install.
Follow the on-screen instructions.
The Application home page appears.
To run an installed demonstration application, click the Run Application icon.
Enter the appropriate login credentials and click Login.
For Sample Application:
For User Name, enter either demo or admin.
For Password, enter the current workspace name in lowercase letters.
For other demonstration applications, enter your workspace user name and password.
|
Note: You can also access the Demonstration Applications page by clicking Create on the Application home page and then selecting Demonstration Application. |
Once you have installed a demonstration application, you can run it from the Demonstration Applications page or from the Application Builder home page.
Topics in this section include:
To run a demonstration application from the Demonstration Applications page:
From the Workspace home page, click the down arrow on the right side of the Application Builder icon.
From the menu, select Demonstrations.
The Demonstration Applications page appears.
On the Demonstration Applications page, locate the application you want to run.
In the Action column, click Run.
Enter the appropriate login credentials and click Login.
For Sample Application:
For User Name, enter either demo or admin.
For Password, enter the current workspace name in lowercase letters.
For other demonstration applications, enter your workspace user name and password.
Once you have installed a demonstration application, you can run it from the Application Builder home page.
To run a demonstration application from the Application Builder home page:
Log in to the Workspace home page.
Click the Application Builder icon.
Click the application to be run.
The Application home page appears.
Click the Run Application icon.
Enter the appropriate login credentials and click Login.
For Sample Application:
For User Name, enter either demo or admin.
For Password, enter the current workspace name in lowercase letters.
For other demonstration applications, enter your workspace user name and password.
This section describes the demonstration application called Sample Application.
Sample Application shows an easy-to-use interface for viewing, updating, and searching order and customer information for electronic and computer products. Users can navigate among the pages using the Home, Customers, Products, Orders, and Charts tabs.
Sample Application demonstrates the following functionality:
Examples of ways to display summary information, including a dial chart and summary reports
Reports for viewing, updating, and adding customers, products, and orders
A Calendar report
Flash charts available in Oracle Application Express including cluster bar, pie chart, and stacked bar
Printer friendly mode
The following sections describe specific functionality available on each page.
The Home page contains four regions:
My Quota
My Orders
Sample Application
Tasks
My Quota demonstrates the use of a Flash Dial Chart. This chart displays a value based on an underlying SQL statement.
Although not demonstrated in this example, you can enable an asynchronous refresh by editing the attributes of any SVG or Flash chart.
|
Tip: The Flash Dial Chart only displays if you log in using the user namedemo. |
My Orders is a interactive report based on a SQL query. This report displays a subset of the information that appears on the Orders page. Users can link to order details by selecting the Edit icon. Users can also change the appearance of the report using the Actions menu.
Sample Application is a simple HTML region that displays static text. You can create this type of region to display explanatory information to users.
Tasks contains a list with links to other pages within the application. Links available on the Home page Tasks list include:
About this Application links to an informational page that describes this application.
Enter a New Order links to a wizard for creating a new order.
Add a New Customer links to a form for entering new customer information.
Add a New Product links to a form for adding new products.
The Customers page enables users to view and edit customer information. The Customers page consists of two main regions:
Customers
Top Customers
Customers is an interactive report for tracking customer information. This region is also based on a SQL query. To search for a customer, enter a customer name in the Search field and click Go. To sort by customer name, click the column heading. A Sort icon then appears to the right of the heading Customer Name. Users can change the appearance of the report using the Actions menu. To update existing customer information, click the Edit icon. 'To add a new customer, click the New Customer button.
Top Customers ranks customers by order amount. This report is based on a SQL query that returns top customers based on their orders.
The Products page enables users to view and edit product information. The Products page consists of two main regions:
Products
Top 10 Products
Products displays an interactive report for tracking product information. This region is based on a SQL query that uses a custom function for displaying images stored in the database. To sort by product category, click the column heading. To edit a product description, click the Edit icon. To add a new product, click the Create Product button at the top of the page. Users can change the appearance of the report using the Actions menu.
Top 10 Products is also a SQL report. This report outlines the top ten products based on quantities sold.
The Orders page enables users to view and edit customer orders. The Orders page contains two regions:
My Orders
Orders by Day
My Orders is a wizard report that summarizes the current orders in the system. To sort a column, click the column heading. A Sort icon then appears to the right of the column heading. To edit an existing order, click the Edit icon. To add a new order, click the Enter New Order button.
Orders by Day is a Calendar report. This report displays each order on the appropriate date in a calendar. Users can select a calendar entry to view order details. Click the Previous and Next buttons to previous and future entries.
The Charts page illustrates three types of Flash charts available in Application Builder: cluster bar, pie chart, and stacked bar. To view a chart, select it from the list on the left.
The Admin page displays only if you log in to Sample Application using the user name admin. Sample Application makes use of a custom authentication scheme that stores user names and obfuscated passwords in a table. The Manage Users page enables you to manage additional users. To add a new user, click Add User at the bottom of the page. To delete a user, select the user and click Remove Selected Users.
Note that this custom authentication scheme does not use any user names or passwords associated with Oracle Application Express application developers.
Clicking Print in the upper left corner of the page displays the current page in Printer Friendly mode. When in Printer Friendly mode, the Application Express engine displays all text within the HTML form fields as text.
To enable your application to display in Printer Friendly mode, you must create and then specify a Print Mode Page Template on the Edit Definition page.
Once you understand the type of functionality available in a demonstration application, the next step is to learn more about the construction of each page. An efficient way to speed up the learning process is to analyze and deconstruct the pages in the demonstration applications. If you happen to break something, you can quickly delete the demonstration application and install it again. See "Deleting an Application" and "Installing a Demonstration Application".
You edit existing pages in an application, add pages to an application, or create entirely new applications using Application Builder.
Topics in this section include:
The Developer toolbar is a quick way to edit the current application, the current running page, create a new page, control, or component, view session state, or turn edit links on or off.
The Developer toolbar consists of the following links:
Home links you to the Workspace home page. See "About the Workspace Home Page".
Application links you to the Application home page. See "Application Builder Concepts".
Edit Page accesses the Page Definition for the current running page. See "About the Page Definition".
Create links to a wizard for creating a new page, region, page control (item, button, branch, computation, process, or validation), or a shared control (navigation bar icon, tab, list of values, list, or breadcrumb). See "Building an Application".
Session links you to session state information for the current page. See "Viewing Session State".
Activity links you to the Activity reports page. See "Activity Reports".
Debug toggles the page between Debug and No Debug mode. See "Accessing Debug Mode".
Show Edit Links toggles between Show Edit Links and Hide Edit Links. Clicking Show Edit Links displays a small orange icon next to each editable object on the page. Each icon is orange and contains a triangle with two rules beneath it. Clicking the link displays another window in which to edit the object.
There are two ways to edit a demonstration application:
From the Demonstration Applications page, click Edit next to the desired application.
If you are running an application, click Application on the Developer toolbar.
The Application home page appears. The application ID and application name display at the top of the page.
You can run the current application, edit supporting objects, create shared components, or export and import information by clicking one of the following:
Run Application submits the pages in the current application to the Application Express engine to render viewable HTML. See "How the Application Express Engine Renders and Processes Pages".
Supporting Objects links to the Supporting Objects page. See "How to Create a Packaged Application".
Shared Components links to a list of shared components and user interface controls that can display or be applied on every page within an application. See "Working with Shared Components".
Export/Import links you to the Export/Import Wizard. Use this wizard to import and export an entire application and related files such as cascading style sheets, images, static files, script files, themes, user interface defaults, and workspace users. See "Exporting an Application and Related Files".
The pages that make up the application appear on the Application home page. To access a specific page, simply click it. To search for a specific page, enter a case insensitive query for the page title or page number in the Page field and click Go.
The Application Express engine renders applications in real time based on data stored in database tables. You can view the database objects for any demonstration application in Object Browser, or by viewing the Application Database Object Dependencies report.
Topics in this section include:
The Database Object Dependencies report identifies database objects referenced by the current application. Review this report to determine what objects to move when deploying an application.
To view the Database Object Dependencies report:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
The Application home page appears.
On the Tasks list, click Application Reports.
Click Shared Components.
Under Application, click Database Object Dependencies.
Click Compute Dependencies.
To view the components that reference a specific database object, select the Reference Count number.
To view the database objects in Object Browser:
On the Workspace home page, click SQL Workshop and then Object Browser.
Object Browser appears.
Select an object type from the Object list in the upper left corner of the page. For example, to view tables, select Tables.
To search for an object name, enter keywords in the search field beneath the Object list.
A list of matching objects appears.
To perform a specific task related to the selected object, select the appropriate task button.
For example, to modify a column in the DEMO_CUSTOMERS table:
From the Objects list, select Tables.
From the Tables list, select DEMO_CUSTOMERS.
Click Modify Column.
To view additional object details, select a tab beneath the object name. For example, to view the data in the DEMO_CUSTOMERS table:
From the Tables list, select DEMO_CUSTOMERS.
Select the Data tab.
A report appears that displays the data in the DEMO_CUSTOMERS table appears.
|
See Also: "Man^aging Database Objects with Object Browser" in Oracle Application Express SQL Workshop and Utilities Guide |
This section describes how to package an application built within Application Builder.
This section contains the following topics:
|
See Also: "Advanced Programming Techniques" and "Managing Application Express Users" in Oracle Application Express Administration Guide |
When developing applications using Application Builder, you need to find a balance between two dramatically different development methodologies:
Iterative, rapid application development
Planned, linear style development
The first approach offers so much flexibility that you run the risk of never completing your project. In contrast, the second approach can yield applications that do not meet the needs of end users even if they meet the stated requirements on paper.
The system development life cycle (SDLC) is the overall process of developing software using a series of defined steps. There are a number of SDLC models that work well for developing applications in Oracle Application Express.
The SDLC waterfall is probably the best known model. In this methodology, the development process is broken down into the following stages:
Project Planning
Requirements Definition
Design
Development
Integration and Testing
Installation and Acceptance
Maintenance
This methodology is referred to as a waterfall because the output from one stage is the input for the next stage. One of the primary problems with this approach is that it is assumed that all requirements can be established in advance. Unfortunately, requirements often change and evolve during the development process.
The Oracle Application Express development environment enables developers to take a more iterative approach to development. Unlike many other development environments, creating prototypes is easy. With Oracle Application Express, developers can:
Use built-in wizards to quickly design an application user interface
Make protoypes available to users and gather feedback
Implement changes in real time, creating new prototypes instantly
Other methodologies that work well with Oracle Application Express include:
Spiral - This approach is actually a series of short waterfall cycles. Each waterfall cycle yields new requirements and enables the development team to create a robust series of prototypes.
Rapid application development (RAD) life cycle - This approach has a heavy emphasis on creating a prototype that closely resembles the final product. The prototype is an essential part of the requirements phase. One disadvantage of this model is that the emphasis on creating the prototype can cause scope creep; developers can lose sight of their initial goals in the attempt to create the perfect application.
To move an application from one Oracle Application Express instance to another, you must move both the metadata and supporting objects used by the application as follows:
Move the application definition and all associated files. See "How to Move an Application to Another Development Instance".
Move the supporting objects. Review the Database Dependencies report to determine what objects to move. See "About the Database Object Dependencies Report" and "How to Create a Packaged Application".
This section contains the following topics:
When you develop an application in Application Builder, you create the application within a specific workspace. Each workspace has a unique ID and name. A common scenario is to create the application in a development instance and then deploy it to a production instance.
During the deployment process, you must decide whether you want to use the existing application ID, the existing workspace, the existing database, the existing Oracle HTTP Server, or create new ones. Deployment options to consider include:
Create Application Express End Users. The simplest way to deploy an application is to create Application Express end users and then send the URL and login information to users. This approach works well for applications with a small and tolerant user population. See "About Publishing the Application URL" and "Managing Application Express Users" in Oracle Application Express Administration Guide.
Use the same workspace and same schema. Export and then import the application and install it using a different application ID. This approach works well when there are few changes to the underlying objects, but frequent changes to the application functionality.
Use a different workspace and same schema. Export and then import the application into a different workspace. This is an effective way to prevent a production application from being modified by developers.
Use a different workspace and different schema. Export and then import the application into a different workspace and install it so that it uses a different schema. This new schema will need to have the database objects required by your application. See "About the Database Object Dependencies Report".
Use a different database with all its variations. Export and then import the application into a different Oracle Application Express instance and install it using a different schema and database.
Deciding whether to copy an existing workspace is a matter of preference. Keep in mind that the production version must have access to all the appropriate objects. For example, you might want to copy a workspace in the following situations:
When the application subscribes to other Oracle Application Express objects within the workspace.
When the application relies on Oracle Application Express authentication. Copying the workspace automatically migrates all the required user data.
When deciding whether to copy the database, remember that the schema against which the application runs must have access to the same objects as the development instance. The actual name of the schema is unimportant. You can change it during the import process.
It is not necessary to have matching application IDs for a development version and production version of an application. In fact, as a best practice never hard code the application ID into your application. Instead, use the application alias (defined on the Edit Definition page), or use a built-in substitution string (such as APP_ID and APP_ALIAS). Using a substitution string is the better approach because it enables you to change the application ID without affecting any application functionality.
|
See Also: "Name" for information about defining an application alias and "About Built-in Substitution Strings" for information about usingAPP_ID and APP_ALIAS |
In order to run, Oracle Application Express must have access to either the embedded PL/SQL gateway or Oracle HTTP Server and mod_plsql. Installing a new HTTP server is another way to separate a development version and production version of an application. To learn more about HTTP server configuration options, see "Choosing a HTTP Server" in the appropriate installation guide for your operating environment. See "Related Documents".
Whether you want to move an application to another workspace or just make a copy of it, deploying involves the following steps:
Move the supporting database objects (if appropriate). Review the Database Dependencies report to determine what objects to move. See "About the Database Object Dependencies Report".
Package an application definition with its supporting objects to create a packaged application. See "How to Create a Packaged Application".
Import the exported files into the target Oracle Application Express instance. See "Importing Export Files".
Note that if the target instance is a different schema, you also need to export and import any required database objects.
Install the exported files from Export Repository. See "Installing Export Files".
You can import an application into your workspace regardless of the workspace in which it was developed. See "Deployment Options to Consider".
|
Tip: You can also move the application definition and all supporting objects manually. See "Exporting an Application and Related Files". |
Before you export an application and the appropriate related files, you must determine if you also need to migrate the database objects referenced by the application. If you are unsure of which database objects to move, review the Database Object Dependencies report.
If the target schema is different from the schema used in the development environment, you need to migrate the database objects referenced by the application. In many cases, this process can be as simple as using Oracle database export and import utilities to copy the application schema from the development environment to target instance. The following are two common scenarios where this approach does not work:
When the object development schema refers to tablespaces to which the target instance schema does not have access
When the development instance schema has sample data that you do not want to migrate to the target instance schema
If a database administrator or an Oracle Application Express administrator is the person responsible for exporting Oracle Application Express applications, be sure to clearly communicate if he or she:
Should include all data when exporting your application
Should not include data from specific tables you identify
|
Tip: "Loading and Unloading Data from the Database" in Oracle Application Express SQL Workshop and Utilities Guide |
You can greatly simplify the steps needed to deploy an application by creating a packaged application on the Supporting Objects page.
This section contains the following topics:
Adding Installation Scripts for an Image, Cascading Style Sheet, or Static File
Deleting Supporting Objects Scripts, Messages, and Installation Options
From a user's perspective, importing and installing an application is a complicated process. First, you create the target database objects and seed data. Second, you import and install the application definition and all related files, including images, themes, and any other required static files.
Creating a packaged application using the Supporting Objects utility greatly simplifies this process. Instead of performing numerous steps to create the database objects and then import and install the application and all supporting files, you can define the supporting objects so that the application and supporting files can be migrated in a few easy steps.
After users import and install the application definition, a wizard guides them through a few simple configuration steps. Then, the wizard asks whether to install the supporting application objects. Users have the option of installing the supporting application objects then or doing it later.
From a developer's perspective, this feature has a number of advantages:
Ensures that the supporting objects are created in the correct order.
Provides users with an automated process for deploying an application quickly using very few steps.
Gives users the option to install supporting application objects when they import and install the application definition or at a later time. See "Installing Supporting Objects".
Enables users and developers with a convenient method for removing the application definition, supporting files, and all database objects. See "Deinstalling Supporting Objects".
Enables users and developers with an easy way to upgrade a previously released packaged application. See "Upgrading a Packaged Application".
Plus, you can also take advantage of the Deinstall and Install features to quickly edit the underlying database objects that support an application. For example, you can deinstall and remove all database objects, edit the underlying database object creation scripts, and reinstall to create the redefined application objects.
To create a packaged application, you must create installation scripts that define your application's supporting objects (including database objects, images, and seed data) and any preinstallation validations. You define these objects and the installation and deinstallation scripts and the messages that display when the user installs or deinstalls on the Supporting Objects page.
This section contains the following topics:
You create a packaged application on the Supporting Objects page.
To access the Supporting Objects Page application:
On the Workspace home page, click the Application Builder icon.
Select the application.
The Application home page appears.
Click the Supporting Objects icon.
The Supporting Objects page appears.
The top of the Supporting Objects page displays the application name and indicates current selections for the following: Check for Objects, Verify System Privileges, Required Free KB, Prompt for License, Substitutions, Build Options, Validations, Installation Scripts, Upgrade Scripts, Deinstallation Script, and Include in Export.
The rest of the page is divided into four categories.
Use the links under Installation to define the following types of information:
Prerequisites. Defines built-in checks required before installing the application, including required free disk space, required system privileges, and schema object restrictions.
Application substitution strings. Lists static substitution strings defined for the application. You can define static substitution strings for phrases or labels that occur in many places within an application. See "Substitutions".
When packaging an application, you can include prompts for substitution strings which users can specify when they install the packaged application.
Build Options. Lists build options defined for this application. You can use build options to conditionally display specific functionality within an application. See "Using Build Options to Control Configuration" and "Exporting Build Options or Build Option Status".
When packaging an application, you can include prompts for specific build options which display when the application is installed.
Pre-installation Validations. Lists validations defined for the packaged application. Similar to normal page validations, these validations prevent a user from installing database objects if the user-defined conditions are not satisfied. To create a new validation, click Create and follow the on-screen instructions.
Installation Scripts. Enables a you to define multiple installation scripts that install supporting objects for the application. To create a new script, click Create and follow the on-screen instructions. To edit an existing script, click the Edit icon.
Use the links under Message to define message to display when the user installs or deinstalls the application. Supported HTML tags include <b>, <i>, <u>, <p>, <br>, <hr>, <ul>, <ol>, <li>, and <pre>. Available message types include:
Welcome
License
Application Substitutions
Build Options
Validations
Confirmation
Post Installation
Upgrade
Deinstallation
Note that when these messages display, only a limited set of HTML tags are recognized in order to prevent a cross site-scripting (XSS) attack. See "Understanding Cross-Site Scripting Protection".
Click Upgrade scripts to define scripts to upgrade database objects, images, and seed data when upgrading an existing application. See "Upgrading a Packaged Application".
You can create installation scripts for images, cascading style sheets, and static files you have previously uploaded for your application or workspace on the Installation Scripts page. Oracle Application Express uses the name of the file you select as the name for each new script. It also adds corresponding API calls to the end of the deinstallation script (or creates one if one does not already exist), which removes the selected files when the application's supporting objects are deinstalled.
To create installation scripts for an image, cascading style sheet, or static file:
Navigate to the Supporting Objects page:
On the Workspace home page, click the Application Builder icon.
Select the application.
The Application home page appears.
Click Supporting Objects.
The Supporting Objects page appears.
Under Installation, click Installation scripts.
The Installation Scripts page appears.
Click Create.
At the bottom of the page, click Create Script to Install Files.
A list of available cascading style sheets, images, and static files appears.
Select the files to include with your packaged application and click Create Script.
You can control access to an application, individual pages, or page components by creating an access control list.
To add an access control list of a packaged application:
Create an access control list. See "Controlling Access to Applications, Pages, and Page Components".
Navigate to the Supporting Objects page:
On the Workspace home page, click the Application Builder icon.
Select the application.
The Application home page appears.
Click Supporting Objects.
The Supporting Objects page appears.
Under Installation, click Installation scripts.
The Installation Scripts page appears.
Click Create.
At the bottom of the page, click Create Scripts for Access Control Tables.
If Access Control tables are defined, the Create Script page displays the tables to be included.
Click Create Script.
After you edit your supporting objects and create the appropriate scripts, you can run your installation scripts by clicking Install Supporting Objects on the Tasks list.
End users can also use this feature if they elect to not install the packaged application (or supporting objects) after they import and install the application definition.
To install supporting objects:
On the Workspace home page, click the Application Builder icon.
Select the application.
Click < span class="bold">Supporting Objects.
The Supporting Objects page appears.
Click the Install Supporting Objects on the Tasks list.
To view details about the installation script before running it, click Preview Installation Script.
The Preview Scripts page appears listing summary information, prerequisites, and the actual scripts to be run.
To exit the Preview Scripts page and continue, click Close.
From Install Supporting Objects, click Yes and click Next.
Follow the on-screen instructions.
You can delete the metadata that defines supporting object scripts, messages, and installation options associated with a packaged application by clicking Remove Supporting Object Installation on the Tasks list on the Supporting Objects page.
To delete the metadata that defines supporting object scripts, messages, and installation options:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Supporting Objects.
The Supporting Objects page appears.
On the Tasks list on the right side of the page, click Remove Supporting Object Installation.
Follow the on-screen instructions.
You can define scripts to upgrade a previously published application on the Upgrade page.
This section contains the following topics:
You can use the Upgrade page to define scripts to upgrade database objects, images, and seed data when upgrading an existing application.
To create an upgrade script:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Supporting Objects.
The Supporting Objects page appears.
Under Upgrade, click Upgrade Scripts.
To create a script, click Create.
|
Tip: To enable users to upgrade from various earlier versions of this application, you can add conditions to the upgrade scripts by going to the Script Properties page. |
Use the Detect Existing Supporting Objects section to determine if the appropriate objects are installed or need to be upgraded.
In Query to Detect Existing Supporting Objects, enter a query in the field provided that returns at least one row if the supporting objects exist.
This query determines whether the user who installs the packaged application is prompted to run the installation scripts or the upgrade scripts.
Follow the on-screen instructions.
After you create your upgrade script, you can test it by clicking Upgrade Supporting Objects on Tasks list on the Supporting Object page.
End users can also use this feature to upgrade an existing packaged application.
To upgrade a packaged application:
Import a new version of application to be upgraded (if applicable). See "Importing an Application or Page".
On the Workspace home page, click the Application Builder icon.
Select the application.
Click Supporting Objects.
The Supporting Objects page appears.
From the Tasks list, click Upgrade Supporting Objects.
Follow the on-screen instructions.
Once you create or install a packaged application, you can deinstall it by either:
Clicking the Deinstall Supporting Objects on the Supporting Objects page
Clicking Delete this Application on the Application home page
When you deinstall an application, you have the option of removing the current application definition and running the deinstallation script defined in the Supporting Objects.
To deinstall a packaged application:
On the Workspace home page, click the Application Builder icon.
Select the application.
Click Supporting Objects.
The Supporting Objects page appears.
Click Deinstall Supporting Objects.
Select a deinstallation option:
Remove Application Definition removes the current application definition.
Deinstall Database Objects runs the deinstallation script defined in the deployment attributes for this application.
Follow the on-screen instructions.
You can view a log of recent installation and deinstallation by clicking View Install Summary on the Tasks list on the Supporting Objects page. Note that this log only displays results from the most recent installation or deinstallation that occurred during the current Application Express session.
To view the Install Summary:
On the Workspace home page, click the Application Builder icon.
Select the application.
Click Supporting Objects.
The Supporting Objects page appears.
On the Tasks list on the right side of the page, click View Install Summary.
A Summary page appears.
You export and import application definitions and all associated files using the Workspace Users, Application, CSS, Images, Files, Themes, and User Interface Defaults tabs located at the top of the Export page. Note that it is not necessary to export a workspace unless you want to migrate workspace users or replicate shared component subscriptions in the target instance.
Once you export an application and any related files, you must import them into the target Oracle Application Express instance and then install them. As a general rule, always import the application first and then the related files. See "How to Move an Application to Another Development Instance".
|
Tip: You can simplify the steps needed to deploy an application by creating a packaged application. See "How to Create a Packaged Application". |
This section contains the following topics:
When you export an application, Oracle Application Express generates a text file containing PL/SQL API calls.
To export an application:
Navigate to the Export page:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Export/Import.
On the Export/Import page, click Export and then click Next.
From Application, select the application to be exported.
From File Format, select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
From Owner Override, optionally select another owner. By default, the application is owned by the owner identified in the application attribute owner.
From Build Status Override, select one of the following:
Run Application Only - Developers can only run an application
Run and Build Application - Developers can both run and edit an application
Selecting Run Application Only is an effective way to protect an application from modifications from other developers.
|
Tip: If you select Run Application Only, you cannot set the argumentp_trace to Yes. See "Using Build Options to Control Configuration". Also, the only way to change this setting after you import the application, is to log in to Oracle Application Express Administration Services. See "Changing Application Build Status Set During Deployment" in Oracle Application Express Administration Guide. |
From Debugging, select one of the following:
Yes exports the application with debugging enabled.
No exports the application with debugging disabled.
From Exporting Supporting Object Definitions, specify whether to export supporting object definitions with your application. Available options include: See "How to Create a Packaged Application".
From Export Comments, specify whether to export comments for this application. See "Adding Developer Comments".
Use the As of field to export your application as it was previously defined. Specify the number of minutes in the field provided.
This utility uses the DBMS_FLASHBACK package. Because the timestamp to System Change Number (SCN) mapping is refreshed approximately every five minutes, you may have to wait that amount of time to locate the version for which you are looking. The time undo information is retained and influenced by the startup parameter UNDO_RETENTION (the default is three hours). However, this only influences the size of the undo tablespace. While two databases can have the same UNDO_RETENTION parameter, you are able to go back further in time on a database with fewer transactions because it is not filling the undo tablespace, forcing older data to be archived.
Click Export Application.
In addition to exporting the actual application file, you may also need to export other related files such as cascading style sheets, images, and script files.
You can make an application available to other users by creating workspace users. When you export workspace users, Oracle Application Express creates an ASCII text SQL script of users and any defined user groups.
To export workspace users:
Navigate to the Export page:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Export/Import.
On the Export/Import page, click Export and then click Next.
On the Export page, click the Workspace Users tab.
From File Format, select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
Click Export Workspace Users.
You can export shared components or components of a page on the Component Export page. You can use this wizard to:
Export shared components or page components to another application or workspace
Back up a component before editing it
Create an export to function as a patch to another Oracle Application Express instance
To export shared components or page components:
Navigate to the Component Export page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
From the Tasks list, click Export Application Components.
The Component Export page appears.
Click the following tabs and select the components to be exported:
Components displays shared application components and entire pages. Use the navigation bar at the top of the page to search for components. See "Working with Shared Components" and "Exporting Build Options or Build Option Status".
Components by Page lists components of the selected page. Navigate to a specific page by making a selection from the Page. Click Check All to select all components.
Application Attributes displays application attributes. Press CTRL or SHIFT to select multiple attributes. See "About the Edit Definition Page".
Build Option Status displays available build options. Use this page to turn build options on and off. See "Exporting Build Options or Build Option Status".
Click Add to Export.
Click Next.
On Components to Export:
From File Format, select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
Use the As of field to export a page as it was previously defined. Specify the number of minutes in the field provided.
This utility uses the DBMS_FLASHBACK package. Because the timestamp to System Change Number (SCN) mapping is refreshed approximately every five minutes, you may have to wait that amount of time to locate the version for which you are looking. The time undo information is retained and influenced by the startup parameter UNDO_RETENTION (the default is three hours). However, this only influences the size of the undo tablespace. While two databases may have the same UNDO_RETENTION parameter, you are able to go back further in time on a database with fewer transactions because it is not filling the undo tablespace, forcing older data to be archived.
Click Export Components.
You can also export a specific page within an application by clicking the Export page icon on the Page Definition. When exporting a page, remember that exported pages can only be imported sucessfully if they have the same application ID and workspace ID.
To export a page in an application:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
On the Page Definition, you can export a page in two ways:
Click the Export Page icon, the down arrow in the upper right corner.
From the View list, select Export and click Go.
The Export Page Wizard appears.
From Page, select the page to be exported.
From File Format, select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
Use the As of field to export a page as it was previously defined. Specify the number of minutes in the field provided.
This utility uses the DBMS_FLASHBACK package. Because the timestamp to System Change Number (SCN) mapping is refreshed approximately every five minutes, you may have to wait that amount of time to locate the version for which you are looking. The time undo information is retained and influenced by the startup parameter UNDO_RETENTION (the default is three hours). However, this only influences the size of the undo tablespace. While two databases may have the same UNDO_RETENTION parameter, you are able to go back further in time on a database with fewer transactions because it is not filling the undo tablespace, forcing older data to be archived.
Click Export Page.
Use the Export Cascading Style Sheets utility to export uploaded cascading style sheets. Note that you can use this utility to export only uploaded cascading style sheets.
To export related cascading style sheets:
Navigate to the Export page:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Export/Import.
On the Export/Import page, click Export and then click Next.
Click the CSS tab at the top of the page.
On the Export Cascading Style Sheets page, select the following:
Stylesheets - Select the cascading style sheets to export.
File Format - Select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
Click Export Style Sheets.
Use the Export Images utility to export uploaded images. When you export images using this utility, the images are converted to a text document. Note that you can use this utility to export only uploaded images.
To export upload images:
Navigate to the Export page:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Export/Import.
On the Export/Import page, click Export and then click Next.
Click the Images tab at the top of the page.
On the Export Images page, select the following:
Export Images in Application - Select an application from which to export images.
Be aware that selecting Workspace Images only exports those images in your repository that are not associated with a specific application. If all of your images are associated with specific applications, then the workspace image export file will be empty.
File Format - Select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
Click Export Images.
Use the Export Static Files utility to export static files you have imported. Note that you can use this utility to export only uploaded static files.
To export related static files:
Navigate to the Export page:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Export/Import.
On the Export/Import page, click Export and then click Next.
Click the Files tab at the top of the page.
On Export Static Files, select the following:
Static Files - Select the files to be exported.
File Format - Select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
Click Export File(s).
Note that you cannot use the Web interface described in this section to import exported static files into another Oracle Application Express instance. To import exported static files into another Oracle Application Express instance, use SQL*Plus while connected to the database. Note that you must export from and to a workspace having the same name and workspace ID.
You can transfer selected scripts from your current Script Repository to a Script Repository in a different Workspace by using the Export and Import tasks.
To export script files:
On the Workspace home page, click the SQL Workshop icon.
Click SQL Scripts.
On the Tasks list, click Export.
Select the appropriate script files and click Add to Export.
Review the file name and click Export All.
Select the Remove check box to remove the script.
Use the Export Theme utility to export themes from one Oracle Application Express development instance to a file.
To export an application theme from the Export page:
Navigate to the Export page:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Export/Import.
On the Export/Import page, click Export and click Next.
Click the Themes tab at the top of the page.
On the Export Application Theme page, select the following:
Export Theme - Select the theme to be exported.
File Format - Select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
Click Export Theme.
To export an application theme from the Themes page:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Shared Components.
Under User Interface, select Themes.
The Themes page appears.
On the Tasks list, click Export Theme.
The Export page appears.
On the Export Theme page, select the following:
Export Theme - Select the theme to be exported.
File Format - Select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
Click Export Theme.
Exporting User Interface Defaults is useful when you plan to develop on a target system.
When you export User Interface Defaults, all User Interface Defaults for the selected schema are exported to a single SQL Command script. When prompted, save this file to your hard drive. The file contains an API call to create table hints by making calls to the application PL/SQL API. You can use this file to import User Interface Defaults to another database and Oracle Application Express instance.
To export User Interface Defaults from the Export page:
Navigate to the Export page:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Export/Import.
On the Export/Import page, click Export and click Next.
Click the User Interface Defaults tab at the top of the page.
On the Export User Interface Defaults page, select the following:
Schema - Select the schema that owns the table associated with the User Interface Defaults.
File Format - Select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
Click Export User Interface Defaults.
To export User Interface Defaults from the User Interface Defaults page:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application Builder home page, click Shared Components.
Under User Interface, select User Interface Defaults.
The User Interface Defaults page appears.
From the Tasks list, click Export.
On the Export User Interface Defaults page, select the following:
Schema - Select the schema that owns the table associated with the User Interface Defaults.
File Format - Select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
Click Export User Interface Defaults.
In order to run, Oracle Application Express must have access to either Oracle HTTP Server and mod_plsql or the embedded PL/SQL gateway. Where images, CSS, and script files are stored depends upon the HTTP server you choose.
This section contains the following topics:
Where Images, CSS, and Script Files Are Stored When Using Oracle HTTP Server
Where Images, CSS, and Script Files Are Stored When Using the Embedded PL/SQL Gateway
In an Oracle HTTP Server or Oracle Application Server configuration, images are stored on the file system in the location referenced by the alias /i/. To locate the images directory on the file system, review the following files and search for the text alias /i/:
Oracle9i HTTP Server Release 2—see the httpd.conf file.
Oracle HTTP Server distributed with Oracle Database 11g—see the dads.conf file.
Oracle Application Server 10g—see the marvel.conf file.
Specific examples for locating the text alias /i/ can be found in Oracle Application Express Installation Guide
When running Oracle Application Express with the embedded PL/SQL gateway, images are stored directly in the database within the Oracle XML DB repository. You can access images by using the WebDAV feature of Oracle XML DB or by using FTP. To learn more, see "Using Protocols to Access the Repository" in Oracle XML DB Developer's Guide.
Once you export an application and any related files, you need to import them into the target Oracle Application Express instance before you can install them. As a general rule, always import the application first and then the related files. See "How to Move an Application to Another Development Instance".
|
Tip: You can simplify the steps needed to deploy an application by creating a packaged application. See "How to Create a Packaged Application". |
This section contains the following topics:
To import an Application or Page Export into a target Oracle Application Express instance:
Navigate to the Import page:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Export/Import.
On the Export/Import page, click Import and then click Next.
For Specify File, specify the following:
Import file - Click Browse and navigate to the file.
File Type - Select Application, Page, or Component Export.
Verify that File Character Set is correct.
Click Next.
Once you import a file, you have the option to install it.
To install an imported file, click Next.
The Install Application wizard appears.
In the Install Application wizard, specify the following:
Parsing Schema - Select a schema.
This is the schema against which all of the application's SQL and PL/SQL will be parsed.
Build Status - Select one of the following:
Run Application Only - Users can only run an application.
Run and Build Application - Users can run an application and developers can both run and edit an application.
Selecting Run Application Only is an effective way to protect an application from modifications from other developers.
|
Tip: If you select Run Application Only, the only way to change this setting after you import the application is to log in to Oracle Application Express Administration Services. See "Changing Application Build Status Set During Deployment" in Oracle Application Express Administration Guide. |
Install As Application - Select one of the following:
Auto Assign New Application ID
Reuse Application ID From Export File
Change Application ID
Use these options to avoid application ID conflicts. These options come in handy when you have two versions of the same application in the same instance. For example, you might be migrating an application to a production instance and still need to maintain the development version.
Click Install.
If you are installing a packaged application (that is, one for which you have defined Supporting Objects), the installer prompts you to install the packaged installation scripts. Follow the on-screen instructions.
Application groups are exported with an application, application exports include an group ID, name, and comments. When importing an application, the application import follows these rules:
On import, an application uses an existing group if the ID matches.
If no application group exists with the same ID on the target machine, then application import looks for another group ID with the same name. If a name match is found, the application is imported with the ID corresponding to this application group name.
If no ID or name matches existing application groups on the target machine then a new application group is created. The new application group will use the application group ID if that ID is not used in that Oracle Application Express instance. If the group ID is being used, then a new ID will be generated.
After you import an application into the target Oracle Application Express instance, you must import all related files.
To import a CSS Export file:
Navigate to the Import page:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Export/Import.
On the Export/Import page, click Import and then click Next.
For Specify File, select the following:
Import file - Click Browse and navigate to the file.
File Type - Select CSS Export.
File Character Set - Verify that File Character Set is correct.
Click Next.
Once you import a file, you have the option to install it.
To install an imported file, click Next.
Click Install CSS.
After you import an application into the target Oracle Application Express instance, you must import all related files.
To import a static file:
Navigate to the Import page:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Export/Import.
On the Export/Import page, click Import and click Next.
For Specify File, select the following:
Import file - Click Browse and navigate to the file.
File Type - Select File Export.
File Character Set - Verify that File Character Set is correct.
Click Next.
Once you import a file, you have the option to install it.
To install an imported file, click Next.
Click Install Static Files.
After you import an application into the target Oracle Application Express instance, you must import all related files.
To import an Image Export file:
Navigate to the Import page:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Export/Import.
On the Export/Import page, click Import and click Next.
On Import Definition, select the following:
Import file - Click Browse and navigate to the file.
File Type - Select Image Export.
File Character Set - Verify that File Character Set is correct.
Click Next.
Once you import a file, you have the option to install it.
To install an imported file, click Next.
Click Install Image.
After you import an application into the target Oracle Application Express instance, you must import all related files.
To import a Theme Export file:
Navigate to the Import page:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Export/Import.
On the Export/Import page, click Import and click Next.
On Import Definition, select the following:
Import file - Click Browse and navigate to the file.
File Type - Select Theme Export.
File Character Set - Verify that File Character Set is correct.
Click Next.
Once you import a file, you have the option to install it.
To install an imported file, click Next.
Click Install Theme.
User Interface Defaults enables you to assign default user interface properties to a table, column, or view within a specified schema.
After you import an application into the target Oracle Application Express instance, you must import all related files.
To import User Interface Defaults:
Navigate to the Import page:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Export/Import.
On the Export/Import page, click Import and then click Next.
Select an application.
On Import Definition, select the following:
Import file - Click Browse and navigate to the file.
File Type - Select User Interface Defaults.
File Character Set - Verify that File Character Set is correct.
Click Next.
Once you import a file, you have the option to install it.
To install an imported file, click Next.
Click Install User Interface Defaults.
After you import an application and any related files into the target Oracle Application Express instance, the files are stored in the Export Repository. Next, you must install them.
You can install export files in the following ways:
After you import the export file, click the Install button and follow the on-screen instructions.
Import the export files into Application Builder and then install the files from the Export Repository.
Install the export files from SQL*Plus.
|
Tip: You can simplify the steps needed to deploy an application by creating a packaged application. See "How to Create a Packaged Application". |
This section contains the following topics:
When you import an application and any related files into a target Oracle Application Express instance, the files are stored in the Export Repository.
To access the Export Repository:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Tasks list, click Manage Export Repository.
The Export Repository appears.
|
Tip: You can also access the Export Repository by clicking Export Repository on the Tasks list on either the Application home or Application Builder home pages. |
After you import an application export into an Oracle Application Express instance, you must install it before it can become active or available in Application Builder.
To install an application export from the Export Repository:
Navigate to the Export Repository:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Tasks list, click Manage Export Repository.
The Export Repository appears.
Select an application export and click Install in the Action column.
Specify the following:
Parsing Schema - Select a schema.
This is the schema against which all of the application's SQL and PL/SQL will be parsed.
Build Status - Select one of the following:
Run Application Only
Run and Build Application
Select Run Application Only to run the application in the target instance and make it inaccessible to developers.
|
Tip: If you select Run Application Only, the only way to change this setting after you import the application is to log in to Oracle Application Express Administration Services. See "Changing Application Build Status Set During Deployment" Oracle Application Express Administration Guide. |
Install As Application - Select one of the following:
Reuse Application ID from Export File
Auto Assign New Application ID
Change Application ID
Use these options to avoid application ID conflicts. Use these options when you must have two versions of the same application in the same instance. For example, you might be migrating an application to a production instance and still need to maintain the development version.
Click Install.
After you import files into an Oracle Application Express instance, you must install them before they can become active or available in Application Builder.
To install files stored in the Export Repository:
Navigate to the Export Repository.
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Tasks list, click Manage Export Repository.
The Export Repository appears.
Select the file to be installed and click Install in the Action column.
Follow the on-screen instructions and click the Install button.
You can delete a file from the Export Repository.
To delete a file from the Export Repository:
Navigate to the Export Repository.
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Tasks list, click Manage Export Repository.
The Export Repository appears.
Select the file to be deleted and click Delete Checked.
You can also install export files from SQL*Plus. Note there are two restrictions:
The export file must originate from the same user database account as the one into which you are installing.
If the export file is an application, the application ID will be overwritten. Therefore, the target workspace must own the ID of the application being installed.
If the export file contains Supporting Object scripts, the scripts are not run when the application is installed. You can either log in to the Application Builder to install Supporting Objects, or copy the installation scripts to a standalone SQL*Plus script and run them from there.
This section contains the following topics:
You can verify that the source and target workspaces are identical by running a query in SQL Command Processor.
To verify that the source and target workspaces are identical:
Log in to the source workspace.
Click the SQL Workshop icon on the Workspace home page.
Click SQL Commands.
Enter the following in the SQL editor pane and click Run:
SELECT &WORKSPACE_ID. FROM DUAL
Note the workspace ID.
Log in to the target workspace.
Repeat steps 2 through 5 to verify the workspace IDs match.
Once you have deployed your application, loaded data, and created users, you can publish your production URL.
You can determine the URL to your application by positioning the mouse over the Run icon on the Application home page. The URL displays in the status bar at the bottom of the page.
The Run icon gets its value from the Home link attribute on the Edit Security Attributes page. This link is only referenced by this icon and by applications that do not use the Oracle Application Express Login API. Consider the following example:
http://apex.somewhere.com/pls/apex/f?p=11563:1:3397731373043366363
Where:
apex.somewhere.com is the URL of the server.
pls is the indicator to use the mod_plsql cartridge.
apex is the database access descriptor (DAD) name. The DAD describes how Oracle HTTP Server connects to the database server so that it can fulfill an HTTP request. The default value is apex.
f?p= is a prefix used by Oracle Application Express.
11563 is the application being called.
1 is the page within the application to be displayed.
3397731373043366363 is the session number.
To run this example application, you would use the URL:
http://apex.somewhere.com/pls/apex/f?p=11563:1
When users log in, they receive unique session numbers.
Build options enable you to conditionally display specific functionality within an application.
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.
This section contains the following topics:
|
See Also: See "Changing Application Build Status Set During Deployment" in Oracle Application Express Administration Guide. |
You create a build option for an application on the Build Options page.
To create a build option:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application Builder home page, click Shared Components.
Under Application, click Build Options.
To create a new build option, click Create.
Follow the on-screen instructions.
Once you create a build option, it appears on the Build Options page. You control how the Build Options page displays by making a selection from the View list. Available options include:
Icons (the default) displays each build option as a large icon. To edit a build option, click the appropriate icon.
Details displays each build option as a line in a report. Each line includes the application ID, build option name, status, and a link to the Build Option Utilization report. To edit a build option, click the appropriate name.
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.
To include or exclude a build option:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application Builder home page, click Shared Components.
Under Application, click Build Options.
Select the appropriate build option.
The Create/Edit Build Option page appears.
For Status, select either INCLUDE or EXCLUDE.
Once you create a build option, you can select it for a page, a component (report, chart, or form), a specific page control (button, item, list of value), and another shared component (breadcrumb, list, or tab). You apply build options to a page, component, page control, or shared component by navigating to the appropriate attributes page. Most attributes pages contain a Configuration section where you can select defined build options.
You can export build options or build option status on the Component Export page. Exporting build option status is an effective way to toggle build options on or off within another environment. For example, you can use this feature to deploy a production application with a hidden feature.
To accomplish this, you associate the components of the hidden feature with a build option having the status of EXCLUDE. After deployment, you can enable the hidden feature by changing the status of the build option to INCLUDE and then exporting the Build Option Status.
Once you apply the Build Options Status to the production instance, the new feature appears.
To export build options or build option status:
Navigate to the Component Export page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
From the Tasks list, click Component Export.
The Component Export page appears.
Select the build options to be exported:
Click the Components tab and select the build options to be exported.
Click Add to Export.
Select Build Option Status to be exported:
Click the Build Options Status tab and select the build options to be exported.
Click Add to Export.
Click Next.
On Components to Export:
From File Format, select how rows in the export file will be formatted:
Choose UNIX to have the resulting file contain rows delimited by line feeds.
Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.
Use the As of field to export a page as it was previously defined. Specify the number of minutes in the field provided.
This utility uses the DBMS_FLASHBACK package. Because the timestamp to System Change Number (SCN) mapping is refreshed approximately every five minutes, you may have to wait that amount of time to locate the version for which you are looking. The time undo information is retained and influenced by the startup parameter UNDO_RETENTION (the default is three hours). However, this only influences the size of the undo tablespace. While two databases may have the same UNDO_RETENTION parameter, you are able to go back further in time on a database with fewer transactions because it is not filling the undo tablespace, forcing older data to be archived.
Click Export Components.
Once you create a build option, a Utilization tab appears on the Build Options page. This report details build option utilization in the current application.
|
Note: The Utilization tab only appears on the Build Options page after you create a build option. |
To view the Build Option Utilization report:
Navigate to the Build Options page:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
On the Application Builder home page, click Shared Components.
Under Application, click Build Options.
The Build Options page appears.
On the Build Options page, click Utilization.
The Build Option Utilization report appears.
Select a build option and click Go.
This section provides important background information about using Application Builder to build dynamically rendered applications.
This section contains the following topics:
An application is a collection of database-driven Web pages linked together using tabs, buttons, or hypertext links. The pages within an application share a common session state definition and authentication method. Application Builder is the tool you use to build the pages that comprise an application.
To access Application Builder:
Log in to Oracle Application Express.
The Workspace home page appears.
To view the Application Builder home page you can either:
Click the Application Builder icon to link to the Application Builder home page.
Click the down arrow on the right side of the Application Builder icon to view a drop down menu. Then select the appropriate menu option.
|
Note: For consistency, this document uses the primary navigation path (or drill-down approach) when explaining navigation. |
The Application Builder home page displays all installed applications.
You can customize the appearance of the Application Builder home page using the navigation bar at the top of the page. Available controls include:
Application. Use the Application field to search for an application. Enter a case insensitive query for the application name or application ID and click Go. To view all applications, leave the field blank and click Go.
Group. Use the Group field to search for an application group. Select an application group and click Go. See "Creating Applications Groups".
View. Use this control to display information about the applications in your workspace. Make a selection from the list and click Go. Available options include:
Icons (the default) displays each application as a large icon identified by the application name.
Details displays each application as a line in a report. Each line includes the application ID, the application name, when the application was last updated, the page count, and who last updated the application.
By Group displays applications by application group.
Display. Determines how many applications display on the page. To change the display, make a selection from the list and click Go.
The following buttons appear to the right of the navigation bar:
Import. Click Import to import an exported application file. See "Importing Export Files"
Create. Click Create to create an application or install a demonstration application. See "Installing a Demonstration Application" and "About Creating an Application Using a Wizard".
About the Tasks List
A Tasks list displays on the right side of the Application Builder home page.
The Tasks list contains the following links:
Application Builder Defaults links to the Manage Application Builder Defaults page. See "Leveraging Application Builder Defaults" in Oracle Application Express Administration Guide.
Developer Preferences links to the Developer Preferences page. See "Configuring Developer Preferences".
User Interface Defaults links to the User Interface Defaults page. See "Managing User Interface Defaults".
Application Groups links to the Application Groups page. See "Creating Applications Groups".
Workspace Themes links to the Workspace Themes page. See "Managing Themes".
Export Repository links to the Export Repository page. See "Importing Export Files".
About the Recent List
The Recent list contains links to recently viewed applications.
Many pages in Application Builder include a navigation bar at the top of the page. You can use the controls in the navigation bar to customize the appearance of the page. Most navigation bars include a View and Display list. You can control the default display for both lists on the Developer Preferences page.
To edit developer preferences:
On the Workspace home page, click the Application Builder icon.
From the Tasks list, click Developer Preferences.
From Set View Mode, select one of the following:
Icons (the default) displays the items on the page as a large icon.
Details displays the items on the page as a line in a report.
From Report Rows, select the number items to display.
Click Apply Changes.
To view a specific application, select the application on the Application Builder home page. The Application home page appears. The application ID and the application name display at the top of the page. To link to the application definition, click application name.
The following large icons appear next:
Run Application submits the pages in the current application to the Application Express engine to render viewable HTML. See "How the Application Express Engine Renders and Processes Pages".
Supporting Objects links to the Supporting Objects page. See "How to Create a Packaged Application".
Shared Components links to a list of shared components and user interface controls that can display or be applied on every page within an application. See "Working with Shared Components".
Export/Import links you to the Export/Import Wizard. Use this wizard to import and export an entire application and related files such as cascading style sheets, images, static files, script files, themes, user interface defaults, and workspace users. "Exporting an Application and Related Files".
About the Navigation Bar and Create Page Button
A navigation bar and the Create Page button display in the center of the Application home page. You can use these controls to search for pages, alter the page view, or create a page.
The Application home page navigation bar contains the following controls:
Page. Search for a page number or name by entering a case insensitive keyword or phrase in the Page field and clicking Go. To view all pages in an application, leave the Page field blank and click Go. You control how many pages display by making a selection from the Display list.
View. By default, each page displays as a large icon. You can change the appearance of the page by making a selection from the View list and clicking Go. See "Understanding Page Display Alternatives".
Display. Determines how many pages display. To change the number of pages that appear, make a selection from the Display list and click Go.
The Create Page button displays to the right of the navigation bar. Click Create Page to launch a wizard that walks you through creating a page. See "Managing Pages in an Application".
About the Tasks List
A Tasks list displays on the right side of the Application home page.
The Tasks list contains the following links:
Delete this Application deletes the current application. See "Deleting an Application".
Copy this Application creates a copy of the current application. See "Copying an Application".
Page Groups links to the Page Groups page. Make the pages within your application easier to access by organizing them into page groups. See "Grouping Pages".
Page Locks links to the Locked Pages page. Locking pages in an application prevents conflicts during application development. See "Locking and Unlocking a Page".
User Interface Defaults link to the User Interface Defaults page. See"Managing User Interface Defaults".
Export Repository links to the Export Repository page. See "Installing Export Files".
Application Reports links to the Application Reports page. Use this page to view reports specific to your application. See "Viewing Application Reports".
Understanding Page Display Alternatives
You can control how the Application home page appears by making a selection from the View list and clicking Go. Available View modes include:
Icons
Details
by Group
by Type
Icons mode (the default) displays each page as a large icon identified by the page name. To view a page, click the icon.
Details mode displays each page as a line in a report. Each line includes the page number, the page name, when the page was last updated, the page type, who updated it, any associated group, and lock status. To view a page, click the page name. Use the Lock icon to prevent conflicts during application development. Click the Run icon to run the associated page and render viewable HTML.
By Group displays currently defined page groups. You can use page groups to organize and manage the pages within an application. See "Grouping Pages".
By Type separates pages into categories, such as Login, Report, Tabular Form, Dynamic Form, Chart, and so on. The number of pages within each page category displays within a parenthesis to the right of the type name. To view a page, click the page type and then the page.
About the Recent List
The Recent list contains links to recently viewed pages within the current application. This list only appears when viewing the Application home page in Icon mode.
The Action bar displays beneath the Utilities tab in the upper right corner of most pages in Application Builder.
This bar contains the icons discussed in the sections that follow. Note that the Run Page icon, Edit Page icon, Developer Comment icon, and Find icon display on numerous pages in Application Builder, including pages for creating and managing shared components. See "Working with Shared Components".
The Run Page icon resembles a small, light green traffic light. Click this icon to render viewable HTML of the current page. If no page is selected, clicking this icon runs the first page in the application. When you run a page, the Application Express engine dynamically renders the page based on data stored in the database. See "Running a Page or Application".
The Edit Page icon resembles a small green piece of paper and pencil. Click this icon to access the Page Definition of the current page. If no page is selected, clicking this icon displays the Page Definition of the first page in the application. See "About the Page Definition".
The Shared Components icon resembles a small mechanical gear. Click this icon to view a list of shared components and user interface controls that can display or be applied on every page within an application. See "Working with Shared Components".
The Developer Comment icon is the shape of a green balloon. Click this icon to record comments about an application, a specific page, or a group of pages. See "Adding Developer Comments".
The Find icon resembles a flashlight. Click this icon to search for items, pages, queries, tables, PL/SQL, images, and cascading style sheets (CSS) within the current application or the schemas associated with the workspace. See "Using the Find Icon".
Application attributes apply to an entire application. Once you create an application, the next logical step is to review and possibly update application attributes.
Topics in this section include:
|
See Also: "How to Create a Packaged Application" for information on using the Supporting Objects utility to create a packaged application |
You use the attributes on the Edit Definition page to control the application name and availability and to define static substitution strings. Additionally, the Edit Definition page displays defined build options, the associated theme, template defaults, and component defaults. Required values are marked with a red asterisk (*).
Topics in this section include:
To edit the application definition:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
The Shared Components page appears.
Under Application, click Definition.
The Edit Definition page appears.
|
Tip: You can also access the Edit Definition page by clicking the application name at the top of the Application home page. |
The Edit Definition page is divided into the following sections: Name, Availability, Global Notification, Substitutions, Logo, Build Options, Theme, Template Defaults, and Component Defaults. 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 following sections describe the attributes available on the Edit Definition page.
Topics in this section include:
Use Name to define basic characteristics of your application, including the application name, an optional alphanumeric alias, and a version number. Table 4-1 describes all Name attributes.
Table 4-1 Application Definition Attributes
| Attribute | Description |
|---|---|
|
Provides a short descriptive name for the application to distinguish it from other applications in your development environment. | |
|
Assigns an alternate alphanumeric application identifier. You can use this identifier in place of the application ID.For example, suppose you create an alias of
See Also: "Using f?p Syntax to Link Pages" | |
|
Includes the application's version number on a page. You can also automatically tie the version to the date of last modification using the following format masks:
If your application version uses YYYY.MM.DD, then Application Builder replaces this format mask with the date of last modification of any application attribute. | |
|
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 | |
|
Determines the virtual path the Web server uses to point to the images directory distributed with Application Builder. During installation, the virtual path is configured as When embedding an image in static text (for example, in page or region headers or footers), you can reference an image using the substitution string
<img src="#IMAGE_PREFIX#go.gif">
See Also: "IMAGE_PREFIX", "Managing Images", and "Referencing Images" | |
|
Use this field to specify a proxy server. For example, you may require a proxy server when using a region source type of URL. The URL region source embeds the results of the URL (that is, the page returned by navigating to the URL) as the region source. If you use a firewall and the target of a URL is outside the firewall relative to Application Builder, you may need to specify a proxy server. You can reference values entered into this field from PL/SQL using the PL/SQL package variable | |
|
Determines whether user activity is recorded in the Oracle Application Express activity log. When set to Yes, every page view is logged, enabling an administrator to monitor user activity for each application. Disabling logging may be advisable for high volume applications. | |
|
Controls debug mode for the current application. Available options include:
Running an application in debug mode is useful when an application is under development. However, for a production application, it is a good idea to disable debugging and thus prevent users from viewing application logic. | |
|
Specifies the schema that all SQL and PL/SQL in the application is parsed as. You may use the | |
|
Determines if exact substitutions are supported. Use exact substitutions. Non-exact substitutions is a deprecated feature. Exact substitutions use the following sytnax: &ITEM. Non-exact substitutions use the following sytnax: &ITEM | |
|
Displays the application group currently associated with this application. To select another application group, make a selection from the list. To remove an application from an existing group, select Unassigned. See Also: "Creating Applications Groups" |
Use Availability attributes to manage your application by defining an application status and build status. For example, if you select the status Restricted Access, you can specify which users have access and can run the application. Table 4-2 describes these attributes.
Table 4-2 Application Availability Attributes
| Attribute | Description |
|---|---|
|
Specifies whether the application is available or unavailable for use. Options include:
See Also: "Changing Build Status for Multiple Applications" in Oracle Application Express Administration Guide, "Changing Application Build Status Set During Deployment" in Oracle Application Express Administration Guide, and "Controlling Access to Applications, Pages, and Page Components", | |
|
Identifies the build status of the current application. Options include:
See Also: "Changing Application Build Status Set During Deployment" in Oracle Application Express Administration Guide | |
|
Use this attribute in conjunction with Status. If you set Status to Unavailable, Unavailable (Status Shown with PL/SQL), or Unavailable (Redirect to URL), the text you enter in this attribute displays. If you set Status to Available, the text you enter in this attribute does not display. | |
|
Restrict to comma separated user list (status must equal Restricted Access) |
Use this attribute in conjunction with the Status Restricted Access. If you set Status to Restricted Access, only the users listed in this attribute can run the application. To use this attribute:
|
You can use the Global Notifications attribute to communicate system status to application users. For example, you can use this attribute to notify users of scheduled downtime, or communicate other messages regarding application availability. If the page templates used in your application contain the #GLOBAL_NOTIFICATION# substitution string, the text entered here will display in that string's place.
To create a global notification:
Include the #GLOBAL_NOTIFICATION# substitution string in your page template.
Navigate to the Edit Definition page and enter a message in the Global Notifications attribute.
Click Apply Changes.
Use these fields to define static substitution strings for your application. You can use static substitution string for phrases or labels that occur in many places within an application. To create a substitution string, enter the string name in the Substitution String column and the string value in the Substitution Value column.
Defining static substitution strings centrally enables you to change text strings in multiple places in your application by making a single change to the Substitution Value defined on this page.
Use Logo attributes to define an application logo. An application logo can be text-based or image-based. To use this feature, your page template must include the #LOGO# substitution string.
To define an application logo:
For Logo Type, select one of the following:
Select Image to use an image for the application logo.
Select Text to use text for the application logo.
In Logo, enter the following:
For an image, enter the complete image name, including the filename extension. For example:
/i/oracle.gif
For text, enter the full text string. For example:
Sample Application
In Logo Attributes, enter the appropriate attributes for the logo.
Image example:
width="100" height="20" alt="Company Logo"
Text example:
style="font-family:Arial; color:#000000; font-size:18; white-space:nowrap; font-weight:bold;"
Displays existing build options. Most applications have a build option attribute. Build Options have two possible values: INCLUDE and EXCLUDE. If you specify an attribute to be included, then the Application Express engine considers it at run time. However, if you specify an attribute to be excluded, then the Application Express engine treats it as if it did not exist.
Do not specify a build option unless you plan to exclude that object from specific installations.
Displays the current theme applied to the application. Themes are collections of templates that can be used to define the layout and style of an entire application. Each theme provides a complete set of templates that accommodate every user interface pattern that may be needed in an application.
Lists the default templates for this application. To specify a default template at the application level, you can either:
Select a new theme. See "Switching the Active Theme".
Select a new default page template on the Create/Edit Theme page. See "Changing the Default Templates in a Theme".
You can also override this default by making a selection from the Page Template list on the Page Attributes page.
Table 4-3 describes template defaults for the current application.
Table 4-3 Application Template Defaults Attributes
| Attribute | Description |
|---|---|
|
Indicates the default page template to display pages. You can override this selection by making a selection from the Page Template list on the Page Attributes page. See Also: "Editing Page Attributes" | |
|
Identifies the template to be used when the Application Express engine is in printer friendly mode. When calling the Application Express engine to render a page, you have the option to specify whether the page should be displayed using the Print Mode Page Template specified. If you specify Yes, then the page displays using a printer friendly template. The Application Express engine displays all text within HTML Form Fields as text. The printer friendly template does not need to have the See Also: "Optimizing a Page for Printing" | |
|
Optional. Specifies a page template to use for errors that display on a separate page, as opposed to those that display inline. |
Displays the default templates used when running wizards. You can override these settings on the attributes page for each control or component. Table 4-4 describes component defaults for the current application.
Table 4-4 Component Defaults
| Attribute | Description |
|---|---|
|
Default calendar template used when you create a calendar. | |
|
Default label template used when you create page items. | |
|
Default report template used when you create report. | |
|
Default template used when you create a list. | |
|
Default template used when you create a breadcrumb. | |
|
Default template used when you create buttons that are template controlled. | |
|
Default template used when you create a region. | |
|
Default region template used when you create a chart. | |
|
Default region template used when you create a form. | |
|
Default region template used when you create a report. | |
|
Default region template used when you create a tabular form. | |
|
Default region template used when you create a wizard component. | |
|
Default region template used when you create a breadcrumb. | |
|
Default region template used when you create a list. |
You can provide security for your application by configuring attributes on the Edit Security Attributes page. The Security Attributes you choose apply to all pages within an application.
Topics in this section include:
To access the Edit Security Attributes page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
The Shared Components page appears.
Under Security, click Edit Security Attributes.
The Edit Security Attributes page appears.
The Edit Security Attributes page is divided into the following sections: Authentication, Authorization, Database Schema, Session State Protection, and Virtual Private Database. 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 following sections describe the attributes available on the Edit Security Attributes page.
Topics in this section include:
Authentication is the process of establishing users' identities before they can access an application. Although you define multiple authentication schemes for your application, only one scheme can be current at a time. Table 4-5 describes the attributes available under Authentication.
Table 4-5 Authentication Attributes
| Attribute | Descriptions |
|---|---|
|
Specifies a URL or procedure that should be run when you run the application. For example, Home Link could contain the relative URL used to locate the application home page. For example, You can also use this attribute to name a procedure. For example, you could create a procedure such as Note: Do not use the Home Link attribute to determine the page that displays after authentication. The page that displays after authentication is determined by other components within the application's authentication scheme. See Also: "HOME_LINK" | |
|
Replaces the substitution strings See Also: "LOGIN_URL" and "Creating an Authentication Scheme" | |
|
Identifies the Oracle schema used to connect to the database through the database access descriptor (DAD). The default value is Once a user has been identified, the Application Express engine keeps track of each user by setting the value of the built-in substitution string Note: Previous versions of Oracle Application Express used the built-in substitution string When
If the current application user ( For example, you can show a login button if the user is the public user and a logout link if the user is not a public user. Reference this value using See Also: "HOME_LINK" and "Understanding Conditional Rendering and Processing" | |
|
Click this button to define an authentication scheme. See Also: "Understanding How Authentication Works" and "Creating an Authentication Scheme" |
Authorization controls user access to specific controls or components based on user privileges. You can specify an authorization scheme for your application, by making a selection from the Authorization Scheme list. You can assign only one authorization to an entire application. However, you can assign an authorization scheme to individual pages, page controls (such as a region, a button, or an item), or a shared component (such as a menu, a list, or a tab).
To create a authorization scheme, click Define Authorization Schemes.
An authorization scheme is a binary operation that either succeeds (equals true) or fails (equals false). If it succeeds, then the component or control can be viewed. If it fails, then the component or control cannot be viewed or processed. When you attach an authorization scheme to a page and it fails, an error message displays instead of the page. However, when you attach an authorization scheme to a page control (for example, a region, a button, or an item) and it fails, no error page displays. Instead, the control either does not display or is not processed or executed.
Use Parsing Schema to specify the database scheme for the current application. Once defined, all SQL and PL/SQL commands issued by the application will be performed with the rights and privileges of the defined database schema.
Use the following attributes to reduce exposure to abandoned computers with an open Web browser by application:
Maximum Session Length in Seconds - Enter a positive integer representing how many seconds a session used by this application will exist. Leave the value NULL for the session to exist indefinitely. This session duration may be superseded by the operation of the job that runs every eight hours which deletes sessions older than 24 hours.
Session Timeout URL - Enter an optional URL to be redirected to when the Maximum Session Length in Seconds has been exceeded. If implemented in Oracle Application Express, the target page in this URL should be a public page. A common use for this page would be to inform the user of the session expiration and to present a login link or other options. If no URL is supplied, the user is redirected to the application home page.
Maximum Session Idle Time in Seconds - Enter a positive integer representing how many seconds of inactivity or idle time a session used by this application should permit. The idle time is the time between one page request and the next one. Leave the value NULL to prevent session idle time checks from being performed.
Idle Timeout URL - Enter an optional URL to be redirected to when the Maximum Session Idle Time in Seconds has been exceeded. If implemented in Oracle Application Express, the target page in this URL should be a public page. A common use for this page would be to inform the user of the session is redirected to the application home page. If no URL is supplied, the user is redirected to the application home page.
|
See Also: "Understanding Session Timeout" and "Configuring Session Timeout" in Oracle Application Express Administration Guide |
Enabling Session State Protection can prevent hackers from tampering with URLs within your application. URL tampering can adversely affect program logic, session state contents, and information privacy.
To enable or disable Session State Protection for your application, make a selection from the Session State Protection list. Setting Session State Protection to Enabled turns on session state protection controls defined at the page and item level.
To configure Session State Protection, click Manage Session State Protection.
Use this attribute to enter a PL/SQL block that sets a Virtual Private Database (VPD) context for the current database session associated with the current "show page" or "accept page" request. The block you enter here is executed at a very early point during the page request, immediately after the APP_USER value is established. The value of APP_USER (using :APP_USER or v('APP_USER')) may be used within the block. Values of other items in session state may be referenced as well, but any such items must have been established in session state before the initiation of the current page request. Consider the following example:
dbms_session.set_context('CTX_USER_QRY','USERPRIV',my_package.my_function(:APP_USER));
The previous example sets the value of USERPRIV in the context named CTX_USER_QRY to the value returned by the function my_function in package my_package. The function is passed the current value of APP_USER as an input argument. Presumably, the named context would be used in a VPD policy ( created within the application's parsing schema) to effect the generation of predicates appropriate to the authenticated user.
Virtual Private Database, also know as Fine-Grained Access Control or FGAC, is an Oracle database feature that provides an application programming interface (API) that enables developers to assign security policies to database tables and views. Using PL/SQL, developers can create security policies with stored procedures and bind the procedures to a table or view by means of a call to an RDBMS package. Such policies are based on the content of application data stored within the database, or based on context variables provided by Oracle database. In this way, VPD permits access security mechanisms to be removed from applications, and to be situated closer to particular schemas.
The code entered in this section need not pertain to VPD/FGAC; in fact, it may not be related to security at all. Any code that needs to be executed at the earliest point in a page request can be placed here. For example, to set the database session time zone for every page request:
BEGIN EXECUTE IMMEDIATE 'alter session set time_zone = ''Australia/Sydney'' '; END;
In Application Builder you can develop applications that can run concurrently in different languages. A single application can be translated to support different languages. Use the attributes on the Edit Globalization Attributes page to specify globalization options such as the primary application language.
Topics in this section include:
To access the Edit Globalization Attributes page:
On the Workspace home page, click the Application Builder icon.
Select an application.
The Application Builder home page appears.
Click Shared Components.
The Shared Components page appears.
Under Globalization, click Edit Attributes.
The Edit Globalization Attributes page appears.
The following sections describe the attributes available on the Edit Globalization Attributes page.
Identifies the language in which an application is developed. This language is the base language from which all translations are made. For example, suppose application 100 was authored in English, translated into French, and published as application 101. English would be the Application Primary Language.
All modifications to the application should be made to the primary language specified here.
Determines how Application Builder determines or derives the application language.
The application primary language can be static, derived from the Web browser language, or determined from a user preference or item. The database language setting also determines how the date is displayed and how certain information is sorted.
This option enables you to disable browser derived language support. You also have the option of having the application language derived from an application preference.
Determines the date format to be used in the application.
This date format is used to alter the NLS_DATE_FORMAT database session setting before showing or submitting any page in the application. This value can be a literal string containing a valid Oracle date format mask or an item reference using substitution syntax. If no value is specified, the default date format is derived from the database session at runtime.
Automatic CSV Encoding controls the encoding of all comma-delimited (CSV) report output in an application. The default value for Automatic CSV Encoding is No. If Automatic CSV Encoding is set to Yes, CSV report output is converted to a character set compatible with localized desktop applications. The character set for the CSV encoding is determined by the Application Language Derived From setting.
The encoding of pages in Application Builder is determined by the character set of the database access descriptor (DAD) used to access Oracle Application Express. For example, if the character set of the database access descriptor is AL32UTF8, all pages in all applications in the Oracle Application Express user interface are encoded in UTF-8.
By default, the CSV output from report regions is encoded in the same character set as the database access descriptor. However, some desktop spreadsheet applications require that the data is encoded in the client desktop operating system character set. In the case of multibyte data, the CSV output from report regions will often appear corrupted when opened by a desktop spreadsheet application. This is because the CSV output is encoded differently than what is required by the desktop application. Enabling Automatic CSV Encoding resolves this issue.
For example, if the user's language preference for an application is de, the CSV data is encoded in Western European Windows 1252, regardless of the Database Access Descriptor character set setting. If the user's language preference is zh-cn, the CSV data will be encoded in Chinese GBK.
Oracle Application Express Application Builder User's Guide describes how to use the Oracle Application Express development environment to build and deploy database-centric Web applications. Oracle Application Express turns a single Oracle database into a shared service by enabling multiple workgroups to build and access applications as if they were running in separate databases.
This preface contains these topics:
This document contains the following chapters:
| Title | Description |
|---|---|
| What's New in Oracle Application Express | Describes new features available in this release of Oracle Application Express. |
| Quick Start | Offers a quick introduction to using the Oracle Application Express. |
| Running a Demonstration Application | Describes how to run and modify the demonstration applications that install with Application Builder. |
| Application Builder Concepts | Provides basic conceptual information about Application Builder. Use Application Builder to assemble an HTML interface (or application) on top of database objects such as tables and procedures. |
| Using Application Builder | Provides important background information about using Application Builder to build dynamically rendered applications. |
| Working with Application Pages | Provides important background information about creating and managing pages within an application. |
| Building an Application | Describes how to use Application Builder to build an application and application components. |
| Adding Application Components | Describes how to use Application Builder to add pages to an application and add other components (reports, charts, or forms), page controls (buttons, items, list of values), and shared components (breadcrumbs, lists, or tabs). |
| Adding Navigation | Describes how to implement navigation in your application using different types of navigation controls, including navigation bar entries, tabs, breadcrumbs, lists, and trees. |
| Controlling Page Layout | Describes different ways you can customize your application's page layout by customizing regions, editing item attributes, and incorporating images. |
| Managing Themes and Templates | Describes different ways you can alter your application's user interface and page layout through themes and templates. |
| Managing User Interface Defaults | Describes how to use user interface defaults to assign default user interface properties to a table, column, or view. |
| Debugging an Application | Describes approaches to debugging your Application Builder application, including viewing Debug Mode, enabling SQL tracing, viewing page reports, and how to manually remove a control or a component to isolate a problem. |
| Managing Application Security | Describes how to provide security for an Application Builder application by utilizing cross-site scripting protection, session state protection, authentication, and authorization. |
| Deploying an Application | Explains how to package an application built within Application Builder. |
| Advanced Programming Techniques | Provides information about advanced programming techniques including establishing database links, using collections, running background SQL, utilizing Web services, and managing user preferences. |
| Managing Application Globalization | Explains how to translate an application built-in Application Builder. |
Oracle Application Express Application Builder User's Guide is intended for application developers who are building database-centric Web applications using Oracle Application Express. The guide describes how to use the Oracle Application Express development environment to build, debug, manage, and deploy applications.
To use this guide, you must have a general understanding of relational database concepts and an understanding of the operating system environment under which you are running Oracle Application Express.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
For more information, see these Oracle resources:
For information about Oracle error messages, see Oracle Database Error Messages. Oracle error message documentation is available only in HTML. If you have access to the Oracle Database Documentation Library, you can browse the error messages by range. Once you find the specific range, use your browser's "find in page" feature to locate the specific message. When connected to the Internet, you can search for a specific error message using the error message search feature of the Oracle online documentation.
Many books in the documentation set use the sample schemas of the seed database, which is installed by default when you install Oracle. Refer to Oracle Database Sample Schemas for information on how these schemas were created and how you can use them yourself.
For additional application examples, please visit the Oracle by Examples (OBEs) Application Express page, located on Oracle's Technology Network. The OBEs provide step-by-step examples with screenshots on how to perform various tasks within Application Express.
http://www.oracle.com/technetwork/developer-tools/apex/overview/index.html
Printed documentation is available for sale in the Oracle Store at
To download free release notes, installation documentation, white papers, or other collateral, please visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at
http://www.oracle.com/technetwork/index.html
If you already have a user name and password for OTN, then you can go directly to the documentation section of the OTN Web site at
http://www.oracle.com/technetwork/indexes/documentation/index.html
The following text conventions are used in this document:
| Convention | Meaning |
|---|---|
| boldface | Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. |
| italic | Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. |
monospace | Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter. |
This section describes how to use Application Builder to build an application and application components. It includes instructions for creating an application and adding pages as well as adding components (reports, charts, or forms), page controls (buttons, items, list of values), and shared components (breadcrumbs, lists, or tabs).
This section contains the following topics:
An application is a collection of pages that share a common session state and authentication. You create an application in Application Builder using a wizard. You delete an application from the Application home page.
Topics in this section include:
|
Tip: You can reduce the number of steps needed to create an application by configuring Application Builder Defaults. See "Leveraging Application Builder Defaults" in Oracle Application Express Administration Guide. |
When you click Create on the Application Builder home page, you must choose one of the following options:
Create Application. Creates an application. The application can be based on SQL queries or database tables. You can define blank pages or pages that contain reports, forms, tabular forms, or a report with a linked form. See "About the Create Application Wizard".
Create Application from Spreadsheet. Creates an application based on spreadsheet data. You can upload or paste spreadsheet data to create a table and then add a user interface. In the resulting application, users can create queries, add, insert, or update records, or analyze the data. See "About the Create Application from Spreadsheet Wizard".
Demonstration Application. Installs or uninstalls demonstration applications. Use demonstration applications to learn how to build applications. See "About Demonstration Applications".
The Create Application wizard enables you to create a fully functional application based on any number of tables. You can use the Create Application Wizard to create blank pages, or pages based on SQL queries or database tables. You can create SQL queries by manually typing SQL, or by using the graphical user interface of Query Builder.
Applications based on tables can consist of a simple report, a form and report, or a tabular form. When creating pages on tables, you have the option to generate analysis pages. Analysis pages extend a simple report or a report on a form to include multiple drill-down reports and charts.
At the workspace level, you have the option of setting defaults that are used for applications built in that workspace. Setting these defaults enables you to exit the wizard without paging through each step. When you exit the wizard, the application you create uses the values you specified as defaults.
|
See Also: "Building Queries with Query Builder"in Oracle Application Express SQL Workshop and Utilities Guide and "Leveraging Application Builder Defaults" in Oracle Application Express Administration Guide |
|
See Tutorials: "Building Your Application" in Oracle Database 2 Day + Oracle Application Express Developer's Guide and Oracle Application Express Advanced Tutorials |
Topics in this section include:
You can create an application based on a table, query, or drill-down query by selecting Create Application in the Create Application Wizard.
To create an application based on a table, query, or drill-down query:
On the Workspace home page, click the Application Builder icon.
Click the Create button.
For Method, select Create Application and click Next.
For Name, enter the following and click Next:
Name - Enter a name to identify the application.
Application - Enter a unique integer value to identify the application.
Create Application - Select a creation method:
Select From scratch to manually add all pages
Select Based on existing application design model to copy page definitions from a previous application model.
Note that you will still have to define all other application attributes, or you can choose to copy some attributes by choosing to copy shared components from another application (See step 7 and "About Application Models and User Interface Defaults").
Schema - Your application will obtain its privileges by parsing all SQL as a specific database schema. Identify the database schema owner.
Next, add pages to your application.
For Pages:
Select the type of page you want to add. Options include:
Blank creates a page with no built-in functionality.
Report creates a page that contains the formatted result of a SQL query. You can choose to build a report based on a table you select, or based on a custom SQL SELECT statement or a PL/SQL function returning a SQL SELECT statement that you provide.
Form creates a form to update a single row in a database table.
Tabular Form creates a form to perform update, insert, and delete operations on multiple rows in a database table.
Master Detail creates a form that displays a master row and multiple detail rows within a single HTML form. With this form, users can query, insert, update, and delete values from two tables or views.
Report and Form builds a two page report and form combination. On the first page, users select a row to update. On the second page, users can add a record or update or delete an existing record.
Action displays the currently selected page type. For each selection, the wizard prompts you for a different types of information, such as selecting a table name or report implementation.
Report pages include the Include Analysis Pages check box. Select this option and follow the wizard prompts to extend a simple report or a report on a form to include multiple drill-down reports and charts.
Click Add Page.
The page (or pages) appear at the top of the page. To delete a page, click Delete icon.
Repeat the previous steps until all pages have been added.
Click Next.
|
Tip: To exit this wizard early and utilize Application Builder Defaults, click the Create button. To configure Application Builder Defaults, see "Leveraging Application Builder Defaults" in Oracle Application Express Administration Guide. |
For Tabs, determine whether to include tabs in your application and click Next.
For Shared Components, determine whether to import shared components from another application. Shared components are common elements that can display or be applied on any page within an application.
To include shared components, select the following:
Copy Shared Components from Another Application - Select Yes.
Copy from Application - Select the application from which you want to import shared components.
Select Components to Import - Select the components to import.
Click Next.
Next, select a default authentication scheme. Authentication is the process of establishing users' identities before they can access an application. See "Establishing User Identity Through Authentication".
For Authentication Scheme, select one of the following:
Application Express - Uses the user account credentials created and maintained with the Application Express Service Administration application. These are the accounts you use to log in to the Application Express development environment. You can also create accounts in this user account repository for end users of your applications.
No Authentication - Also known as database authentication, this option enables users to access your application using the account credentials stored in the modplsql DAD definition. In most cases this results in users not having to login when accessing your application. This is the quickest way to create a "public" application.
Database Account - Requires users logging into your application to enter a database schema name (or user name) and a password in order to authenticate. This account information is managed entirely within the Oracle database.
Next, select the following globalization preferences:
Language - Select the primary language for this application.
This attribute identifies the language in which an application is developed. This language is the base language from which all translations are made.
User Language Preference Derived From - Specifies how the engine determines the application language. The application primary language can be static (that is, derived from the Web browser language) or determined from a user preference or item. The database language setting determines date display and sorting characteristics.
You can alter the Language and User Language Preference Derived From attributes later on the Edit Globalization attributes page. See "Configuring Globalization Attributes".
Date Format - Specifies the date format to be used in the application.
This date format is used to alter the NLS_DATE_FORMAT database session setting before showing or submitting any page within the application. This value can be a literal string containing a valid Oracle date format mask or an item reference via substitution syntax. If no value is specified, the default date format is derived from the database session at runtime. If supplied, this is also used as the date format for any items resulting from columns of type DATE.
Click Next.
For User Interface, select a theme and click Next.
Themes are collections of templates that can be used to define the layout and style of an entire application. See "Managing Themes".
Confirm your selections and click Create.
The Create Application Wizard is designed with the assumption that the developer may run it multiple times. To facilitate this iterative approach to application development, every time you run the wizard it saves the page definitions to an application model.
Consider the following example. You create an application by running the Create Application Wizard. After viewing the application, you realize it is not quite what you wanted. Instead of altering it, you can run the wizard again and select an application model. By selecting an existing application model when you rerun the wizard, you can quickly improve your application with minimal time and effort.
Another way to increase your productivity when creating an application is to specify user interface defaults. User interface defaults are metadata that enable you to assign default user interface properties to a table, column, or view within a specified schema.
You can increase your productivity when creating applications by leveraging application models and user interface defaults. Consider the following scenario:
Create an application based on tables or views by running the Create Application Wizard.
Run the generated application. Note any functional deficiencies.
Evaluate whether to create or edit user interface defaults.
For example, you can use user interface defaults to control how form field or report labels display. You can also utilize user interface defaults to display specific columns or have columns display in an alternate order.
Navigate to the Application home page and create an application by clicking Create.
Select Create Application.
When prompted to enter application details, specify the following:
Name - Enter a name to identify the application.
Application - Enter a unique integer value to identify the application, or accept the default.
Create Application - Select Based on existing application design model.
Select an application model.
Note the pages you previously created already appear.
Add pages, edit pages, or remove pages.
Complete the wizard.
Repeat steps 2 through 9 until the application meets your functional requirements.
You can create an application based on spreadsheet data by selecting Create from Spreadsheet in the Create Application Wizard.
To create an application from spreadsheet data:
On the Workspace home page, click the Application Builder icon.
Click the Create button.
Select Create from Spreadsheet.
For Load Method, specify how spreadsheet data will be uploaded. Select one of the following and click Next:
Upload file, comma separated (*.csv) or tab delimited. Specify the following and click Next:
Text File - Click Browse to locate the file to be uploaded.
Separator - Specify the column separator character. Use \t for tab separators.
Optionally Enclosed By - Enter a delimiter character. You can use this character to deliminate the starting and ending boundary of a data value. If you specify a delimiter character, the wizard ignores white space occurring before the starting and ending boundary of a data value. You can also use this option to enclose a data value with the specified delimiter character.
File Character Set - Choose the character set in which the text file is encoded.
Copy and paste. Copy and paste the tab delimited data you want to import.
For Table Properties, review how your table will display and click Next. Specify the table name and column names, or modify the data types. To specify whether to include a column, make a selection from the Upload list.
For User Interface Defaults:
Review the displayed Singular Name and enter a Plural Name.
(Optional) Under Column User Interface Defaults, review the displayed column labels.
Click Next.
For Summary Page:
Summary By Column - Select the columns for which data will be summarized in reports and charts and click Next.
Aggregate By Column - Select columns for which values will be aggregated in summary report and click Next.
For Application Options, specify the following:
Application Name - Enter an alphanumeric name for this application.
Create Mode:
Read and Write includes insert and update pages.
Read Only does not include insert and update pages.
Report Implementation - Choose Classic to create a SQL report or Interactive to create an interactive report.
Select a chart type.
Click Next.
For User Interface Theme, select a theme and click Next.
Themes are collections of templates that can be used to define the layout and style of an entire application. See "Managing Themes".
Confirm your selections and click Create.
|
See Also: "Building Queries with Query Builder" in Oracle Application Express SQL Workshop and Utilities Guide |
|
See Tutorial: "How to Build an Access Control Page" in Oracle Application Express Advanced Tutorials |
Oracle Application Express installs with a number of demonstration applications. Use these applications to learn more about the different types of functionality you can include in your applications.
|
See Also: "Running a Demonstration Application", "Disabling the Creation of Demonstration Applications in a New Workspace" in Oracle Application Express Administration Guide, and "Downloading Public Packaged Applications and Sample Code in Oracle Database 2 Day + Oracle Application Express Developer's Guide |
To access demonstration applications:
On the Workspace home page, click the Application Builder icon.
Click the Create button.
Select Demonstration Application.
The Demonstration Applications page appears, displaying links to the following applications:
To install a demonstration application, locate the application you want to install and click Install.
Follow the on-screen instructions.
The Application home page appears.
To run an installed demonstration application, click the Run link.
Enter the appropriate login credentials and click Login.
For Sample Application:
For User Name, enter either demo or admin
For Password, enter current workspace name in lowercase letters
For other demonstration applications, enter your workspace user name and password.
To copy an application:
On the Workspace home page, click the Application Builder icon.
Select an application.
The Application home page appears.
Click Copy this Application on the Tasks list. See "About the Tasks List".
On Copy Application:
Enter a new application ID.
Enter a new application name.
Specify whether to copy deployment attributes.
Click Next.
Click Copy Application.
You can delete an application from within Application Builder, or while editing application attributes. If you delete an application you also delete all defined components (reports, charts, or forms), page controls (buttons, items, list of values), and shared components (breadcrumbs, lists, and tabs, but not user interface defaults).
Topics in this section include:
To delete an application from Application Builder:
On the Workspace home page, click the Application Builder icon.
Select an application.
When Application Builder appears, verify the application ID and name at the top of the page.
On the Tasks list, click Delete this Application.
When prompted, click Permanently Delete Now.
To delete an application from the Edit Definition page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
The Shared Components page appears.
Under Application, click Definition.
The Edit Definition page appears.
Verify the application ID and name.
Click Delete at the top of the page.
When prompted, click Permanently Delete Now.
A page is the basic building block of an application. When you build an application in Application Builder, you create pages that contain user interface elements, such as tabs, lists, buttons, items, and regions.
Topics in this section include:
You add a page or add a component to an existing page by running the Create Page Wizard. You can access this wizard by:
Clicking Create Page on the Application home page. See "Creating a Page from the Application Home Page".
Clicking Create on the Page Definition. See "Creating a Page from the Page Definition".
Click the Create link on the Developer toolbar and then select New Page. "Creating a Page from the Developer Toolbar".
|
Note: You can also use the Create Page Wizard to add a component (that is, a report, chart, form, wizard, a calendar, or tree) to an existing page. When prompted, specify an existing page number. |
To create a page from the Application home page:
On the Workspace home page, click Application Builder.
Select an application.
The Application home page appears.
Click the Create Page button.
Select the type of page you want to create as described in the following table.
| Page Type | Description |
|---|---|
| Blank Page | Creates a blank page. |
| Multiple Blank Pages | Creates multiple blank pages. |
| Report | Formatted result of a SQL query. Available options:
See Also: "Creating Reports" and "Implementing Web Services" |
| Chart | Enables you to create three types of graphical charts: HTML, Scalable Vector Graphics (SVG), and Flash.
See Also: "Creating Charts" |
| Form | Creates a form interface with which users can update a single row or multiple rows within a table.
See Also: "Creating Forms" |
| Wizard | Create a wizard. |
| Calendar | Generates a calendar with monthly, weekly, and daily views.
See Also: "Creating Calendars" |
| Tree | Creates a a tree to graphically communicate hierarchical or multiple level data.
See Also: "Creating Trees" |
| Login Page | Creates a login page.
See Also: "Building a Login Page" |
| Access Control | Creates a page containing a access control list, enabling developers to control access to an application, individual pages, or page components.
See Also: "Controlling Access to Applications, Pages, and Page Components" |
| Page Zero | A page zero that functions as a master page. The Application Express engine renders all components you add to page zero on every page within your application. You can further control whether the Application Express engine renders a component or runs a computation, validation, or process by defining conditions.
See Also: "Displaying Components on Every Page of an Application" |
Follow the on-screen instructions.
To create a page while viewing a Page Definition:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
Click the Create button at the top of the page.
Select the type of page you want to create:
New Page
Region on this page
Page control on this page
Shared Control
Follow the on-screen instructions.
When you run the Create Page Wizard, you select a page type. Table 6-1 describes available create page options based on the type of page you select.
Table 6-1 Create Page Options
| Create Page Options | Available Selections |
|---|---|
|
New Page |
Available page types:
|
|
Region on this page |
Regions function as containers for content. Available region types:
See Also: "Understanding Regions" and "About Region Types" |
|
Page control on this page |
Page controls:
|
|
Shared control |
Shared component options:
|
To view a rendered version of your application, you run or submit it to the Application Express engine by clicking the Run or Run Application icon.
When you run an application, the Developer toolbar appears at the bottom of the page. The Developer toolbar offers a quick way to edit the current page, create a page, region, or page control, view session state, or turn edit links on and off. You can control whether the Developer toolbar displays by changing the Status attribute on the Edit Definition page.
To create a page from the Developer toolbar:
Run the application. See "Running a Page or Application".
On the Developer toolbar, click Create.
Select the type of component you want to create and click Next. Available options include:
New Page
Region on this page
Page control on this page
Shared control
Follow the on-screen instructions.
You can copy a page from the current application or from another application. During the copy process, you can also copy shared components or change mappings to shared components in the target application.
To copy a page:
Navigate to the application you want to copy to:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
Select a page.
The Page Definition appears.
Click the Copy button.
For Copy Page Option, select one of the following:
Page in this application
Page in another application
Follow the on-screen instructions.
The Application Express engine dynamically renders and processes pages based on data stored in database tables. To view a rendered version of your application, you run or submit it to the Application Express engine. As you create new pages, you can run them individually, or run an entire application. You can run an application by clicking the Run Application icon.
Topics in this section include:
The Run Application icon resembles a large traffic light and displays on the Application home page. Clicking the Run Application icon runs an entire application.
The Run Page icon resembles a small, light green traffic light and displays in the upper right corner of many pages within Application Builder. Clicking the Run Page icon runs the current page.
To run an entire application from the Application Builder home page:
On the Workspace home page, click the Application Builder icon.
From the View list, select Details and click Go.
Locate the application in the Applications list.
Click the Run icon in the far right column.
To run an entire application from the Application home page:
On the Workspace home page, click the Application Builder icon.
The Application Builder home page appears.
Select on application.
Click the Run Application icon at the top of the page.
You can control how the Application home page displays by making a selection from the View list on the navigation bar at the top of the page. Selecting Details displays each page as a line in a report. Each line includes the page number, the page name, when the page was last updated, who last updated the page, a lock icon, and a Run icon.
To run a page from the Pages list:
On the Workspace home page, click the Application Builder icon.
Select an application.
From the View list, select Details and click Go.
From the Pages list, locate the page you want to run and click the Run icon in the far right column.
You can make the pages within your application easier to access by organizing them into page groups. To use page groups, you create a group and then assign pages to the group.
Page groups do not have any function other than to help developers organize their application pages.
Topics in this section include:
The section describes different ways to view page groups.
To access the Page Groups page:
On the Workspace home page, click the Application Builder icon.
Select the application.
On the Tasks List on the right side of the page, click Page Groups.
The Page Groups page appears.
Use the Navigation bar at the top of the page to search for a page group by name or change the page display. You can change the default display by making a selection from View list. Available options include:
Icons (the default) displays each group as a large icon. To edit a group, click the appropriate icon.
Details displays each group as a line in a report. To edit a group, click the name.
To view the pages associated with a group, click Report Page Groups on the Tasks list.
|
Note: The Tasks list only appears if groups currently exist. |
To edit the group name and description, click the group name.
To view page groups from the Application home page:
On the Workspace home page, click the Application Builder icon.
On the Application Builder home page, select an application.
From the View list, select by Group and click Go.
Any defined groups appear. Pages not associated with a group are filed in the Unassigned folder.
To view the pages within a group, click the group name.
To view page groups from the Page Definition:
Navigate to the Page Definition. See "Accessing a Page Definition".
From the View list, select Groups and click Go.
Make a selection from the Tasks list on the right side of the page.
To create a page group:
On the Workspace home page, click the Application Builder icon
Select an application.
On the Tasks List on the right side of the page, click Page Groups.
On the Page Groups page, click Create.
Enter a name, a description (optional), and click Create.
When you create page group you specify a name and description.
To edit the Page Group definition:
On the Workspace home page, click the Application Builder icon
Select an application.
On the Tasks List on the right side of the page, click Page Groups.
Page Groups page appears.
Select a page group.
On the Page Group page, edit the name or description and click Apply Changes.
To move to the next Page Group definition, click the Previous (<) and Next (>) buttons and repeat the previous step.
To assign pages to a group:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Tasks List on the right side of the page, click Page Groups.
On the Tasks list, click Manage Unassigned.
The Manage Page Group Assignments page appears. Clicking a page number takes you to the Page Attributes page. Clicking the page Name links to the Page Definition.
From the New Group list, select a group to which you want to assign pages and click Go.
Select the pages to be assigned and click Assigned Checked.
To reassign a page to a page group:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Tasks List on the right side of the page, click Page Groups.
On the Tasks list, click Manage Assignments.
The Manage Page Group Assignments page appears. Clicking the page number takes you to the Page Attributes page. Clicking the page Name links to the Page Definition.
From the Group list, select a group and click Go.
From New Group, select a group to which you want to assign pages.
Select the pages to be reassigned and click Assigned Checked.
To remove a page to a page group:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Tasks List on the right side of the page, click Page Groups.
On the Tasks list, click Manage Assignments.
The Manage Page Group Assignments page appears. Clicking the page number takes you to the Page Attributes page. Clicking the page Name links to the Page Definition.
From the Group list, select a group and click Go.
Under Name, locate the Group list and select - Unassign -.
Select the page to be removed.
Click Apply Changes.
To remove a page group:
Remove all pages from the group to be deleted. See "Removing a Page from a Page Group".
Access the Page Group page. See "Accessing a Page Group Definition".
Click Delete.
A confirmation page appears.
Confirm your request.
To view pages by page group:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Tasks List on the right side of the page, click Page Groups.
On the Tasks list, click Report Page Groups.
The Pages by Page Group report appears. Clicking the page number takes you to the Page Attributes page. Clicking the Page Name links to the Page Definition.
To view a page group, make a selection from the Group list and click Go.
You can prevent conflicts during application development by locking pages in your application. By locking a page, you prevent other developers from editing it.
Topics in this section include:
A lock icon indicates whether a page is currently locked. If a page is unlocked, the icon appears as an open padlock. If the page is locked, the icon appears as a locked padlock. A lock icon appears on the Application home page and on the Page Definition.
To view the lock icon on the Application home page, select Details from the View list. A list of pages appears. The lock icon appears under the Lock column.
The lock icon also appears on the Action Bar on the Page Definition. See "About the Action Bar".
You can lock pages from the Page Locks page, the Pages list, and from a Page Definition.
To lock a page from the Page Locks Page:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Tasks List on the right side of the page, click Page Locks.
The Page Locks page appears.
Select the appropriate pages and click Lock Checked.
Enter a comment in the Comment field.
Click Lock Page(s).
To lock a page from the Details view:
On the Workspace home page, click the Application Builder icon.
Select an application.
From the View list, select Details and click Go.
In the Pages list, locate the page you want to lock and click the Lock icon.
Enter a comment in the Comment field.
Click Lock Page(s).
To lock a page from the Page Definition:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
Click the Lock icon in the Action bar. See "About the Action Bar".
Select the selected page and click Lock Checked.
Enter a comment in the Comment field.
Click Lock Page(s).
Only the developer who locked a page can unlock it. However, a developer with administrative privileges can unlock pages locked by other developers.
To unlock a page from the Page Locks page:
On the Workspace home page, click the Application Builder icon.
Select the application.
On the Tasks List on the right side of the page, click Page Locks.
The Page Locks page appears.
Select the appropriate pages.
Click UnLock Checked.
To unlock a page from the Details view:
On the Workspace home page, click the Application Builder icon.
Select an application.
From the View list, select Details and click Go.
In the Pages list, locate the page you want to unlock and click the Lock icon.
The Edit Lock Comment page appears.
Click UnLock.
To unlock pages from the Page Definition:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
Click the Lock icon in the upper right corner above Shared Components.
The Page Locks page appears.
Select the page you want to unlock and click Unlock Checked.
You can access a number of different views of Locked Pages on the Locked Pages page.
To access different views of locked pages:
On the Workspace home page, click the Application Builder icon.
Select the application.
On the Tasks List on the right side of the page, click Page Locks.
On the Tasks list, click one of the following:
Show Locked Pages displays only locked pages within the current application.
Show All Pages displays all pages within the current application.
Show Unlocked Pages displays only unlocked pages within the current application.
Administer Locks enables an administrator to unlock any pages locked by a developer.
You can delete a page from the Page Definition or while editing page attributes.
Topics in this section include:
To delete a page from the Page Definition:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
Verify the page name.
Click the Delete button at the top of the page.
Follow the on-screen instructions.
To delete a page while editing page attributes:
Navigate to the Page Definition. See "Accessing a Page Definition".
Under Page Rendering, locate the Page section.
Click the Edit page attributes icon to link to Page Attributes page. This icon resembles a small page with a pencil on top of it.
The Edit Page appears.
Verify the page number and page name.
Click Delete.
Follow the on-screen instructions.
You can add comments concerning an entire application on the Application Comments page. You could add a description of the application or track the developers involved in working on the application.
Topics in this section include:
To create an application comment:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
On the Application home page, click Shared Components.
The Shared Components page appears.
Under Application, click Comments.
The Application Comments page appears.
Enter comments in the Comments field and click Apply Changes.
To view reports specific to an application:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
The Application home page appears.
On the Tasks list, click Application Reports.
Click Shared Components and then Application Comments.
You can add developer comments to an application, a page, or a group of pages using the Developer Comment icon. The Developer Comment icon resembles a green balloon. This icon displays on the Action bar.
You can use developer comments to communicate application changes, report issues, or record developer suggestions.
This section contains the following topics:
The Developer Comment icon displays on any page in Application Builder that is related to a specific application or application page. You can add developer comments to an application, a page, or a group of pages.
To add a developer comment:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click the Developer Comment icon.
The Create Comment page displays in a separate window.
In Relevant Page(s), specify the pages to which the comment applies. To enter a comment that:
Applies to a specific page, enter the page number.
Applies to multiple pages, enter a comma-delimited list of pages. For example:
1, 2, 3
Does not apply to a page or group of pages, leave this field blank.
In Comment, enter up to 4000 characters of text.
Click Create or Create Another.
To edit a developer comment:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click the Developer Comment icon.
The Create Comment page displays in a separate window.
Click View Comments.
The View Comments page appears. See "About the Navigation Bar on the View Comments Page".
To edit a comment, click the Edit icon.
The Edit Comment page appears.
In Relevant Page(s), specify the pages to which the comment applies. To enter a comment that:
Applies to a specific page, enter the page number.
Applies to multiple pages, enter a comma-delimited list of pages. For example:
1, 2, 3
Does not apply to a page or group of pages, leave this field blank.
In Comment, enter up to 4000 characters of text.
Click Apply Changes.
A navigation bar appears at the top of the View Comments page and contains the following controls:
Page. Search for a page number. Enter a page number and click Go. To view all pages, leave the field blank and click Go.
Comment. Search for comments. Enter a case insensitive query for comment text and click Go. To view all comments, leave the field blank and click Go.
Developer. Limit the display to a specific developer. Select a developer to display and click Go.
Display. Determines how comments display. To increase or decrease the number of comments that appear, make a selection from the Display list and click Go.
You can delete developer comments on the Edit Comment page or on the Manage Comments page.
Topics in this section include:
To delete a developer comment:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click the Developer Comment icon.
The Create Comment page displays in a separate window.
Click View Comments.
Locate the comment to be deleted. See "About the Navigation Bar on the View Comments Page".
Click the Edit icon.
The Edit Comment page appears.
Click Delete.
To delete multiple developer comments:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click the Developer Comment icon.
The Create Comment page displays in a separate window.
Click Manage Comments.
Select one of the following actions:
Delete all comments
Delete comments created by a developer
Delete comments by date
Follow the on-screen instructions.
You can also view, edit, and manage developer comments from the Developer Comments report.
Topics in this section include:
To access the Developer Comments report:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Application Reports on the Tasks list.
Click Shared Components
Under Application Reports, click Developer Comments.
The Developer Comments report appears.
A navigation bar appears at the top of the page and contains the following controls:
Page. Search for a page number. Enter a page number and click Go. To view all pages, leave the field blank and click Go.
Comment. Search for comments. Enter a case insensitive query of comment text and click Go. To view all, leave the field blank and click Go.
Developer. Limit the display to a specific developer. Select a developer to display and click Go.
Date. Limit the display to a specific date. Select a date and click Go.
Display. Determine how comments display. To increase or decrease the number of comments that appear, make a selection from the Display list and click Go.
To edit a comment from the Developer Comments report:
Navigate to the Developer Comments report. See "Accessing the Developer Comments Report".
The Developer Comments report appears.
Locate the comment to be edited.
Click the Edit icon.
The Edit Comment page displays in a separate window.
In Relevant Page(s), specify the pages to which the comment applies. To enter a comment that:
Applies to a specific page, enter the page number.
Applies to multiple pages, enter a comma-delimited list of pages, for example:
1, 2, 3
Does not apply to a page or group of pages, leave this field blank.
In Comment, enter up to 4000 characters of text.
Click Apply Changes.
To delete a comment from the Developer Comments report:
Navigate to the Developer Comments report. See "Accessing the Developer Comments Report".
The Developer Comments report appears.
Locate the comment to be deleted.
Click the Edit icon.
The Edit Comment page displays in a separate window.
Click Delete.
To delete multiple comments from the Developer Comments report:
Navigate to the Developer Comments report. See "Accessing the Developer Comments Report".
The Developer Comments report appears.
Locate the comment to be deleted.
Click the Edit icon.
The Edit Comment page displays in a separate window.
Click Manage Comments.
Select one of the following actions:
Delete all comments
Delete comments created by a developer
Delete comments by date
Follow the on-screen instructions.
Click Apply Changes.
You can download the Developer Comments report as a comma-delimited file (.csv) file by clicking the Export link.
To download the Developer Comments report:
Navigate to the Developer Comments report. See "Accessing the Developer Comments Report".
The Developer Comments report appears.
Click the Export link at the bottom of the page.
Follow the on-screen instructions.
You can organize your applications by assigning them to application groups. To use application groups, create a group by clicking the Create button and then assign applications to it.
Topics in this section include:
The section describes different ways to view application groups.
To access the Application Group page:
On the Workspace home page, click the Application Builder icon.
On the Tasks List on the right side of the page, click Application Groups.
The Application Group page appears.
Use the Navigation bar at the top of the page to search for a page group by name or change the page display. You can change the default display by making a selection from View list. Available options include:
Icons (the default) displays each group as a large icon. To edit a group, click the appropriate icon.
Details displays each group as a line in a report. To edit a group, click the name.
To view the applications associated with a gr oup, you click the group name.
|
Note: The Tasks list only appears if groups currently exist. |
To view page groups from the Application Builder home page:
On the Workspace home page, click the Application Builder icon.
From the View list, select By Group and click Go.
Any defined groups appear.
To view or edit a page group, click the group name.
To create an application group:
On the Workspace home page, click the Application Builder icon
On the Tasks List on the right side of the page, click Application Groups.
On the Application Group page, click Create.
Enter a name, a description (optional), and click Create.
When you create page group you specify a name and description.
To edit an application group definition:
On the Workspace home page, click the Application Builder icon
On the Tasks List on the right side of the page, click Application Groups.
Application Group page appears.
Select an application group.
On the Application Group page, edit the name or description and click Apply Changes.
To assign applications to a group:
On the Workspace home page, click the Application Builder icon.
On the Tasks List on the right side of the page, click Application Groups.
On the Tasks list, click Manage Unassigned.
The Manage Application Group Assignments page appears.
From the New Group list, select a group.
Select the applications to be assigned and click Assigned Checked.
|
Tip: You can also assign an application to an application group by editing the application definition. Select the group from the Application Group list. See "Configuring the Application Definition". |
To remove an application from an application group:
On the Workspace home page, click the Application Builder icon.
On the Tasks List on the right side of the page, click Application Groups.
On the Tasks list, click Manage Unassigned.
The Manage Application Group Assignments page appears.
From the New Group list, select Unassign.
Select the pages to be unassigned and click Assigned Checked.
|
Tip: You can also remove an application from an application group by editing the application definition. Select Unassigned from the Application Group list. See "Configuring the Application Definition". |
To remove an application group:
On the Workspace home page, click the Application Builder icon.
On the Tasks List on the right side of the page, click Application Groups.
Assign all applications in the group to Unassign. See "Removing an Application from an Application Group".
Return to the Application Groups page.
Select the application group to be deleted.
On the Application Group page, click Delete.
A confirmation page appears.
Confirm your request.
Application Builder includes over 100 reports that provide a comprehensive view of your application from various perspectives. You can use application reports to achieve consistency among shared components and page components within your application. For example, you can view details about buttons used on all pages within your application. Additionally, many reports are updatable so you can standardize components, such as item and region labels, without navigating to a specific page.
Topics in this section include:
To view reports specific to an application:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
The Application home page appears.
On the Tasks list, click Application Reports.
Select a type of report to view:
Shared Components. See "Shared Components Reports".
Page Components. See "Page Components Reports".
Activity. "Activity Reports".
Cross Application. "Cross Application Reports".
Shared Components reports offer information on common elements that can display on every page within an application. Reports are grouped by the following categories: including Application, Logic, Security, Globalization, Conditional Components, Navigation, User Interface, and Files. Report examples include Developer Comments, Database Object Dependencies, Application Items, Application Computations, Authentication Schemes, Breadcrumb Entries, and Shortcuts.
The Database Object Dependencies report identifies database objects referenced by the current application. Review this report to determine what objects to move when deploying an application.
To view the Database Object Dependencies report:
Navigate to the appropriate application.
From the Workspace home page, click the Application Builder icon.
Select an application.
On the Tasks list, click Application Reports.
Click Shared Components.
Under Application, click Database Object Dependencies.
Click Compute Dependencies.
To view the components that reference a specific database object, select the Reference Count number.
Page Components reports offer detailed information on controls and logic that execute when a page is rendered (for example, branches, buttons, computations, items, and regions).
Use the Search Region Source report to search through all region source in your application.
To view the Search Region Source report:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
On the Tasks list, click Application Reports.
Click Page Components.
Under Regions, click Search Source.
To view the Page Definition for a region, select the page number.
To view region attributes for a region, select the region name.
Activity reports offer details about developer activity within the current application. Available reports are grouped into the following categories: Page Views, Caching, Developer Activity, and Sessions.
|
Tip: You can also access the Activity page by clicking the Activity link on the Developer toolbar. See "About the Developer Toolbar". |
Cross Application reports offer information that apply to multiple applications. Available reports include Application Attributes, Application Comments, Build Options, Build Status and Application Status, Page Component Counts, Security Profiles, Authentication Schemes, and Template Defaults by Application.
Use the Application Comparison report to compare two applications.
To view the Application Comparison report:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
On the Tasks list, click Application Reports.
Click Cross Application.
The Application Comparison page appears.
In the navigation bar, specify the following:
Application 1 - Select the first application to compare.
Application 2 - Select the second application to compare.
Component - Select the components to include in the report.
Page - Identify a specific page number to compare.
Show - Select the number of differences to display on each page.
Click Go.
To view only differences, select Show Differences Only and click Go.
To view details, select Show Details and click Go.
An item is part of an HTML form. An item can be a text field, text area, password, select list, check box, and so on. Item attributes affect the display of items on a page. For example, these attributes can impact where a label displays, how large an item is, and if the item will display next to or below the previous item.
Topics in this section include:
There are two types of items: page items and application items. Page items are placed on a page and have associated user interface properties, such as Display As, Label and Label Template. Examples of page-level items include a check box, date picker, display as text, file browse field, popup list of values, select list, or a text area. Application items are not associated with a page and therefore have no user interface properties. You can use an application item as a global variable.
You create and edit page-level items on the Page Definition. The Items section appears in the Page Rendering area.
You can temporarily hide all other subsections by clicking the Items icon. To restore the view, click Show All. The Show All icon resembles an inverted triangle.
The following icons display next to the section title:
Edit All. The Edit All icon resembles a small grid with a pencil on top of it. Use this icon to edit all items at once. See "Using the Edit All Icon to Edit Multiple Items".
Copy. The Copy icon resembles two small overlapping pages. Use this icon to make a copy of an existing item.
Create. The Create icon resembles a plus (+) sign overlapping a small page. Click this icon to create an item.
Items are organized by region. To edit an item, click the item name.
You can quickly change the appearance of a page by clicking the Drag and drop icon to access the Drag and Drop Layout page. The Drag and drop icon resembles a green rectangle and displays to the right of the Reorder Region Items icon.
You can use the Drag and Drop Layout page to interactively reorder items within a given region, change select item attributes, create items, or delete existing items. See "Using the Drag and Drop Layout Page".
You can quickly edit the label and position of items in a region by clicking the Reorder Region Items icon on the Page Definition. This icon resembles a light green down or up arrow.
You can create page-level items by running the Create Item Wizard.
Topics in this section include:
You create a page-level item by running the Create Item Wizard from the Page Definition.
To create a page-level item:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
If necessary, create an HTML region. See "Understanding Regions".
Under Items, click the Create icon.
Select an item type. See "About Item Types".
Follow the on-screen instructions.
To learn more about a specific field, click the field label.
When help is available, the item label changes to red when you pass your cursor over it, and the cursor changes to an arrow and question mark. See "About Field-Level Help".
When specifying an item name, remember the following rules. Item names must:
Be unique within an application
Not have quotation marks
Begin with a letter or a number, and subsequent characters can be letters, numbers, or underscore characters
Be case-insensitive
Should not exceed 30 characters
Cannot contain letters outside the base ASCII character set
When you create an item, you specify an item type. Once you create an item, these types appear on the Display As list on the Edit Page Item page. Table 6-2 describes available item types.
Table 6-2 Available Item Types
| Item Type | Description |
|---|---|
|
Displayed using a list of values. A list of values is required for items displayed as check boxes. The value corresponding to a checked box is returned in a single colon-delimited string. The following example demonstrates how to create a single check box that returns SELECT NULL display_text, 'YES' return_value FROM DUAL; This example includes the additional text Click to select. SELECT 'Click to select' display_text, 'YES' return_value FROM DUAL; See Also: "APEX_UTIL" in Oracle Application Express API Reference for information about breaking up returned values | |
|
Displays a text field with a Calendar icon next to it. When clicked, this icon displays a small calendar where the user can select a date and a time (optional). If the format you need is not included in the Display As list, select Date Picker (use application format mask) or Date Picker (use item format mask). The latter uses the value from the Format Mask field in the Source section of the Edit Page Item page. | |
|
Available Display As Text subtypes include:
| |
|
Displays a text field with a Browse... button. The Browse button enables the user to locate a file on a local file system and upload it. Oracle Application Express provides a table for these files to be uploaded to and an API to retrieve the files. See Also: "Securing File Uploads" | |
|
Renders an HTML hidden form element. Session state can be assigned and referenced just like a text field. | |
|
Renders an HTML hidden form element. Session state can be assigned and referenced just like a text field. For maximum security use Hidden and Protected instead of Hidden unless your page has client-side behavior, for example, JavaScript that alters the item value after the page is rendered by Oracle Application Express. | |
|
Based on a list of values. This item enables you to manage a list of items by selecting and adding to a list. The list of values display as a popup. | |
|
Renders as a multiselect HTML form element. When submitted, selected values are returned in a single colon-delimited string. You can break up the values using the See Also: "Working with a Multiple Select List Item" and "APEX_UTIL" in Oracle Application Express API Reference | |
|
Renders as an HTML password form element. Available password types include:
The Password and Password (submits when Enter pressed) save the password in a database table when the page is submitted. Use these password item types only when the password is needed in session state for use by other pages during the session. Password (does not save state) and Password (submits when Enter pressed, does not save state) do not save the password in a database table. Use these password item types when the submitted password value is used only by after-submit page processing on the same page and is never needed again during the session. If you must reference and retrieve the value of a password in your application then you set the Store value encrypted in session state attribute to Yes. To learn more, see "About Session State and Security". | |
|
Renders as a text field with an icon. When the user clicks the icon, a popup window appears with one of these, depending on the popup selection you make:
With the exception of the color picker, you control popup lists of values through templates. You can only specify one popup list of values (LOV) template for each application. A popup LOV is a good choice for lists of values that are too large to return on a single page. There are two types of Popup LOVs: one that fetches a set of rows when the window pops up and one that does not. Available popup LOVs include:
Popup LOVs must be based on a query that selects two columns with different column aliases. For example: SELECT ename name, empno id FROM emp If one of the columns is an expression, remember to use an alias. For example: SELECT ename||' '||job display_value, empno FROM emp | |
|
Renders as an HTML radio group form element, based on a list of values. Choose Radiogroup with Submit to have the page submitted when the radio button is selected. The following example displays employee names ( SELECT ename, empno FROM emp | |
|
Displays using a list of values. A list of values is required for items displayed as a select list. Select lists are rendered using the HTML form element The following example would return employee names ( SELECT ename display_text, empno return_value FROM emp Oracle Application Express provides additional enhancements to a standard HTML select list:
Note: Long select lists can cause errors. If you have a long select list that generates an error, try using a Popup List of Values instead. | |
|
Renders as a multiple select list that includes two boxes containing lists. The left list displays a source list of values. Users use the shuttle control icons and buttons to select list items and move them from the left (source) list to the right (destination) list. Each shuttle has five controls:
The right destination list includes the sort controls Move to top, Move up, Move down, and Move to bottom. Note: In order to create this item type, you must define a list of values. See "Creating a Static List of Values", "Creating Lists of Values", and "Working with a Multiple Select List Item". | |
|
Displays as an HTML text field containing a maximum of 30,000 bytes of text. You control the maximum length and display width by editing the Height and Width item attribute. Available Text display options include:
| |
|
Renders as an HTML text area. There is no maximum length for an item displayed as a text area. You control the height and width by editing the Height and Width item attribute. Additional available Text Area Display As options include:
| |
|
Forces the close of an HTML table using the Note that a Stop and Start Table item only displays its label. You can prevent the label from displaying at all by setting it to null. To do this, you simply remove the default label. |
To create multiple items simultaneously:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
If necessary, create an HTML region. See "Understanding Regions".
Under Items, click the Create icon.
The Create Item wizard appears.
At the bottom of the page, click the Create multiple Items Using Tabular Form link.
On the Create Multiple Items page, specify the following:
Create Item(s) in Region - Select the region to contain the items.
Item Template - Select an item template.
For each item, enter the Sequence, Name, Label, Type and specify whether the item should be cached.
Click Create Multiple Items.
To create multiple items using the Drag and Drop Layout page:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
If necessary, create an HTML region. See "Understanding Regions".
Under Items, click the Create icon.
The Create Item wizard appears.
At the bottom of the page, click the Create multiple Items Using Drag and Drop Layout link.
The Drag and Drop Layout page appears.
Select an item from the palette on the left side of the page and drag it to the appropriate position on the page.
Edit the item attributes at the of the page.
Display Name - Enter an item name. Use this name retrieve the value of the item. Item names longer than 30 characters cannot be referenced using bind variable syntax.
Label - Enter the label for this item. You may include HTML, JavaScript, and shortcuts. You can also use the substitution string #CURRENT_ITEM_NAME# to obtain the name of the item associated with this label.
Display Type - Select a display type (if applicable). See "About Item Types".
To edit an existing item, edit the Item Name and Label fields, or select a new Display Type at the top of the page.
Click Next.
Optionally, edit the each item's Name and Label.
Click Apply Changes.
One way to create a static list of values is to edit an item's List of Values definition. Note that this type of list of values is not reusable. As a best practice, create a list of values as a shared component whenever possible.
To create a static list of values:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
Under Items, select the item name.
The Edit Page Item page appears.
Under Name, specify how the item will be rendered. Make a selection from the Display As list.
Under List of Values, create a static list of values:
From Named LOV, select Select Named LOV.
In List of values definition, enter a definition using the following syntax:
STATIC[2]:Display Value[;Return Value],Display Value[;Return Value]
Where:
The first keyword may be STATIC or STATIC2.
STATIC results in the values being sorted alphabetically by display value. STATIC2 results in the values being displayed in the order they are entered in the list.
A semicolon separates the display value from the return value in each entry.
Return Value is optional. If a Return Value is not included, the return value is the same as the display value.
To learn more, see item Help. To view help for a specific item on a page, click the item label.
When help is available, the item label changes to red when you pass your cursor over it and the cursor changes to an arrow and question mark. See "About Field-Level Help".
Click Apply Changes.
The examples that follow demonstrate syntax for three different static LOVs.
In this example, the list of values has four values (Cow, Dog, Cat, and Lion) that display in alphabetical order. The return value of each entry equals the display value.
STATIC:Cow,Dog,Cat,Lion
In this example, the list of values has ten values that display in the order listed in the definition. The return value of each entry equals the display value.
STATIC2:10,15,20,25,50,100,200,500,1000,10000
You can edit page-level items by editing page item attributes or using the Edit All or Reorder Items icons.
Topics in this section include:
Once you create a page item, you can edit it on the Edit Page Item page.
To edit page item attributes:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
Under Items, select the item name.
The Edit Page Item page appears.
To learn more about a specific attribute on a page, click the attribute label.
When help is available, the item label changes to red when you pass your cursor over it, and the cursor changes to an arrow and question mark. See "About Field-Level Help".
Click Apply Changes.
The Edit Page Item page is divided into the following sections: Name, Displayed, Label, Element, Source, Default, List of Values, Security, Conditions, Read Only, Help Text, Configuration, and Comments.
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.
You can edit multiple items at once by clicking the Edit All icon on the Page Definition. The Edit All icon resembles a small grid with a pencil on top of it.
Clicking the Edit All icon displays a series of pages that enable you to edit multiple items simultaneously or view a history of recent changes.
Topics in this section include:
Item attributes control how items display on a page. You can use the Page Items page to edit the sequence, field label, template, region, and overall position for all items on a page.
A Navigation bar displays at the top of the page. Use the Page field to navigate to another page. To limit the display to just items in a specific region, make a selection from Show Regions list.
The Page Items page displays items in an editable report. Table 6-3 describes each editable attribute.
Table 6-3 Editable Attributes on Page Items
| Attribute | Description |
|---|---|
|
Sequence |
Specify the display sequence for this component. The sequence determines the order of evaluation. |
|
Prompt |
Enter the label for this HTML form element. You may include HTML, JavaScript, and shortcuts. You can also use the substitution string #CURRENT_ITEM_NAME# to obtain the name of the item associated with this label. |
|
Field Template |
Determines the label template. Label templates enable you to define the user interface attributes in a central place and share that definition among many labels. |
|
Region |
Defines the region in which the item displays. All items must be in a region. |
|
New Line |
Determines whether this item displays on the same line as the previous item or whether it displays on the next line. Items are laid out in an HTML table. Select Yes to have an item display as the first field in a new row in the table. |
|
Width |
Specifies the length (in characters) of the form element that displays for this item. |
|
Height |
Specifies the height (in lines) for text areas and multi select lists. |
|
Column Span |
Items are laid out in HTML tables. This property defines the value to be used for the |
|
Row Span |
Items are laid out in HTML tables. The attribute determines the value to be used for the |
Edit the appropriate attributes and click Apply Changes.
Use the Item Help page to edit item help for all items on a page. You can avoid repeating the same Help text in multiple locations by subscribing to another item.
To edit item Help:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
Under Items, click the Edit All icon.
Click Item Help.
The Item Help page appears.
Use the Navigation bar at the top of the page to narrow or broaden the display. Available options include:
Page - Select or enter a new number and click Go.
Search - Enter a case insensitive query and click Go.
Show - Select whether to display All, Subscribed, or Unsubscribed Help text.
All Pages - Select to run the search query on all pages in the application.
Current Page - Select to restrict the search query to the current page.
You can also use the arrows in the Navigation bar to scroll through the application pages.
To subscribe to an existing Help item, make a selection from Subscribed To.
To edit help for a specific item, click the item name.
On the Edit Help page:
Reference Master Item Help From - (Optional) Select a existing item Help topic to subscribe to.
Help Text - Enter or edit the Help text for this item.
Click Apply Changes.
Click Apply Changes.
Use the Reassign Region Items page to assign items to a new region.
To Reassign Region Items page:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
Under Items, click the Edit All icon.
Click Reassign Region Items.
The Reassign Region Items page appears.
Use the Navigation bar at the top of the page to narrow or broaden the display. Available options include:
Page - Select or enter a new number and click Go.
Show Regions - Select a region to display and click Go.
To reassign an item to another region:
Select the items to reassign.
From Assign to Region, select a new region.
Click Reassign Region Items.
Use the Delete Multiple Items page to delete multiple items at once.
To delete multiple items:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
Under Items, click the Edit All icon.
Click Delete Multiple Items.
The Delete Multiple Items page appears.
Use the Navigation bar at the top of the page to narrow or broaden the display. Available options include:
Page - Select or enter a new number and click Go.
Show Regions - Select a region to display and click Go.
Forward (>) and Next (<) buttons - Display the previous and next page.
To reassign an item to another region:
Select the items to reassign.
From Assign to Region, select a new region.
Click Reassign Region Items.
You can quickly edit the label and position of items in a region by clicking the Reorder Region Items icon on the Page Definition. This icon resembles a light green down or up arrow.
To use the Reorder Region Items icon:
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
Under Items, click the Reorder Region Items icon.
The Reorder Region Items page appears with items laid out in tables. You can edit the position of an item by selecting values for New Line, New Field, Column Span, and Label Alignment attributes. Note that a graphical representation of how the items display appears at the bottom of the page.
To edit an item label, enter a new title in the Label field.
To change the position of an item, edit the following attributes:
New Line. Determines if the item displays on the same line as the previous item, or displays on the next line. Select Yes to have an item display as the first field in a new row in the table.
New Field. Determines if the item displays in the next column or in the same column as the previous item. Select Yes to have the label and value for the item display in a new HTML table cell. Use this attribute in combination with the New Line and Span attributes to control layout.
Column Span. Defines the value to be used for the COLSPAN attribute in the table cell. The COLSPAN attribute defines the number of columns that it spans across the table.
To change label alignment, make a selection from the Label Alignment list.
To change the order in which items display, click the up and down arrows in the far right column. Clicking the arrow moves the item one row up or down.
Note that the order you specify here translates to sequence number in the Sequence attribute on the Edit Page Item page. See "Editing Page Item Attributes".
Click Apply Changes.
|
Tip: You can also use the Drag and Drop Layout feature to reorder items. See "Using the Drag and Drop Layout Page". |
|
Note: To change the region in which an item resides, you must edit the item attributes. See "Editing Page Item Attributes". |
You can use the Drag and Drop Layout page to interactively reorder items within a given region, change select item attributes, create items, or delete existing items.
Topics in this section include:
You access the Drag and Drop Layout page by either:
Clicking the Drag and drop icon on the Page Definition. See "About the Drag and Drop Icon".
Clicking the Reorder Regions Items icon and selecting the Drag and Drop Layout tab. See "Using the Reorder Buttons Icon".
The Drag and Drop Layout page is divided into two sections: Item palette and Layout region.
The Item palette displays on the left side of the page. You add items by clicking an item type on the palette and dragging it to the correct position in the Layout region. Note that when you position the cursor over an item type, a tooltip appears.
Use the right side of the page (or Layout region) to position items. To move an item vertically, click the Add Row button to insert an empty row. Then drag and drop the item into the empty row.
To create a new item on the Drag and Drop Layout page:
Navigate to the Drag and Drop Layout page. See "Accessing the Drag and Drop Layout Page".
Click an item type in the Item palette on the left side of the page and drag it to the appropriate location in the Layout region.
Note that when you position the cursor over an item type, a tooltip appears.
You can reposition the item:
To move an item horizontally, select the item and drag it to the appropriate position on the page.
To insert an existing or new item between two existing rows, click the Add Row button and drag it between the existing rows. This creates an empty row where you can then move the item.
Edit the item attributes at the of the page.
Display Name - Enter an item name. Use this name to retrieve the value of the item. Item names longer than 30 characters cannot be referenced using bind variable syntax.
Label - Enter the label for this item. You may include HTML, JavaScript, and shortcuts. You can also use the substitution string #CURRENT_ITEM_NAME# to obtain the name of the item associated with this label.
Display Type - Select a display type (if applicable). Note that the select list is restricted to options corresponding to the type of item you are creating. See "About Item Types".
Click Next.
Optionally, edit the each item's Name and Label.
Click Apply Changes.
To edit an existing item on the Drag and Drop Layout page:
Navigate to the Drag and Drop Layout page. See "Accessing the Drag and Drop Layout Page".
To reposition the item:
To move an item horizontally, select the item and drag it to the appropriate position on the page.
To insert an existing or new item between two existing rows, click the Add Row button and drag it between the existing rows. This creates an empty row where you can then move the item.
If required, select an item and edit its attributes at the of the page.
Display Name - Enter an item name. Use this name retrieve the value of the item. Item names longer than 30 characters cannot be referenced using bind variable syntax.
Label - Enter the label for this item. You may include HTML, JavaScript, and shortcuts. You can also use the substitution string #CURRENT_ITEM_NAME# to obtain the name of the item associated with this label.
Display Type - Select a display type (if applicable). Note that the select list is restricted to options corresponding to the type of item you are creating. See "About Item Types". See "About Item Types".
Click Next.
Optionally, edit the each item's Name and Label.
Click Apply Changes.
|
Note: To change the region in which an item resides, you must edit the item attributes. See "Editing Page Item Attributes". |
To delete an item, click it and drag it to the Recycle box at the bottom of the page. If you delete an existing item, it appears in the Recycle box and can be retrieved until you click Apply Changes on the next page. Note that if you drop a new item you have just created in the Recycle box, it instantly disappears and cannot be retrieved.
You can reference item values stored in session state in regions, computations, processes, validation, and branches. Table 6-4 describes the supported syntax for referencing item values.
Table 6-4 Syntax for Referencing Item Values
| Type | Syntax | Description |
|---|---|---|
|
SQL |
|
Standard bind variable syntax for items whose names are no longer than 30 bytes. Use this syntax for references within a SQL query and within PL/SQL. |
|
PL/SQL |
|
PL/SQL syntax referencing the item value using the See Also: Oracle Application Express API Reference |
|
PL/SQL |
|
Standard PL/SQL syntax referencing the numeric item value using the See Also: Oracle Application Express API Reference |
|
Static Text |
|
Static text. |
|
Static Text (exact) |
|
Static text. Exact Substitution. |
You can set the value of an item in your application using any of the following methods:
For page-level items, use the Source Attribute to set the item value.
From the Page Definition, select the item name to view the Edit Page Item page. Scroll down to Source and edit the appropriate fields.
You can also set the value of an item in any region based on PL/SQL or a process using the following syntax:
BEGIN :MY_ITEM := 'new value'; END;
Pass the value on a URL reference using f?p syntax. For example:
f?p=100:101:10636547268728380919::NO::MY_ITEM:ABC
Set the value using a computation. Computations are designed to set item values. For example:
TO_CHAR(SYSDATE,'Day DD Month, YYYY');
Use the PL/SQL API to set an item value within a PL/SQL context. For example:
APEX_UTIL.SET_SESSION_STATE('MY_ITEM',SYSDATE);
You can choose to have an item display conditionally or as read-only by editing attributes on the Edit Pages Item page.
To display a conditional or read-only item:
Create the item. See "Creating Page-Level Items".
Navigate to the appropriate Page Definition. See "Accessing a Page Definition".
Under Items, select the item name.
The Edit Page Item page appears.
To display an item conditionally:
Scroll down to Conditions.
Make a selection from the Condition Type list.
Enter an expression in the fields provided.
To make an item read-only:
Scroll down to Read Only Display Settings.
Make a selection from the Read Only Condition Type list.
Enter an expression in the fields provided.
Click Apply Changes.
A multiple select item renders as a multiple select list form element which can be either a Multiselect List or Shuttle item type. When submitted, selected values are returned in a single colon-delimited string. You can handle values in this format in two ways:
Using the INSTR function
Using the APEX_UTIL.STRING_TO_TABLE function
Suppose you had a report on the EMP and DEPT tables that is limited by the departments selected from a Department multiple select list. First, you create the multiple select item, P1_DEPTNO, using the following query:
SELECT dname, deptno FROM dept
Second, you return only those employees within the selected departments as follows:
SELECT ename, job, sal, comm, dname
FROM emp e, dept d
WHERE d.deptno = e.deptno
AND instr(':'||:P1_DEPTNO||':',':'||e.deptno||':') > 0
Next, assume you want to programmatically step through the values selected in the multiple select item, P1_DEPTNO. To accomplish this, you would convert the colon-delimited string into a PL/SQL array using the APEX_UTIL.STRING_TO_TABLE function. The following example demonstrates how to insert the selected departments into an audit table containing the date of the query.
DECLARE
l_selected APEX_APPLICATION_GLOBAL.VC_ARR2;
BEGIN
--
-- Convert the colon separated string of values into
-- a PL/SQL array
l_selected := APEX_UTIL.STRING_TO_TABLE(:P1_DEPTNO);
--
-- Loop over array to insert department numbers and sysdate
--
FOR i IN 1..l_selected.count
LOOP
INSERT INTO report_audit_table (report_date, selected_department)
VALUES (sysdate, l_selected(i));
END LOOP;
END;
Application-level items do not display, but are used as global variables to the application. You can use an application item as a global variable.
Topics in this section include:
To create an application-level item:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
When Application Builder appears, click Shared Components.
Under Logic, select Application Items.
The Application Items page appears.
To create an application item, click Create.
Follow the on-screen instructions.
Once you create a application item, it appears on the Application Items page. You control how the Application Items page displays by making a selection from the View list. Available options include:
Icons (the default) displays each application item as a large icon. To edit an application item, click the appropriate icon.
Details displays each application item as a line in a report. To edit an application item, click the name.
You can view a history of changes to application items by clicking History at the top of the Application Items page.
Once you create an application-level item, you can edit it on the Create/Edit Application Item page.
To edit application-level item attributes:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
When Application Builder appears, click Shared Components.
Under Logic, select Application Items.
The Application Items page appears.
Select an application item.
The Create/Edit Application Item page appears.
To learn more about a specific item on a page, click the item label.
When Help is available, the item label changes to red when you pass your cursor over it and the cursor changes to an arrow and question mark. See "About Field-Level Help".
Click Apply Changes.
The Create/Edit Application Item page is divided into the following sections: Name, Security, Configuration, and Comments.
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.
This section describes how to implement security best practices for Oracle Application Express. Administrators are primarily responsible for ensuring the security of the Oracle Application Express installation, while developers are responsible for building secure applications.
This section contains the following topics:
This section describes security best practices for Oracle Application Express administrators.
Topics in this section include:
Security Considerations When Using the Embedded PL/SQL Gateway
About Configuring Oracle HTTP Server with mod_plsql for Oracle Application Express
Advantages of the Oracle Application Express Runtime Environment
Enabling Indexing of Online Help in Oracle Database 11g Release 2 and Higher
The embedded PL/SQL gateway runs in the database as part of the XML DB HTTP Protocol Listener. The XML DB HTTP Protocol Listener and embedded PL/SQL gateway provides the equivalent core features of Oracle HTTP Server and mod_plsql. Because the HTTP Listener runs in the same database where Oracle Application Express is installed, it is not possible to separate the HTTP listener from the database. For this reason, it is not recommended to use the embedded PL/SQL gateway for applications that run on the Internet. Additionally, the embedded PL/SQL gateway does not provide the same flexibility of configuration and detailed logging as Oracle HTTP Server with mod_plsql.
Oracle HTTP Server uses the mod_plsql plug-in to communicate with the Oracle Application Express engine within the Oracle database. mod_plsql functions act as a communication broker between the Web server and the Oracle Application Express engine in the Oracle database.
Each mod_plsql request is associated with a set of configuration values used to access the database called a Database Access Descriptor (DAD). mod_plsql provides a DAD parameter called PlsqlRequestValidationFunction which enables you to allow or disallow further processing of a requested procedure. You can utilize this parameter to implement tighter security for your PL/SQL application by blocking package and procedure calls which should not be allowed to run from the DAD. Oracle recommends a DAD configuration for Oracle Application Express which utilizes the PlsqlRequestValidationFunction directive with a value of wwv_flow_epg_include_modules.authorize.
The purpose of the PlsqlRequestValidationFunction parameter is to control which procedures can be invoked through mod_plsql. By default, the only procedures permitted are the public entry points of Oracle Application Express. This can be extended using the validation functions shipped with Oracle Application Express. To learn more, see "Restricting Access to Oracle Application Express" in Oracle Application Express Administration Guide.
Secure Sockets Layer (SSL) is a protocol for managing the security of data transmitted on the Internet. For Web applications, SSL is implemented by using the HTTPS protocol. Oracle recommends that you run Oracle Application Express applications using SSL (HTTPS protocol) to prevent any sensitive data from being sent over an unencrypted (cleartext) communication channel.
You can configure both your Oracle Application Express instance and all related applications to require HTTPS by setting the Require HTTPS attribute to Yes on the on the Manage Service page in Oracle Application Express Administration Services.
Setting the Require HTTPS attribute to Yes and logging out prevents anyone from logging in to Oracle Application Express Administration Services and from logging into an Oracle Application Express workspace as a developer or administrator unless the protocol in use is HTTPS.
Oracle recommends that you employ Secure Sockets Layer (SSL) when integrating Oracle Application Express with Oracle BI Publisher. Once SSL (HTTPS protocol) is configured for your Oracle BI Publisher server, you must create a wallet and specify the HTTPS protocol for the Report Server in the internal administration Environment Settings.
|
See Also: "Configuring Wallet Information" and "Configuring Report Printing" in Oracle Application Express Administration Guide |
Workspace administrators and developers can create user accounts for the purpose of logging in to the Oracle Application Express development environment and for end-user authentication to applications developed within their workspaces. The Oracle Application Express administrator can create password complexity rules, or a policy, for the passwords of these accounts. These rules apply to all accounts in the installation, across all workspaces.
The following are example password complexity policies:
All passwords must:
Contain at least one upper-case character
Contain at least one numeric digit
Must be at least six characters long
Note that many other variations are possible. Oracle recommends administrators establish a password complexity policy for each Oracle Application Express instance. To learn more, see "Enabling Login Controls for All Workspaces," "About Password Policies," and "Enabling Login Controls for a Workspace" in Oracle Application Express Administration Guide.
Site administrators can restrict password reuse for all administrator, developer, and end-user accounts based on a history of passwords previously used for the accounts.
To restrict password reuse:
Start SQL*Plus and connect to the database where Oracle Application Express is installed having the apex_administrator_role role or as SYS specifying the SYSDBA role. For example:
On Windows:
SYSTEM_DRIVE:\ sqlplus /nolog SQL> CONNECT SYS as SYSDBA Enter password: SYS_password
On UNIX and Linux:
$ sqlplus /nolog
SQL> CONNECT SYS as SYSDBA
Enter password: SYS_password
Execute the following statement:
ALTER SESSION SET CURRENT_SCHEMA = APEX_030200;
Execute the following statement:
BEGIN
APEX_INSTANCE_ADMIN.SET_PARAMETER('PASSWORD_HISTORY_DAYS',365);
COMMIT;
END;
/
This will restrict new or updated passwords to those that have not been used for the account for the previous 365 days. Recording of previously used passwords (actually, hashed representations of passwords) begins upon installation of Oracle Application Express 3.2.
To disable this feature, run the block above, providing 0 for the parameter value. For example:
BEGIN
APEX_INSTANCE_ADMIN.SET_PARAMETER('PASSWORD_HISTORY_DAYS',0);
COMMIT;
END;
/
|
Tip: Developers can also use theAPEX_UTIL.STRONG_PASSWORD_CHECK procedure and the APEX_UTIL.STRONG_PASSWORD_VALIDATION function described in Oracle Application Express API Reference. |
An Oracle Application Express runtime environment enables you to run production applications, but it does not provide a Web interface for administration or direct development of these applications
Oracle recommends that you run any sensitive production Oracle Application Express applications with a runtime installation of Oracle Application Express. A runtime installation does not expose the Web-based application development environment, thus preventing the use of Application Builder, SQL Workshop, and related utilities on a production installation. Additionally, a runtime environment only includes the Oracle Application Express database objects and privileges necessary to run applications, making it a more hardened environment.
By configuring Session Timeout attributes, you can reduce your application's exposure. Users often leave their computers unattended for extended periods and do not close applications before departing. Therefore, an unauthorized person can easily assume the user's identity within the application. By setting the session and idle timeout, users are automatically logged out of their application after the specified timeout.
Session Timeout attributes include:
Maximum Session Length in Seconds
Session Timeout URL
Maximum Session Idle Time in Seconds
Idle Timeout URL
To learn more about configuring these attributes at an application-level, see "Session Timeout". To learn more about configuring these attributes for an entire Oracle Application Express instance, see "Configuring Session Timeout" in Oracle Application Express Administration Guide.
By default, the ability to interact with network services is disabled in Oracle Database 11g release 1 (11.1). Therefore, if you are running Oracle Application Express with Oracle Database 11g release 1 (11.1), you must use the new DBMS_NETWORK_ACL_ADMIN package to grant connect privileges to any host for the APEX_030200 database user. Failing to grant these privileges results in issues with:
Sending outbound mail in Oracle Application Express.
Users can call methods from the APEX_MAIL package, but issues arise when sending outbound email.
Using Web services in Oracle Application Express.
PDF/report printing.
Searching for content in online Help (that is, using the Find link).
Topics in this section include:
|
Tip: To run the examples described in this section, the compatible initialization parameter of the database must be set to at least 11.1.0.0.0. By default an 11g database will have the parameter set properly, but a database upgraded to 11g from a prior version may not. See "Creating and Configuring an Oracle Database" in Oracle Database Administrator's Guide for information about changing database initialization parameters. |
The following example demonstrates how to grant connect privileges to a host for the APEX_030200 database user.
DECLARE
ACL_PATH VARCHAR2(4000);
ACL_ID RAW(16);
BEGIN
-- Look for the ACL currently assigned to '*' and give APEX_030200
-- the "connect" privilege if APEX_030200 does not have the privilege yet.
SELECT ACL INTO ACL_PATH FROM DBA_NETWORK_ACLS
WHERE HOST = '*' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL;
-- Before checking the privilege, make sure that the ACL is valid
-- (for example, does not contain stale references to dropped users).
-- If it does, the following exception will be raised:
--
-- ORA-44416: Invalid ACL: Unresolved principal 'APEX_030200'
-- ORA-06512: at "XDB.DBMS_XDBZ", line ...
--
SELECT SYS_OP_R2O(extractValue(P.RES, '/Resource/XMLRef')) INTO ACL_ID
FROM XDB.XDB$ACL A, PATH_VIEW P
WHERE extractValue(P.RES, '/Resource/XMLRef') = REF(A) AND
EQUALS_PATH(P.RES, ACL_PATH) = 1;
DBMS_XDBZ.ValidateACL(ACL_ID);
IF DBMS_NETWORK_ACL_ADMIN.CHECK_PRIVILEGE(ACL_PATH, 'APEX_030200',
'connect') IS NULL THEN
DBMS_NETWORK_ACL_ADMIN.ADD_PRIVILEGE(ACL_PATH,
'APEX_030200', TRUE, 'connect');
END IF;
EXCEPTION
-- When no ACL has been assigned to '*'.
WHEN NO_DATA_FOUND THEN
DBMS_NETWORK_ACL_ADMIN.CREATE_ACL('power_users.xml',
'ACL that lets power users to connect to everywhere',
'APEX_030200', TRUE, 'connect');
DBMS_NETWORK_ACL_ADMIN.ASSIGN_ACL('power_users.xml','*');
END;
/
COMMIT;
The following example is a less privileged demonstration of how to access resources on a local host. This example would enable indexing of Oracle Application Express Online Help and could possibly enable email and PDF printing if those servers were also on the local host.
DECLARE
ACL_PATH VARCHAR2(4000);
ACL_ID RAW(16);
BEGIN
-- Look for the ACL currently assigned to 'localhost' and give APEX_030200
-- the "connect" privilege if APEX_030200 does not have the privilege yet.
SELECT ACL INTO ACL_PATH FROM DBA_NETWORK_ACLS
WHERE HOST = 'localhost' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL;
-- Before checking the privilege, make sure that the ACL is valid
-- (for example, does not contain stale references to dropped users).
-- If it does, the following exception will be raised:
--
-- ORA-44416: Invalid ACL: Unresolved principal 'APEX_030200'
-- ORA-06512: at "XDB.DBMS_XDBZ", line ...
--
SELECT SYS_OP_R2O(extractValue(P.RES, '/Resource/XMLRef')) INTO ACL_ID
FROM XDB.XDB$ACL A, PATH_VIEW P
WHERE extractValue(P.RES, '/Resource/XMLRef') = REF(A) AND
EQUALS_PATH(P.RES, ACL_PATH) = 1;
DBMS_XDBZ.ValidateACL(ACL_ID);
IF DBMS_NETWORK_ACL_ADMIN.CHECK_PRIVILEGE(ACL_PATH, 'APEX_030200',
'connect') IS NULL THEN
DBMS_NETWORK_ACL_ADMIN.ADD_PRIVILEGE(ACL_PATH,
'APEX_030200', TRUE, 'connect');
END IF;
EXCEPTION
-- When no ACL has been assigned to 'localhost'.
WHEN NO_DATA_FOUND THEN
DBMS_NETWORK_ACL_ADMIN.CREATE_ACL('local-access-users.xml',
'ACL that lets power users to connect to everywhere',
'APEX_030200', TRUE, 'connect');
DBMS_NETWORK_ACL_ADMIN.ASSIGN_ACL('local-access-users.xml','localhost');
END;
/
COMMIT;
If you receive an ORA-44416: Invalid ACL error after running the previous script, use the following query to identify the invalid ACL:
REM Show the dangling references to dropped users in the ACL that is assigned
REM to '*'.
SELECT ACL, PRINCIPAL
FROM DBA_NETWORK_ACLS NACL, XDS_ACE ACE
WHERE HOST = '*' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL AND
NACL.ACLID = ACE.ACLID AND
NOT EXISTS (SELECT NULL FROM ALL_USERS WHERE USERNAME = PRINCIPAL);
Next, run the following code to fix the ACL:
DECLARE
ACL_ID RAW(16);
CNT NUMBER;
BEGIN
-- Look for the object ID of the ACL currently assigned to '*'
SELECT ACLID INTO ACL_ID FROM DBA_NETWORK_ACLS
WHERE HOST = '*' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL;
-- If just some users referenced in the ACL are invalid, remove just those
-- users in the ACL. Otherwise, drop the ACL completely.
SELECT COUNT(PRINCIPAL) INTO CNT FROM XDS_ACE
WHERE ACLID = ACL_ID AND
EXISTS (SELECT NULL FROM ALL_USERS WHERE USERNAME = PRINCIPAL);
IF (CNT > 0) THEN
FOR R IN (SELECT PRINCIPAL FROM XDS_ACE
WHERE ACLID = ACL_ID AND
NOT EXISTS (SELECT NULL FROM ALL_USERS
WHERE USERNAME = PRINCIPAL)) LOOP
UPDATE XDB.XDB$ACL
SET OBJECT_VALUE =
DELETEXML(OBJECT_VALUE,
'/ACL/ACE[PRINCIPAL="'||R.PRINCIPAL||'"]')
WHERE OBJECT_ID = ACL_ID;
END LOOP;
ELSE
DELETE FROM XDB.XDB$ACL WHERE OBJECT_ID = ACL_ID;
END IF;
END;
/
REM commit the changes.
COMMIT;
Once the ACL has been fixed, you must run the first script in this section to apply the ACL to the APEX_030200 user. See "Granting Connect Privileges to a Host".
The ability to search Oracle Application Express online Help is accomplished through Oracle Text and a URL data store. There is a change in the default behavior and permissions to use an Oracle Text URL data store in Oracle Database 11g Release 2 and later releases.
If users attempt to search Oracle Application Express online Help in Oracle database 11g Release 2 and encounter the following error, then the permission to use an Oracle Text URL data store has not been granted to database user APEX_030200.
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine ORA-20000: Oracle Text error: DRG-10758: index owner does not have the privilege to use file or URL data store
To enable the indexing of online Help in Oracle Application Express, the permission to use an Oracle Text URL data store must be granted to the APEX_030200 database user. This is accomplished by assigning this specific privilege to a datbase role and then granting this role to the APEX_030200 database user.
To determine if the ability to use an Oracle Text URL data store is already granted to a database role:
Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role. For example:
On Windows:
SYSTEM_DRIVE:\ sqlplus /nolog SQL> CONNECT SYS as SYSDBA Enter password: SYS_password
On UNIX and Linux:
$ sqlplus /nolog
SQL> CONNECT SYS as SYSDBA
Enter password: SYS_password
Run the following command:
SELECT par_value FROM ctxsys.ctx_parameters WHERE par_name = 'FILE_ACCESS_ROLE';
This returns either NULL or the database role which is granted the ability to use an Oracle Text URL data store.
If no value is returned by step 2, then create a new database role as shown in the following example:
CREATE ROLE APEX_URL_DATASTORE_ROLE;
Grant this role to the database user APEX_030200 with the following statement:
GRANT APEX_URL_DATASTORE_ROLE to APEX_030200;
If step 2 returned a value, use this database role name instead of the example APEX_URL_DATASTORE_ROLE.
Lastly, if step 2 did not return a value, then use the Oracle Text API to grant permission to the newly created database role with the following statement:
EXEC ctxsys.ctx_adm.set_parameter('file_access_role', 'APEX_URL_DATASTORE_ROLE');
This section describes security best practices for Oracle Application Express developers.
Topics in this section include:
Password items do not emit the text entered to the Web browser screen. When creating items of type password, Oracle recommends using password item types that do not save session state. This prevents the password from being saved in the database in the session state tables.
Available password item types include:
Password - Suppresses text entered into the field. Saves the value in session state when the page is submitted.
Password (submits when Enter pressed) - Suppresses text entered into the field and submits the page when ENTER is pressed.
Password (does not save state) - Suppresses text entered into the field. Does not save the value in session state.
Password (submits when Enter pressed, does not save state) - Suppresses text entered into the filed and submits the page when Enter is pressed. Does not save the value in session state.
The Password and Password (submits when Enter pressed) save the password in a database table when the page is submitted. Use these password item types only when the password is needed in session state for use by other pages during the session.
Password (does not save state) and Password (submits when Enter pressed, does not save state) do not save the password in a database table. Use these password item types when the submitted password value is used only by after-submit page processing on the same page and is never needed again during the session.
If you must reference and retrieve the value of a password in your application then you should set the Store value encrypted in session state attribute to Yes. To learn more, see "About Session State and Security".
At risk password items are those that either:
Do not use one of the password item types that does not save session state
Store the value in session state un-encrypted
Use the Password Items, Security Profiles, and Password Items report to help identify at risk password item:
To view reports that identify at risk password item types:
Navigate to the Workspace home page.
Click the Application Builder icon.
Select an application.
The Application home page appears.
On the Tasks list, click Application Reports.
To view the Password Items report:
Select Page Components.
Under Items, click Password Items.
This report shows all of the password items within the application and indicates if they use encryption and whethere they save state. Password items that do neither are highlighted as At Risk.
To view the Security Profiles report:
Select Cross Application.
Under Items, click Password Items.
To view the Password Items report:
Select Cross Application.
Under Items, click Security Profiles.
Notice the At Risk Password Items column.
For pages that contain password items, set page attribute Form Auto Complete to Off. Setting that attribute to Off prevents the Web browser from attempting to auto complete items on the page. To learn more about this attribute, see Table 5-6.
When users access Oracle Application Express application pages, numerous links containing session IDs become visible in the Web browser's location window. If the application is publicly accessible and the user communicates one of these links to another application user, for example by using email or a messaging service, the recipient can use the link and immediately begin sharing the original user's session. This can have a negative effect on both users as they use the application and lead to unpredictable, hard to reproduce screen behavior. To prevent this, Oracle recommends the use of the Zero Session ID feature for all applications where users are not required to provide login authentication. To learn more, see "Facilitating Bookmarks by Using Zero as the Session ID".
Cross site-scripting (also referred to as XSS) is a security breach that takes advantage of dynamically generated Web pages. In a XSS attack, a Web application is sent a script that activates when it is read by a user's browser. Once activated, these scripts can steal data, even session credentials, and return the information to the attacker.
If malicious code were introduced into an Oracle Application Express application, it could be rendered into HTML regions and other places within the application during normal page rendering. To prevent the introduction of malicious code into session state, the Application Express engine escapes characters in certain cases.
Topics in this section include:
In HTML regions and other static display areas, you can reference session state using the &ITEM. notation. Examples of static display areas include HTML regions, page headers and footers, region headers and footers, region titles, button labels, help text, form item labels and post-element text, templates, radiogroup (before and after field text), event success messages, event error messages, navigation bar attributes, application static substitution string values, chart labels and legends, breadcrumbs and list framing text, and calendar text, labels, or legends.
When session state is referenced in this way, the value emitted to the page will not have special characters (<, >, &, ") escaped if the referenced item is one of the following safe item display types:
Display as Text (does not save state)
Display as Text (escape special characters, does not save state)
Display as Text (based on LOV, does not save state)
Display as Text (based on PL/SQL, does not save state)
Text Field (Disabled, does not save state)
Stop and Start HTML Table (Displays label only)
If the referenced item has a display type other than one of the above types, the value emitted to the page will have special characters escaped. Although application-level items are also considered to have a safe display type, they do not actually have display properties like form items do.
The Application Express engine uses predefined smart escaping rules to determine if and when to escape values fetched from session state.
The reason for these rules is that items that use the display types listed previously are often for text containing HTML that is intended to be emitted to the browser without being filtered (that is, escaped). The only way this can be made safe is by the enforcement of the rule that these types of items are always escaped on input to the application. For example, if a user passes some text into a safe item using an Oracle Application Express f?p URL syntax, the Application Express engine escapes special characters when saving the value into session state. This has two intended results:
If the value contained no special characters, the value passed in is saved into session state exactly as it was provided.
If the value contained special characters, those characters are escaped when the value is saved into session state.
In either situation, the item can now safely be referenced using an &ITEM. notation in any HTML region or other static area mentioned previously.
You can use the safe item types listed previously to hold and emit HTML markup to the browser. For example, suppose you have a requirement to render some text in bold face by referencing a safe page item named P1_XXX (using &P1_XXX.) The item P1_XXX is presumed to contain the following HTML:
<b>ABABABAB</b>
You can achieve this by using application controls (computations, processes, item source expressions, item default values, and so on) to store values into these safe items. When values are introduced in this way, you ensure the safety of the content. When you use these methods, the Application Express engine does not escape any special characters when saving the values into session state.
Finally, the safety of safe items is ensured by a rule that prevents those items from being posted on a page and submitted to the Application Express engine as part of a page submission.
Items fetched from session state and rendered using htp.p or other methods should be explicitly escaped by the code where it is appropriate to do so. For example, suppose a PL/SQL dynamic content region on a page uses the following:
htp.p(v('SOME_ITEM'));
If the value of the item fetched from session state could contain unintended tags or scripts, you might want to use the following in the region:
htp.p(htf.escape_sc(v('SOME_ITEM')));
However, if you are confident that the fetched value is safe for rendering, you do not need to escape the value. As a developer, you need to determine when it is appropriate to not escape output.
As a best practice, follow this rule:
Never emit an item fetched from session state without escaping it unless the item is one of the safe types described in "About Safe Item Display Types".
The reason for this is that as a developer, there is no way you can prevent a hacker from posting a malicious value into a non-safe item. Even if your application does not present these items visibly to ordinary users, be aware that a hacker can mount a XSS attack using your application if you do not follow this rule.
The Application Express engine escapes data rendered in the body of a report. References to session state in report headings and messages are fetched from session state using the smart escaping rules so that the values of safe item types are not escaped and the values of other item types are escaped.
When form items, including hidden items, obtain their values during the generation of the form page to be sent to the browser, the resulting text is escaped before rendering. Some of the safe item types are exceptions to this rule in order to support the intended behavior of each display type.
Oracle Application Express persists session state in database tables. Session state is preserved in database tables because it is more secure to store the session state on the server side than on the client. Because Oracle Application Express applications use the stateless HTTP protocol, an application's session state across multiple page views is preserved in database tables. Not maintaining a synchronous database connection for each Oracle Application Express application user significantly lessens memory and database resource requirements.
Developers can query the session state stored by Oracle Application Express applications using the Application Builder and built-in monitoring pages. Developers and administrators can access session state for any application in the workspace to which they are authenticated.
A few best practices for developers include:
As a standard part of implementing program control flow, clear the session state of unneeded values using clear-cache page processes or clear-cache directives in URLs used to navigate to pages.
Use password page item types that do not save state. This prevents the entered passwords from being saved in session state tables in the database.
When sensitive data must persist in a session, it should be saved in Oracle Application Express session state tables in encrypted form. To use this feature, set the page item's Store value encrypted in session state attribute to Yes. Encrypted stored values are automatically decrypted when read.
|
Note: The objective of encrypted session state is to persist session state such that the unencrypted values cannot be read by other Oracle Application Express developers or database administrators who might have access to the Oracle Application Express session state tables, debug output, or database data files. Oracle recommends that database backups be performed using facilities that encrypt data in the backup files. |
|
Tip: You can encrypt item values up to 4000 bytes in length. Attempts to encrypt values longer than 4000 bytes produces an error message. |
Session State Protection is a built-in functionality that prevents hackers from tampering with the URLs within your application. URL tampering can adversely affect program logic, session state contents, and information privacy.
Enabling Session State Protection is a two-step process. First, you enable the feature. Second, you set page and item security attributes.
Topics in this section include:
When enabled, Session State Protection uses the Page Access Protection attributes and the Session State Protection item attributes with checksums positioned in f?p= URLs to prevent URL tampering and unauthorized access to and alteration of session state. When Session State Protection is disabled, the page and item attributes related to session state protection are ignored and checksums are not included checksums in generated f?p= URLs.
You can enable session state protection from either the Edit Security Attributes page or the Session State Protection page.
Enabling Session State Protection is a two-step process. First, you enable the feature. Second, you set page and item security attributes. You can perform these steps using a wizard, or you can set security attributes for pages and items manually on the Session State Protection page.
Topics in this section include:
Enabling Session State Protection from Edit Security Attributes
Enabling Session State Protection from Session State Protection
To enable Session State Protection from the Edit Security Attributes page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click the Shared Components icon.
Under Security, click Edit Security Attributes.
Scroll down to Session State Protection and select Enabled from the Session State Protection list.
To configure session Session State Protection, click Manage Session State Protection.
The Session State Projection page appears.
Navigate to the Edit Security Attributes page to set page and item security attributes.
|
Tip: To disable Session State Protection, perform the same steps again, but select Disabled instead of Enabled. Disabling Session State Protection will not change existing security attribute settings, but those attributes will be ignored at run time. |
Enabling Session State Protection affects whether bookmarked links to the current application will work. Consider the following rules:
Bookmarked links created after Session State Protection is enabled will work if the bookmarked link contains a checksum.
Bookmarked links created before Session State Protection is enabled will not work if the bookmarked link contains a checksum.
Bookmarks that do not contain checksums or contain unnecessary checksums will not be affected by Session State Protection.
During page rendering, the Application Express engine uses a hidden application attribute (a checksum salt) during computation and to verify checksums included in f?p URLs. When you enable Session State Protection, the Application Express engine includes checksums. You can reset the checksum salt attribute by clicking Expire Bookmarks on the Edit Security Attributes page. Note that if you click Expire Bookmarks, bookmarked URLs used to access your application that contain previously generated checksums will fail.
To enable Session State Protection:
Navigate to the Shared Components page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
Under Security, select Session State Protection.
The Session State Protection page appears. Note the current Session State Protection status (Enabled or Disabled) displays at the top of the page.
Click the Set Protection button.
The Session State Protection wizard appears.
Under Select Action, select Enable and click Next.
Next, determine whether to set security attributes for pages and items.
Select Enable and click Next.
Click Enable Session State Protection.
|
Tip: To disable Session State Protection, perform the same steps, but select Disable instead of Enable. Disabling Session State Protection will not change existing security attribute settings, but those attributes will be ignored at run time. |
Once you have enabled Session State Protection, the next step is to configure security attributes. You can configure security attributes in two ways:
Use a wizard and select a value for specific attribute categories. Those selections will then be applied to all pages and items within the application.
Configure values for individual pages, items, or application items.
Topics in this section include:
|
Tip: Before you can configure security attributes, you must first enable Session State Protection. See "Enabling Session State Protection". |
You can review a summary of Session State Protection settings for pages, items, and application items on the first page of the Session State Protection wizard.
To view summaries of existing Session State Protection settings:
Navigate to the Session State Protection page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
Under Security, select Session State Protection.
The Session State Protection page appears.
Click Set Protection.
Expand the following reports at the bottom of the page:
Page Level Session State Protection Summary
Page Item Session State Protection Summary
Application Item Session State Protection
When you configure Session State Protection using a wizard, you set a value for specific attribute categories. Those selections are then applied to all pages and items within the application.
To configure Session State Protection using a wizard:
Navigate to the Session State Protection page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
Under Security, select Session State Protection.
The Session State Protection page appears.
Click Set Protection.
The Session State Protection wizard appears.
Under Select Action, select Configure and click Next.
For Page Access Protection, select one of the following:
Unrestricted - The page may be requested using a URL with or without session state arguments (Request, Clear Cache, Name/Values).
Arguments Must Have Checksum - If Request, Clear Cache, or Name/Value arguments appear in the URL, a checksum must also be provided. The checksum type must be compatible with the most stringent Session State Protection attribute of all the items passed as arguments.
No Arguments Allowed - A URL may be used to request the page but no Request, Clear Cache, or Name/Value arguments are allowed.
No URL Access - The page may not be accessed using a URL; however, the page may be the target of a Branch to Page branch type, which does not do a URL redirect.
For Application Item Protection, select one of the following:
Unrestricted - The item's session state may be set by passing the item name/value in a URL or in a form. No checksum is required in the URL.
Checksum Required: Application Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the schema is provided. A user-level checksum or a session-level checksum will also suffice (see next bullets). Use this option when you want to allow the item to be set only by URLs having checksums that were generated by any user running the same application in the current workspace but in a different session.
Checksum Required: User Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the workspace, application, and user is provided. A session-level checksum will also suffice (see next bullet). Use this option when you want to allow the item to be set only by URLs having checksums that were generated by the same named user, running the same application in the current workspace but in a different session.
Checksum Required: Session Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the current session is also provided. Use this option when you want to allow this item to be set only by URLs having checksums that were generated in the current session.
Restricted - May not be set from browser - The item may not be altered using the URL or POSTDATA. Use this option when you want to restrict the way that the item value can be set to internal processes, computations, and so on. This attribute is applicable only to items that cannot be used as data entry items and is always observed even if Session State Protection is disabled.
Use this attribute for application items or for page items with any of these Display As types:
Display as Text (escape special characters, does not save state)
Display as Text (does not save state)
Display as Text (based on LOV, does not save state)
Display as Text (based on PLSQL, does not save state)
Text Field (Disabled, does not save state)
Stop and Start HTML Table (Displays label only)
For Page Data Entry Item Protection, select one of the following:
Unrestricted - The item's session state may be set by passing the item name/value in a URL or in a form. No checksum is required in the URL.
Checksum Required: Application Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the schema is provided. A user-level checksum or a session-level checksum will also suffice (see next bullets). Use this option when you want to allow the item to be set only by URLs having checksums that were generated by any user running the same application in the current workspace but in a different session.
Checksum Required: User Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the workspace, application, and user is provided. A session-level checksum will also suffice (see next bullet). Use this option when you want to allow the item to be set only by URLs having checksums that were generated by the same named user, running the same application in the current workspace but in a different session.
Checksum Required: Session Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the current session is provided. Use this option when you want to allow this item to be set only by URLs having checksums that were generated in the current session.
For Page Display-Only Item Protection, select one of the following:
Unrestricted - The item may be set by passing the item name/value in a URL or in a form. No checksum is required in the URL.
Checksum Required: Application Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the schema is provided. A user-level checksum or a session-level checksum will also suffice (see next bullets). Use this option when you want to allow the item to be set only by URLs having checksums that were generated by any user running the same application in the current workspace but in a different session.
Checksum Required: Session Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the current session is provided. Use this option when you want to allow this item to be set only by URLs having checksums that were generated in the current session.
Checksum Required: User Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the workspace, application, and user is provided. A session-level checksum will also suffice (see next bullet). Use this option when you want to allow the item to be set only by URLs having checksums that were generated by the same named user, running the same application in the current workspace but in a different session.
Restricted: May not be set from browser - The item may not be altered using the URL or POSTDATA. Use this when you want to restrict the way that the item value can be set to internal processes, computations, and so on. This attribute is always observed, even if Session State Protection is disabled.
This attribute may be used with any of these Display As types:
Display as Text (escape special characters, does not save state)
Display as Text (does not save state)
Display as Text (based on LOV, does not save state)
Display as Text (based on PLSQL, does not save state)
Text Field (Disabled, does not save state)
Stop and Start HTML Table (Displays label only)
Click Next.
Click Finish.
To configure Session State Protection for Pages:
Navigate to the Session State Protection page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
Under Security, select Session State Protection.
The Session State Protection page appears.
Click the Page icon.
To filter the view, use the Page, Display, and Page Access Protection lists at the top of the page.
Select a page number.
The Set Page and Item Protection page appears. The following information displays at the top of the page:
Application ID and name
Session State Protection status (Enabled or Disabled)
Page Number
Page name
For Page Access Protection, select one of the following:
Unrestricted - The page may be requested using a URL with or without session state arguments (Request, Clear Cache, Name/Values).
Arguments Must Have Checksum - If Request, Clear Cache, or Name/Value arguments appear in the URL, a checksum must also be provided. The checksum type must be compatible with the most stringent Session State Protection attribute of all the items passed as arguments.
No Arguments Allowed - A URL may be used to request the page but no Request, Clear Cache, or Name/Value arguments are allowed.
No URL Access - The page may not be accessed using a URL; however, the page may be the target of a Branch to Page branch type, which does not do a URL redirect.
For Item Types, select Data Entry Items or Display-only Items.
Data Entry items are items that can be altered using forms and include hidden items. Display-Only items are rendered only and are not submitted with the form.
If you select Data Entry Items, select a session state protection level for each item:
Unrestricted - The item's session state may be set by passing the item name/value in a URL or in a form. No checksum is required in the URL.
Checksum Required: Application Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the schema is provided. A user-level checksum or a session-level checksum will also suffice (see next bullets). Use this option when you want to allow the item to be set only by URLs having checksums that were generated by any user running the same application in the current workspace but in a different session.
Checksum Required: User Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the workspace, application, and user is provided. A session-level checksum will also suffice (see next bullet). Use this option when you want to allow the item to be set only by URLs having checksums that were generated by the same named user, running the same application in the current workspace but in a different session.
Checksum Required: Session Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the current session is provided. Use this option when you want to allow this item to be set only by URLs having checksums that were generated in the current session.
If you select Display-only Item, select a session state protection level for each item:
Unrestricted - The item may be set by passing the item name/value in a URL or in a form. No checksum is required in the URL.
Restricted: May not be set from browser - The item may not be altered using the URL or POSTDATA. Use this when you want to restrict the way that the item value can be set to internal processes, computations, and so on. This attribute is always observed, even if Session State Protection is disabled. This attribute may be used with any of these Display As types:
Display as Text (escape special characters, does not save state)
Display as Text (does not save state)
Display as Text (based on LOV, does not save state)
Display as Text (based on PLSQL, does not save state)
Text Field (Disabled, does not save state)
Stop and Start HTML Table (Displays label only)
Checksum Required: Application Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the schema is provided. A user-level checksum or a session-level checksum will also suffice (see next bullets). Use this option when you want to allow the item to be set only by URLs having checksums that were generated by any user running the same application in the current workspace but in a different session.
Checksum Required: User Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the workspace, application, and user is provided. A session-level checksum will also suffice (see next bullet). Use this option when you want to allow the item to be set only by URLs having checksums that were generated by the same named user, running the same application in the current workspace but in a different session.
Checksum Required: Session Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the current session is provided. Use this option when you want to allow this item to be set only by URLs having checksums that were generated in the current session.
Click Apply Changes.
To configure Session State Protection for items:
Navigate to the Session State Protection page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
Under Security, select Session State Protection.
The Session State Protection page appears.
Click the Item icon.
To filter the view, select from the Page, Display, and Item Session State Protection lists at the top of the page and click Go.
Select a page number.
The Edit Session State Protection for Page and Items page appears. The following information displays at the top of the page:
Application ID and name
Session State Protection status (Enabled or Disabled)
page Number
Page name
For Page Access Protection, select a session state protection level for each item:
Unrestricted - The page may be requested using a URL with or without session state arguments (Request, Clear Cache, Name/Values).
Arguments Must Have Checksum - If Request, Clear Cache, or Name/Value arguments appear in the URL, a checksum must also be provided. The checksum type must be compatible with the most stringent Session State Protection attribute of all the items passed as arguments.
No Arguments Allowed - A URL may be used to request the page but no Request, Clear Cache, or Name/Value arguments are allowed.
No URL Access - The page may not be accessed using a URL, however the page may be the target of a Branch to Page branch type, which does not do a URL redirect.
For Item Types, select Data Entry Items or Display-only Items.
Data Entry items are items that can be altered using forms and include hidden items. Display-Only items are rendered only and are not submitted with the form.
If you select Data Entry Items, select a session state protection level for each item:
Unrestricted - The item's session state may be set by passing the item name/value in a URL or in a form. No checksum is required in the URL.
Checksum Required: Application Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the schema is provided. A user-level checksum or a session-level checksum will also suffice (see next bullets). Use this option when you want to allow the item to be set only by URLs having checksums that were generated by any user running the same application in the current workspace but in a different session.
Checksum Required: User Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the workspace, application, and user is provided. A session-level checksum will also suffice (see next bullet). Use this option when you want to allow the item to be set only by URLs having checksums that were generated by the same named user, running the same application in the current workspace but in a different session.
Checksum Required: Session Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the current session is provided. Use this option when you want to allow this item to be set only by URLs having checksums that were generated in the current session.
If you select Display-only Item, select a session state protection level for each item:
Unrestricted - The item may be set by passing the item name/value in a URL or in a form. No checksum is required in the URL.
Restricted: May not be set from browser - The item may not be altered using the URL or POSTDATA. Use this when you want to restrict the way that the item value can be set to internal processes, computations, and so on. This attribute is always observed, even if Session State Protection is disabled. This attribute may be used with any of these Display As types:
Display as Text (escape special characters, does not save state)
Display as Text (does not save state)
Display as Text (based on LOV, does not save state)
Display as Text (based on PLSQL, does not save state)
Text Field (Disabled, does not save state)
Stop and Start HTML Table (Displays label only)
Checksum Required: Application Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the schema is provided. A user-level checksum or a session-level checksum will also suffice (see next bullets). Use this option when you want to allow the item to be set only by URLs having checksums that were generated by any user running the same application in the current workspace but in a different session.
Checksum Required: User Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the workspace, application, and user is provided. A session-level checksum will also suffice (see next bullet). Use this option when you want to allow the item to be set only by URLs having checksums that were generated by the same named user, running the same application in the current workspace but in a different session.
Checksum Required: Session Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the current session is provided. Use this option when you want to allow this item to be set only by URLs having checksums that were generated in the current session.
Click Apply Changes.
To configure Session State Protection for application items:
Navigate to the Session State Protection page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
Under Security, select Session State Protection.
The Session State Protection page appears.
Click the Application Item icon.
Select an application item.
Under Security, select one of the following from the Session State Protection list:
Unrestricted - The item's session state may be set by passing the item name/value in a URL or in a form. No checksum is required in the URL.
Restricted - May not be set from browser - The item may not be altered using the URL or POSTDATA. Use this option when you want to restrict the way that the item value can be set to internal processes, computations, and so on. This attribute is only applicable only to items that cannot be used as data entry items and is always observed even if Session State Protection is disabled. This attribute may be used for application items or for page items with any of these Display As types:
Display as Text (escape special characters, does not save state)
Display as Text (does not save state)
Display as Text (based on LOV, does not save state)
Display as Text (based on PLSQL, does not save state)
Text Field (Disabled, does not save state)
Stop and Start HTML Table (Displays label only)
Checksum Required: Application Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the schema is provided. A user-level checksum or a session-level checksum will also suffice (see next bullets). Use this option when you want to allow the item to be set only by URLs having checksums that were generated by any user running the same application in the current workspace but in a different session.
Checksum Required: User Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the workspace, application, and user is provided. A session-level checksum will also suffice (see next bullet). Use this option when you want to allow the item to be set only by URLs having checksums that were generated by the same named user, running the same application in the current workspace but in a different session.
Checksum Required: Session Level - The item's session state may be set by passing the item name/value in a URL if a checksum specific to the current session is provided. Use this option when you want to allow this item to be set only by URLs having checksums that were generated in the current session.
Click Apply Changes.
Oracle Application Express enables you to easily build an application that can be used to upload files and to access uploaded files. These files are uploaded into a common file storage table. Although the database view APEX_APPLICATION_FILES shows those files associated with your database account (or workspace), programmatic access to the common file storage table does not always require authentication, enabling other users to see your uploaded files. For this reason, Oracle recommends that developers either use the methods described in "About BLOB Support in Forms and Reports" or use the methods described in Oracle Application Express How To Documents for file upload on OTN at:
http://www.oracle.com/technetwork/developer-tools/apex/overview/index.html
Either of these methods results in the uploaded files being stored in schema tables and not the public table.
|
See Also: "Differences Between Page Items and Application Items" and "About Item Types" to learn more about creating a File Browse page-level item |
Authentication is the process of establishing each user's identify before they can access your application. Authentication may require a user identify a user name and password or could involve the use of digital certificates or a secure key.
When you create an authentication scheme, you have the option of choosing from a number of preconfigured authentication schemes, copying an authentication scheme from an existing application, or creating your own custom authentication scheme.
Topics in this section include:
Viewing the Authentication Scheme Associated with an Application
Changing the Authentication Scheme Associated with an Application
You determine how your application interacts with users. If all users have the same rights and privileges, they are referred to as public users. However, if your application needs to track each user individually, you need to specify an authentication method.
Authentication establishes the identity of each user who accesses your application. Many authentication processes require that a user provide some type of credentials such as a user name and password. These credentials are then evaluated and they either pass or fail. If the credentials pass, the user has access to the application. Otherwise, access is denied.
Once a user has been identified, the Application Express engine keeps track of each user by setting the value of the built-in substitution string APP_USER. As a user navigates from page to page, the Application Express engine sets the value of APP_USER to identify the user. The Application Express engine uses APP_USER as one component of a key for tracking each user's session state.
From a programming perspective, you can access APP_USER using the following syntax:
From PL/SQL:
V('APP_USER')
As a bind variable from either PL/SQL or SQL:
:APP_USER
You can use APP_USER to perform your own security checks and conditional processing. For example, suppose you created the following table:
CREATE TABLE my_security_table ( user_id VARCHAR2(30), privilege VARCHAR2(30));
Once created, you could populate this table with user privilege information and then use it to control the display of pages, tabs, navigation bars, buttons, regions, or any other control or component.
As you create your application, you need to determine whether to include authentication. You can:
Choose to not require authentication. Oracle Application Express does not check any user credentials. All pages of your application are accessible to all users.
Select a built-in authentication scheme. Create an authentication method based on available preconfigured authentication schemes. Depending on which scheme you choose, you may also have to configure the corresponding components of Oracle 10giAS, Oracle Internet Directory, or other external services. See "Using Preconfigured Authentication Schemes" and "Changing the Authentication Scheme Associated with an Application".
Create custom authentication scheme. Create a custom authentication method to have complete control over the authentication interface. To implement this approach, you must provide a PL/SQL function the Application Express engine executes before processing each page request. This function's Boolean return value determines whether the Application Express engine processes the page normally or displays a failure page. See "Creating an Authorization Scheme".
To create an authentication scheme:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Shared Components.
The Shared Components page appears.
Under Security, select Authentication Schemes.
The Authentication Schemes page appears.
To create a new authentication scheme, click Create.
Specify how the scheme should be created by selecting one of the following:
Based on preconfigured scheme. See "Managing Existing Authentication Schemes".
As a copy of an existing scheme
From scratch
Follow the on-screen instructions.
When you select a preconfigured authentication scheme, Oracle Application Express creates an authentication scheme for your application that follows a standard behavior for authentication and session management.
Topics in this section include:
Open Door Credentials enables anyone to access your application using a built-in login page that captures a user name. This authentication method is useful during application development.
To set up Open Door Credentials:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Shared Components.
The Shared Components page appears.
Under Security, select Authentication Schemes.
On the Authentication Schemes page, click Create.
Select Based on a pre-configured scheme from the gallery.
From Gallery, select Show Login Page and Use Open Door Credentials.
Specify a login page and click Next.
Enter a name and click Create Scheme.
Oracle Application Express Account Credentials are internal user accounts (also known as "cookie user" accounts) that are created within and managed in the Oracle Application Express user repository. When you use this method, your application is authenticated against these accounts.
Application Express Account Credentials is a good solution when:
You want control of the user account repository
User name and password-based approach to security is sufficient
You do not need to integrate into a single sign-on framework
This is an especially good approach when you need to get a group of users up and running on a new application quickly.
To set up Application Express Account Credentials:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Shared Components.
The Shared Components page appears.
Under Security, select Authentication Schemes.
On the Authentication Schemes page, click Create.
Select Based on a pre-configured scheme from the gallery.
From Gallery, select Show Login Page and Use Application Express Account Credentials.
Specify a login page and click Next.
Enter a name and click Create Scheme.
Database Account Credentials utilizes database schema accounts.This authentication scheme requires that a database user (schema) exist in the local database. When using this method, the user name and password of the database account is used to authenticate the user.
Database Account Credentials is a good choice if having one database account for each named user of your application is feasible and account maintenance using database tools meets your needs
To set up Database Account Credentials:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Shared Components.
The Shared Components page appears.
Under Security, select Authentication Schemes.
On the Authentication Schemes page, click Create.
Select Based on a pre-configured scheme from the gallery.
From Gallery, select Show Login Page and Use Database Account Credentials.
Specify a login page and click Next.
Enter a name and click Create Scheme.
You can configure any authentication scheme that uses a login page to use Lightweight Directory Access Protocol (LDAP) to verify the user name and password submitted on the login page.
Application Builder includes wizards and edit pages that explain how to configure this option. These wizards assume that an LDAP directory accessible to your application for this purpose already exists and that it can respond to a SIMPLE_BIND_S call for credentials verification. When you create an LDAP Credentials authentication scheme, the wizard requests and saves the LDAP host name, LDAP port, and the DN string. An optional preprocessing function can be specified to adjust formatting of the user name passed to the API.
To set up LDAP credentials verification:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Shared Components.
The Shared Components page appears.
Under Security, select Authentication Schemes.
On the Authentication Schemes page, click Create.
Select Based on a pre-configured scheme from the gallery.
From Gallery, select Show Login Page and Use LDAP Directory Credentials.
Specify a login page and click Next.
Specify the following and click Next.
LDAP Host
LDAP Port
LDAP Distinguished Name (DN) String
(Optional) LDAP Username Edit Function
To view help for a specific item, click the item label. When help is available, the item label changes to red when you pass your cursor over it and the cursor changes to an arrow and question mark. See "About Field-Level Help".
Enter a name and click Create Scheme.
Database Access Descriptor (DAD) database authentication uses the Oracle database native authentication and user mechanisms to authenticate users using a basic authentication scheme. This authentication scheme gets the user name from the DAD either as the value stored in the DAD configuration or, if the account information is not stored in the DAD configuration, as the user name captured using the basic authentication challenge.
To use DAD credentials verification:
Each application user must have a user account in the Oracle database.
You must configure a PL/SQL DAD for basic authentication (without account information).
This results in one user name/password challenge for browser session for your application users. The user identity token is then made available in the APP_USER item.
DAD database authentication is useful when you need to implement an authentication method that requires minimal setup for a manageable number of users. Ideally these users would have self-managed accounts in the database and your use of this authentication method would be short lived (for example, during the demonstration or prototyping stages of development).
The main drawback of this approach is burdensome account maintenance, especially if users do not administer their own passwords, or if their database accounts exist only to facilitate authentication to your application.
To set up DAD Credentials Verification:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Shared Components.
The Shared Components page appears.
Under Security, select Authentication Schemes.
On the Authentication Schemes page, click Create.
Select Based on a pre-configured scheme from the gallery.
From Gallery, select No Authentication (using DAD).
Enter a name and click Create Scheme.
Oracle Application Server Single Sign-On verification delegates authentication to the Oracle AS Single Sign-On (SSO) Server. To use this authentication scheme, your site must have been registered as a partner application with the SSO server.
Oracle Application Express applications can operate as partner applications with Oracle Application Server's Single Sign-On (SSO) infrastructure. To accomplish this, you must register your application (or register the Application Express engine) as the partner application. To do so, follow the Oracle Application Server instructions for registering partner applications and install the Oracle 9iAS SSO Software Developer Kit (SDK).
If you choose this approach, your application will not use an integrated login page. Instead, when a user accesses your application in a new browser session, the Application Express engine redirects to the Single Sign-On login page. After the user is authentication by SSO, the SSO components redirect back to your application, passing the user identity and other information to the Application Express engine. The user can then continue to use the application until they log off, terminate their browser session, or until some other session-terminating event occurs.
To set up Oracle Application Server Single Sign-On:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Shared Components.
The Shared Components page appears.
Under Security, select Authentication Schemes.
On the Authentication Schemes page, click Create.
Select Based on a pre-configured scheme from the gallery.
From Gallery, select one of the following:
Oracle Application Server Single Sign-On (Application Express engine as Partner App) delegates authentication to the Oracle AS Single Sign-On (SSO) Server. To use this authentication scheme, your site must have been registered as a partner application with the SSO server.
Oracle Application Server Single Sign-On (My application as Partner App) delegates authentication to the SSO server. Requires that you register an application with SSO as a partner application.
Enter a name and click Create Scheme.
Creating an authentication scheme from scratch gives you complete control over your authentication interface. This is the best approach for applications when any of the following is true:
Database authentication or other methods are not adequate.
You want to develop your own login form and associated methods.
You want to delegate all aspects of user authentication to external services such as Oracle 10gAS Single Sign-On.
You want to control security aspects of session management.
You want to record or audit activity at the user or session level.
You want to enforce session activity or expiry limits.
You want to program conditional one-way redirection logic before Oracle Application Express page processing.
You want to integrate your application with non-Oracle Application Express applications using a common session management framework.
Your application consists of multiple applications that operate seamlessly (for example, more than one application ID).
When running custom authentication, Oracle Application Express attempts to prevent two improper situations:
Intentional attempts by a user to access session state belonging to someone else. However, users can still type in an arbitrary application session ID into the URL.
Inadvertent access to a stale session state (probably belonging to the same user from an earlier time). This would commonly result from using bookmarks to application pages.
Oracle Application Express checks that the user identity token set by the custom authentication function matches the user identity recorded when the application session was first created. If the user has not yet been authenticated and the user identity is not yet known, the session state being accessed does not belong to someone else. These checks determine whether the session ID in the request can be used. If not, the Application Express engine redirects back the same page using an appropriate session ID.
When you create an application in Oracle Application Express, a login page is created. The alias for the page is 'LOGIN'. You can use this page as the "invalid session page" in an authentication scheme. The page is constructed with processes that call the Oracle Application Express login API to perform credentials verification and session registration.
You can also build your own login pages using the pre-built pages as models and tailoring all of the user interface and processing logic to your requirements.
To create a login page for your application:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Create Page.
Select Login Page.
Specify Login page attributes and click Create.
Deep linking refers to the ability to link to an Oracle Application Express page out of context (for example, from a hyperlink in an email or workflow notification). When you link to a page out of context and the application requires the user be authenticated, the user will be taken to the login page. After credentials verification, the Application Express engine automatically displays the page that was referenced in the original link. Deep linking is supported for applications that use authentication schemes.
Once created, available authentication schemes display in the Authentication Schemes Repository.
To navigate to the Authentication Schemes Repository:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Shared Components.
The Shared Components page appears.
Under Security, select Authentication Schemes.
The Authentication Schemes page appears. You can change the appearance of the page by making a selection from the View list. Available options include:
Icons (the default) displays each authentication scheme as a large icon. To edit an authentication scheme, click the appropriate icon.
Details displays each application item as a line in a report.
In Details view you can:
Edit an authentication scheme by selecting the scheme name
View a list of the steps performed on each page by clicking the Show icon
Apply an authentication scheme to an application by clicking the make current link
To view the current authentication scheme for an application:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click Shared Components.
Under Security, click Edit Security Attributes.
Locate the Authentication section. The current authentication scheme displays next to Authentication Scheme.
To link to the Authentication Scheme pages, select the scheme name.
To change the authentication scheme for an application:
Navigate to the Authentication Schemes:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Shared Components.
The Shared Components page appears.
Under Security, select Authentication Schemes.
Click the Change Current tab at the top of the page.
Select a new authentication scheme and click Next.
Click Make Current.
The Authentication Schemes report lists authentication scheme utilization for all applications in the current workspace.
To view the Authentication Schemes report:
On the Workspace home page, click the Application Builder icon.
Select an application.
The Application home page appears.
On the Tasks list, click View Application Reports.
Click Cross Application Reports.
Select Authentication Schemes.
Click the application ID to link to the appropriate Application home page.
Authorization is a broad term for controlling access to resources based on user privileges. While conditions control the rendering and processing of specific page controls or components, authorization schemes control user access to specific controls or components.
Topics in this section include:
An authorization scheme extends the security of your application's authentication scheme. You can specify an authorization scheme for an entire application, page, or specific control such as a region, item, or button. For example, you could use an authorization scheme to selectively determine which tabs, regions, or navigation bars a user sees.
An authorization scheme either succeeds or fails. If a component or control level authorization scheme succeeds, the user can view the component or control. If it fails, the user cannot view the component or control. If an application or page-level authorization scheme fails, then Oracle Application Express displays a previously defined message.
When you define an authorization scheme, you give it a unique name. Once defined, you can attach it to any component or control in your application. To attach an authorization scheme to a component or control in your application, simply navigate to the appropriate attributes page and select an authorization scheme from the Authorization Scheme list.
Before you can attach an authorization scheme to an application or an application component or control, you must first create it.
To create an authorization scheme:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Shared Components.
The Shared Components page appears.
Under Security, select Authorization Schemes.
Click Create.
Specify how to create an authorization scheme by selecting one of the following:
From Scratch
As a Copy of an Existing Authorization Scheme
Follow the on-screen instructions.
To edit attributes of an existing authorization scheme:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Shared Components.
The Shared Components page appears.
Under Security, select Authorization Schemes.
The Authorization Schemes page appears. By default, each scheme displays as an icon.
To access a detail view of all schemes, select Details from the View list.
The Authorization Schemes page appears. You can change the appearance of the page by making a selection from the View list. Available options include:
Icons (the default) displays each authentication scheme as a large icon. To edit an authorization scheme, click the appropriate icon.
Details displays each application item as a line in a report. To edit an authorization scheme, select the scheme name.
You can specify when your authorization scheme is validated in the Evaluation Point attribute. You can choose to have your authorization scheme validated once for each session or once for each page view.
Keep in mind, if you specify that an authorization scheme should be evaluated once for each session and the authorization scheme passes, the underlying code, test, or query will not be executed again for the duration of the application session. If your authorization scheme consists of a test whose results might change if evaluated at different times during the session, then you should specify that the evaluation point be once for each page view.
If an authorization scheme is validated once for each session, Oracle Application Express caches the validation results in each user's session cache. You can reset a session's authorization scheme state by calling the APEX_UTIL.RESET_AUTHORIZATIONS API.
Calling this procedure nulls out any previously cached authorization scheme results for the current session. Be aware that this procedure takes no arguments and is part of the publicly executable APEX_UTIL package.
Once you have created an authorization scheme you can attach it to an entire application, page, control, or component.
Topics in this section include:
To attach an authorization scheme to an application:
On the Workspace home page, click the Application Builder icon.
Select an application.
Click the Shared Components icon.
The Shared Components page appears.
Under Security, click Edit Security Attributes.
Scroll down to Authorization and make a selection from the Authorization Scheme list.
To attach an authorization scheme to a page:
On the Workspace home page, click the Application Builder icon.
Select an application.
Select a page.
Under Page Rendering, locate the section with the title of Page.
Click Edit page attributes icon.
Scroll down to Security and make a selection from the Authorization Scheme list.
To attach an authorization scheme to a page component or control:
On the Workspace home page, click the Application Builder icon.
Select an application.
Select a page.
Click the name of the component or control to which you want to apply the authorization scheme.
Scroll down to Security and make a selection from the Authorization Scheme list.
You can use the Authorization Scheme Subscription and Authorization Scheme Utilization reports to better manage authorization schemes within your application.
To view authorization scheme reports:
On the Workspace home page, click the Application Builder icon.
Select an application.
On the Application home page, click Shared Components.
The Shared Components page appears.
Under Security, select Authorization Schemes.
Click the appropriate tab at the top of the page:
Subscription
Utilization
Use the Authorization Scheme Subscription report to view details about authorization schemes subscription.
Use the Authorization Scheme Utilization report to view details about authorization schemes utilization.
To view additional reports indicating which pages having authorization schemes and which do not, select one of the following from the Tasks list:
Report Pages With Authorization Schemes
Report Pages Without Authorization Schemes
A condition is a small unit of logic that helps you control the display of regions, items, buttons, and tabs as well execute processes, computations and validations. When you apply a condition to a control or component, the condition is evaluated. Whether a condition passes or fails determines whether a control or component displays, or page processing executes.
You can specify conditions by selecting a condition type when you create the control (region, button, or item) or component (tab, list, or navigation bar), or by making a selection under the Condition attribute.
Table A-1 describes many Application Builder conditions. To view a complete listing of all available conditions for a given control or component, click the View icon to the right of the Condition Type list. Shortcuts to common selections appear directly beneath the Type list. If your condition requires an expression, type it in the appropriate field.
Table A-1 describes the conditions available in Application Builder.
Table A-1 Available Conditions
| Condition | Description |
|---|---|
|
Always |
Always returns true. Used primarily for the read-only conditions of a page item |
|
Current Language != Expression 1 |
Verifies the language setting in which the client browser is not currently running. Evaluates to true if the current language is contained within the string entered in Expression 1. |
|
Current Language = Expression |
Verifies the language setting in which the client browser is currently running. Evaluates to true if the current language matches the value entered in Expression 1. |
|
Current Language is contained within Expression 1 |
Determines whether the browser current language is contained within a string. Evaluates to true if the current language matches the string entered in Expression 1. For example, to check if the current language is either en-US or en-GB, choose this condition and enter the following string in Expression 1: en-us,en-gb |
|
Current Language is not contained within Expression 1 |
Verifies the application's current language is not contained within a specified string. Evaluates to true if the current language is not contained within the string entered in Expression 1. |
|
Current page != Expression 1 |
Evaluates to true if the current page does not equal the page you specify in Expression 1. |
|
Current Page != Page Submitted (this page was not the page posted) |
Determines if the specified page was not posted. Evaluates to true if the current page does not match the value entered in Expression 1. |
|
Current page = Expression 1 |
Evaluates to true if the current page equals the page you specify in Expression 1. |
|
Current Page = Page Submitted (this page was posted) |
Verifies the whether the specified page was posted. Evaluates to true if the current page matches the value entered in Expression 1. |
|
Current Page is contained within Expression 1 (comma-delimited list of pages) |
Verifies if the current page is part of the list of pages you specify in Expression 1. To check if the current page is in either page 1, 2, 3 or 4, select this condition type and enter the following string in Expression 1: 1,2,3,4 |
|
Current page is in Printer Friendly mode |
Only displays certain page control or components when the user has selected printer friendly mode. If the current page is in printer friendly mode, then the condition evaluates to true. Use |
|
Current page is not in Printer Friendly mode |
Hides page controls or components when printer friendly mode is selected. Use See Also: "Using f?p Syntax to Link Pages" for information about |
|
Current Page not in Expression 1 (comma-delimited list of pages) |
Verifies if the current page is not part of the comma-separated list of pages specified in Expression 1. |
|
Exists (SQL query returns at least one row) |
This condition is expressed as a SQL query. If the query returns at least one row then the condition evaluates as true. For example: select 1 from emp where deptno = :P101_DEPTNO This example references item See Also: "About Bind Variable Syntax" for information about bind variables |
|
Never |
This condition type is hard wired to always fail. It is useful in temporarily preventing controls or components (such as regions, buttons, or items) from being rendered on a page, or to prevent processes, computations and validations from running. |
|
NOT Exists (SQL query returns no rows) |
This condition is expressed as a SQL query. If the query does not return any rows, it evaluates as true. |
|
PLSQL Expression |
A PL/SQL expression is any expression in valid PL/SQL syntax that evaluates to true or false. For example: nvl(:MY_FLOW_ITEM,'NO') = 'YES' If the value of |
|
PLSQL Function Body returning a Boolean |
The body of a PL/SQL function that returns true or false. For example:
BEGIN
IF :P1_DAY = 'MONDAY' THEN
RETURN TRUE;
ELSE
RETURN FALSE;
END IF;
END;
|
|
Request != Expression 1 |
For example, the event could be when a user clicks a button or selects a tab menu. Depending upon the event, you can perform different operations by referencing the value of the This condition evaluates as true if See Also: "Understanding URL Syntax", "REQUEST", and "Understanding the Relationship Between Button Names and REQUEST" |
|
Request = Expression 1 |
This condition is the opposite of This condition evaluates as true if
V('REQUEST')
See Also: "Understanding URL Syntax", "REQUEST", and "Understanding the Relationship Between Button Names and REQUEST" |
|
Request is contained within Expression 1 |
Use this condition to specify a list of allowed requests (such as SAVE or UPDATE) in Expression 1. The condition evaluates to true if the value of See Also: "REQUEST", and "Understanding the Relationship Between Button Names and REQUEST" |
|
Request is not contained within Expression 1 |
This condition is the opposite of See Also: "REQUEST", and "Understanding the Relationship Between Button Names and REQUEST" |
|
SQL Expression |
SQL Expressions are evaluated as a WHERE clause in a SQL statement. For example suppose your expression is The Application Express engine processes the following: select 1 from dual where :MY_ITEM = 'ABC' This condition evaluates to true if a row is returned. |
|
SQL Reports (OK to show the back button) |
Use this condition for reports having pagination. It automatically determines when it is appropriate to include a button that pages back in the result set. |
|
SQL Reports (OK to show the forward button) |
Use this condition for reports having pagination. It automatically determines when it is appropriate to include a button that pages forward in the result set. |
|
Text in Expression 1 != Expression 2 (includes &ITEM substitutions) |
Use this expression to compare two expressions containing strings. Either expression may contain references to session state using See Also: "Understanding Substitution Strings" for information about |
|
Text in Expression 1 = Expression 2 (includes &ITEM substitutions) |
This condition is the opposite of To check if the item
See Also: "Understanding Substitution Strings" for information about |
|
User is authenticated (not public) |
Verifies whether the current user was authenticated using one of the built-in authentication schemes or a custom authentication scheme. See Also: "Establishing User Identity Through Authentication" for information about authentication |
|
User is the public user (user has not authenticated) |
The public user is defined as an application attribute. To set the public user for a specific application, navigate to the Application Builder home page and click the edit link corresponding to your application. A public user is a user used for multiple users. Sometimes applications have pages that are public and thus require authentication and log in. This condition returns true if the user is the public user (that is, the user is authenticated as themselves or some other user not equal to the public user identified in the application attribute Public User. See Also: "Authentication" for information about Public User |
|
Value of Item in Expression 1 != zero |
Verifies if the value of the item in Expression 1 does not equal zero. |
|
Value of item in Expression 1 = Expression 2 |
Compares the value of an item with a specific string. Comparisons using this condition are case-sensitive. For example, to verify whether the value of an item
|
|
Value of Item in Expression 1 = zero |
Verifies if the value of the item in Expression 1 does equal zero. |
|
Value of item in Expression 1 contains no spaces |
Evaluate to true if the value of the item specified in Expression 1 contains no spaces. |
|
Value of Item in Expression 1 is alphanumeric |
Evaluates to true when the string in Expression 1 contains only alphanumeric characters. |
|
Value of Item in Expression 1 is contained within colon-delimited list in Expression 2 |
Use this condition type to check whether a certain string is contained within the value of a session state item. Verifies whether the string specified in Expression 1 is contained in the value of the item specified in Expression 2. |
|
Value of Item in Expression 1 is NOT contained within colon-delimited list in Expression 2 |
Evaluates to true when the value specified in Expression 1 contains a string that lists elements delimited by colons. To check if the item
|
|
Value of Item in Expression 1 is NOT NULL |
In Expression 1, enter the name (uppercase) of the application or page item. Evaluates as true, if the current cache value of the item is not null and has a value. If not, the condition evaluates as false. |
|
Value of Item in Expression 1 is NULL |
Evaluates as true if the item in Expression 1 has no value. |
|
Value of Item in Expression 1 is NULL or zero |
Evaluates as true if the item in Expression is either NULL or zero. |
|
Value of item in Expression 1 is numeric |
Evaluates to true if the value of the Item in Expression 1 is numeric. |
|
Value of user preference in Expression 1 != Expression 2 |
This condition is the opposite of |
|
Value of user preference in Expression 1 = Expression 2 |
Verifies the value of a user preferences. Evaluates to true if the name of the user preference specified in Expression 1 is equal to the string in Expression 2. |
|
When any item in comma-delimited list of items has changed |
Evaluates to true when the value of any nonnull session state item in the list of items specified in Expression 1 has changed. |
|
When any item in comma-delimited list of pages has changed |
Evaluates to true when the value of any nonnull session state item in the list of pages specified in Expression 1 has changed. |
|
When any item in current application has changed |
This condition passes when the value of any nonnull session state item in the current application has changed. |
|
When any item in current page has changed |
Evaluate to true when the value of any nonnull session state item in the current page has changed. |
|
When any item in current session has changed |
Evaluates to true when the value of any nonnull session state item in the current session has changed. |
|
When cgi_env DAD_NAME != Expression 1 |
This condition is the opposite of Checks for the data access descriptor (DAD) that is being used in the URL to call the current page in the application and compares it to Expression 1. Evaluate to true, when the DAD is not the same as Expression 1. |
|
When cgi_env DAD_NAME = Expression 1 |
Checks for the data access descriptor (DAD) that is being used in the URL to call the current page in the application and compares it to Expression 1. Evaluate to true, when the DAD is the same as Expression 1. |
|
When cgi_env HTTP_HOST != Expression 1 |
This condition is the opposite of Checks for the value of the common gateway interface (CGI) environment variable |
|
When cgi_env HTTP_HOST = Expression 1 |
Checks for the value of the common gateway interface (CGI) environment variable |
|
When cgi_env SERVER_NAME != Expression 1 |
This condition is the opposite of This condition checks for the value of the common gateway interface (CGI) environment variable |
|
When cgi_env SERVER_NAME = Expression 1 |
This condition checks for the value of the common gateway interface (CGI) environment variable |
KA B\hXDFCYpatl7q&x%dfn0e p2pxF3y@ X@Ͱ` ~Іc 'Px`dr& @`ޢ`B8(
ߗDDP Qg@ hVhh @
|P~;7 P *@DXv|O
[/p'*X2g~~F$ `xP
F h56~,xWiYk X e ]@r ɐFhv
T7HM) Z@.
R8qpPڸ8 ww~%K` A،Xr&`Q x PR `u xD7 @M Xhȅ4V a Y
'gq+h3'
h%
@i8i
b`QU@FͶ/9T' z0u@
T|<b{
p< ~`Cjpm
` L !0Uw,N|
H
8w C
,$Iy M&$ 8 0Y]К9Y Pyb~D) ٙ MRI9 ˀ2%0 Pyؙٝ[d$rNlF.1 . M瘎ʉ# 7p :Zz
ђ '%!@`0
@ @P<`0 qA ,ڢ:=
s79W4 8^Рw bf>ɟ)N
2YxP£QR @wwp}P>`*
GНvzw>G R:28qz( )%^*p}`K0dZPPק
3ЦL f7Z @~Z5F\NTP
0 0T |0@p ʦ| nTGA
ЧV TpCz@3LsYq JѫP@=M@ pP(
:aV'ڤ
az@Q@ {0
P0/`, \=h P 1a qB N9 2
; ЁR
@{
+xk$k(*kp /[Nn`wP
ǀ
(]w\0@N[AV.p~`
@_
&`xȊP Pb1r
pW+qv{{*+{'^E[
AEpNp @@ ~`{Pw PGyyh@-p}G
pXUP[ >t˼ y0 m1$\&@ e0M;ʳ0I p<>L ($諾 p}JW`(
:
6`O
lp> б"==r|
c1,3 O` _;0ڽĉnj p
Py
C0ʮ b f`js00
v. @{o 1`ip pf !sm2ڪM gCt46J[9 T >dP; ܝ ~ F0j N2n^5L:;n
e?\
HnH.i"@һ| P up#ӋK>4|ȟ
G2H`M. 5~GA
DPtP z N 4 zn% /Q.5mp 7}f ! ?|[DbG߮= #?Pz^x_``0Gqo?wqoNۥwN?M :NP
p
^l/Co ڛ9!y!P:3 Q FĬ
~X,.^
@QIOJ+9MP
x0 M D0 ? 7U W`65D[ V.Ҍ?.q:zQA a5
͚=}Th(
ЃMG4bTU^JuAMYn8# (cŋ8(HqA
h !
ТB gŽ.z\9^~{% Fp a@@ ^1
D%8E@6h%hJE q8 (b a5:X>;Гs7@SC㷔kڻ=!p(x.A^*jpP nb@;1 8 `
S#p)+Ap/Уl;/B;S6c;kpXx z1("n ȟ `p Ah HpD;h [?# (1" 04(ܶ2,-.d7;5>5O
!-Y,ec'W0= `%5'(Iȅ1XpZpt c@QJlmnobE,@@.\ CxSqW'?Bk:>p~pD5xL PL QT7;;?x yʐˠG{ P lǍHoLJ
={3 Jl3 ȞI L#`ɐ,ǭ;QLDŽDI,JHsɩ H(«lQHH[`M$Kw臧
?/4EvdH,L6H 4($ Eh 0 SPq&pX@@$0> )0L5p
R\DžT6ʦ˽\ & HS''H8OL!yȃ'
$O@'8L ,9Rx8x
DX_X>( ă$G3O@RTGLI|\866, X"Hs
h:)ޤ 5[/9HH4 MCX lL5@N`O0cL> M$\ Y$ ȣ
%*@
+h
2l!Ĉ9W?nDuqpHP$,Yp?Ll%̘2gҬiDGp)fF2I%2)"qD)ԨRRj?,h 6L Ax b[3)JJrҭkB K7 Z
fM1 `` 2/̃8ar
50]H&ǚi* /ٺw.=6=DDڑX8J\ Sַs X"a 9j ٲĎ>QqC f1 , (1.b0|=dvZxKb ܂4
ӀGE!-8 C@
Ҩݭ"=I) Ey$I* P F" TZ hL)]e`P 0,+ &9uy'yyCAi)*@'$<
v
F`5t:3IZ*jiJ|gJ
J!$hJB*) ;PKf/ / PK 6(A OEBPS/img/shared_comp_icon_2.gifXGIF87a |||ƴμʼ¬̴´䔪̌ƴԬƬ¬´ĔԜ||䔪llll, @ 0l8QXDa 5I G
#P,9-h6)ʠ#!&B'
s]uKE% !"E
` oDb x EFwys͋ ȽFLgN
Xf0p` p%,!A ;PKaq(Y PK 6(A OEBPS/img/ir_srch_col.gifR!GIF89a k 9s k k J{!!1R91c99s99{9B9JBBBBJBB{BBJBJJBRJZRJcJJcRJcJkJJkJJRJRRsRRsZR{RRZJZZZZZcccZcccccckccccck k kk kZkkckkk kkkkkkkkskk{kkkkkkkkkkks ssksssss{{{s{{{{{{{{{{{{{{{{ބ{{ތΌƄ k k kkkk Ɣ֔ƌޔ ƜΔΜޜΥk kkkkkƥkk{{ ƭƵέｌƽƽνֽ֭ Ɣ ƔkƔ{ƭkƭΥΜ֭ޭk{ޭsƔΥޭΔ֭ޭ ! , H*\ȰÇ#JHŋ3jȱǏ C Iɓ(S\ɲ˗0cʜI͛8sɳϟ@
JѣH*]ʴӧPJJիXjʵׯ`Ê KٳhӪ]˶[)ݻx˷߿ LÈ+^̸zZ̛˘3k̹ϠC MӨS^ͺװcsʲsͻ Uʈ+_μУ6^Unjo֬Yν>v<OI+OϿ (-Gz͂ 6M5Byɣ yRYW0ka mB!hJe"g " 4h$9爦L'Az aT0l 2"DI'dg)Hԋe9R8 +dʙ̑?\j
Q3 !Zxc0$It ܑOݓ$zy %.2*楖A)ܤ!N6tfg$ gD$D" }D`Fp:e蕝"%0[W* B5aJOGd)Ԏ)jy3D phTc6 (|Eo6+i%2&,.YBa۳ )Ŕ0n=xZ 0+E0 C/S
")Cnv٥ \)g Kl3 @Kdb&c3 @m?#qgf KҊy+H@ 4K 5d72ㄭ9.|3d\,\ʧ*4Ûi{P=,椓nrF`3+a
A-Ap@ARrF፝5X s\8f9r"scN CN @4K ?"9Yfn9 = i:a @C>@X 'x3' 27e~ "N S,|=0|{WCũ >=耳Mbʀ
%ҏi
'~߾~ӏ `-РAH ,Ё `(AF7A
N`-@$`Ap LaL `8̡' ! >HD#:1ITD& ;- @2 u08 \c1n0n`8.~k|]=q!
mDL" F`$'IJZU!m Nz (GIR*;M,eJ`
ȥ.wK^n0IbL&1_`+ Ќ4IjZ̦6ɃmB|7Ir.0:v Kx⑇^y x~zk^:UXa7 _?}Շ}ݧ}Uzɯ?緟@Oi ?.Ё,`@Blh ~Ou;
R0Bp)(!
OBЅ&
cX0/x l _(C 氇;!
m(ш:D ;|+D*M>& c8F2ьgDK,&_Lc 8G3щ{# 4ڱ# 9HZ ·d$%9IJVҒ F^ғ%%3I@v2De%GG=%,WyHDE`[B ]e09LaeHK<4f49d.SxΔf6l*&7ũMrқ ӝg<9Oz :O~f NԠ(:7 ԡM(3..1@ 2v@D:RF &@JUR DiLc: tT(lQjԣ )IzRԨ/uLejӚTFѐu(=QYҤ*Li@-UN5UjQUԫ_iS:QTThYT
ժ[TvgjV%Z.E\_÷2_%R5aDԳ+dS:ڭ´3lj3S_) \WVW,[Kk` (
mrKYӞύ.XG]N h]t1G^Zv'k6x{ze %}^vm}+X _
X>M0l`'\ {]p~^ֻ#bBvme1^w<)0P8n NrC]x}c+[$Cp)d9F,ˬ2Pa*[e dn=/*^M1hkίI7.q m^uEj' AlElidFG# :f E@e=kZZ ڬqm |j+lkb״{
_kխu\Zv4g{>6if8ثIYXk 8Ȼ`Y6 N-Se^q[{x䷻my6[#fx ^S }BqZ"7<|43CAypWr\Z.ݘp|.k7={\7HUrԾAVO| M݀
&pUށ]d7;7v, {x=MպxG\xg|{tÝ[oR7C $ G}U
h _}s>f:;m^?=_߷ ߴfQ#O> {|5/g@Gտ~]`Ձyk]gw;+ӿ?5@n,@
e+ t::(2w[2;@ A+A@{@}" A3A78Gk:A| )~&\'(9e˶!A
%B'/)$*9Bs ..d/C #C3=RC/6|õC@$z8r9B`<2ĉ@āS
F 3HԈIl+L BĢKD+C3tD#+s7EW9! @cXEa EEE_#`BZ$F( DԺɫΰںڮ:9:||!xZ!+u~ *ʹdڥZAwz{Ud9 ۱ 7";]S&3(")10:2$Ѕ/
*<ݺṒJM/ Ч
ꜝ
2y;)ڨ:㩠_ګ~H7 ʳn衵:Jj%*zKSz-{PKjyڴ]iqꋌ 3m+6 lM? W
o}0| }|~q ~ KyMg!%70* (%1X}[ n7 7'W
wYx Ё!~N(~( a`Z(V8/c S
.rÇ; 'W?W7PG( gTU(b([HX Yh/(x؉h
+p 5[shWw~ꇄyW腊X8ȉ$ȅ'8}ֈsX~ @xvǨh茉ȎȎk
p9; pK6!|0PPWј3xx8ȸ8*h!ّ )z 0 7~͘hdH!؈;ieX#c98N>ƴ{(Ղ]D`b9dYfyhyNZ9M\)}SnQQqsPkRYx `~i)Q ؗK(vp٘T0yPRɘ x!p Y К yI9P9WiiYYIy0K
y ٜҹY9
驘ɟ幟9 ٛٹO|I 陘JiٝI
*ʚJ|JZ9+Z.Z
%O0JH*pq ڣ>ʣ Y&oQ: Iڤ:9ڙ١hjԚpr:tZvzx
`|ڧ駀4 ڨPzM:کZNꩤJ:
ʗZ唩:*J ʫjƄ1ʨڪϪ˪*DʊJjzJʭ:*L蚮:*:z)yTڠ
ʞXڞAz;ډjj:{ { {&'J٢ Ezʱ7۱*|1'}Q
}4By2:JjY 0 A/yMBP1QdjXTU5Pc{ZU&"aM?"PdL%XtT H W!c?a .`(D @VR`I%!8##G1E DX%kpyP.0V\{*#] 0 C '(]q 9nTDgegʢO `pD
:a(9V 8/AQ$ T #A%
h.1e @2Q Uj)T%5VLBV%
C6_2iV`jj xxn|ilTyReTD7]7=iRђuLHftA3g ~~_
dAQ]h;u-4|^.\`N R[ۑjՈdv/]T*>.}wm ;Hǝ>@
i WXfw1m|[ |;סf0G}#2mxBZŋK!t5r]l{[v[k`
T=!Ȯ6ZB7nZ|3Εjי6ŧNH1V'_
kcSz!jQVhOpvϻa);Ox=Ȇ;'OWL7{Ǽ#5қ}Qֻ^A CЁϽw?|:XbX$mO;ЏF.xS?= ?>R]^و}8
CK? nuG
MHXN Q`
XH(O (x {!O#txp4
Z6Z4ă>XHDB5=h5 EI0,p`p IPHӀc(HRtTlSMoHnXHjLsHuxw2xG@{xIO4O9' &4d qTNGS
XV|ԉhH1:I9` 2 x9@x aHIGe8
IkEU0%7xFtzČ(HO6 `"`R8 pyč䍯HhGـ-xIP &pȋd ,'pTĎx
g0
g7
t:pPPfP
ywpTyH
yG 鐂tdP8Ydh+VԒ$HH/釀Ddky [c@d0bp둕M_uĔMiH`H S
MpP{@}0 ّ
! ЗP `4 (1SU;xOI(Yd G?8x
@xdTCKɔK)d %u$Yipx0 Qd &y'`*yYS{ȐGG˹9pf0p ruix{ٗ
@
0 [
pٜ>5rg0ˉ
aV:YP P
Ϙ
)ЉI "*jšH9kE..ٛi"8*YHi>
@gyɢMY R
Yz鹞|ƤXykiOYʋOHsHoPИk:b:נ0IiI:zZ{P)Y: [d"L Ʃ>
@ c G) f Rq9YXz \I +ʢzyLcp: O@f`v`~jfx
wrа`
a'zګ|ԩ
Jɫ)*W{'0L
" k@Z&,b !},:::Jʗ})
ZӺVl9
b*J[b^6 ʮ~YZۮ0 Z;Jگ L+N[Z[Yv{xz|۷u; G:"cMpT2
p
$˪k =5c:KT
zjBۥъ
* ZBPqj~Y
̫]kQZrcR~u
iv;ܚMKM`[+{p+$ +
{ p>
RK{K:9:rZ[z 19
,`ccUQ 9:Лfj |h@ -ؾ8fK XZ\^`Ű0 X <ń+tLZ [xr,nj20<%
>:ǂ|'#+|gYŶ :`JrгVYڬ#iت·뫆1, 0<`~0Y;}î [+dp <\|
`lkȡTM pڼll k#* ]( , L ,K k 0L#<[ IL(VҬL &EqÐʰԠ ҳú|A:<:ݽ6:}- Ԭ [NP R=T]P=P0\G G[
0
j],\j
̵
-GI *Y=@ #wP G9) `ө P %94M#T0۴]۶}۳
ɜ`} j졄Miʽ 0
kPKفmGc}(Vfix ";ܪ"p&`
pUM8 0 IMgpܵ)Ӛ
$Ь zψ
-P 2 rKhV3ʟ ̰
ӊ ̠ >L
y <>@ㄚĈ@.,`+ T^V~XZ\~ ` k
ΔLᣬO:
p xp t^ Lo[@{mu^@q~o Mw4؈~٠\ܑl<>o9^q +" <ٟ ڳ p >ؠ7q` DM ު . >^nPȰ dپ.l~ 譈0tͪǁ`^銾G?}r钜t) C+. .0_O>Ȟ
켲̞ ڨ:- mpT@ nώjN~]2o fh]@ - N~+2Yp { cI.xD鏯P-p ^$ )?/ů^8o@ɛ)P @
@J3miAXu /1y^ ?_ q _Iy?p( H"9@ :́
D-^ĸ FOH%Ql:L f$ԧO%
c¾_룙,>JPOBr m/ @Z BSёXr:
A
4(Q2(8E J@\@ *"@JrR@ | ф\уjQѺIK=PjKCǝڭ"D1/Aѐ76<%8:U [BȪӊ>* C+A*B-H.T4ӂ{>=ܩ*Hz?= To01-
2YLS)찕(kQQU<*IеUU:ӓY}4lbzDP/z˔M{!jdElLDm 7#
U5e GZqɘHvmot-9a8eԓd/a<"ij\2j2HGkƸ uFn- X}=*y5U"8l(l>
ΒIϙ ƒ8١L} * IE44lyH[SYHTٰs٥M+KY kY\ u\GsmUz*d=) *P[+- !sE ?1ĪzY+m6)Jy3SJ,aʱ8[ (J|sJݻ --F
ܹEKXX#$ۯ@9hy]0K֭5 X]ڃ;$^ ]d^
52x[78`owlo"cgy8~!褏nwX$:/ߢKN./abaD# \_3W_}YdڟR|}>h ZhD곿~>?O3 jML O焤5p]Nh<*Pa ̠1h^5
9rJ "Fg. uT*
[IPwC RpVHD"z0
Q`$n
eQٞ`!#g=̢U
0dZT
m&'5 h4#ueȈ p 1r@X2 -ِ"*Ε
KQ F*y
Kj?$+, Q#L%<2V5`)Z6DD^ 0IbFQD J2f:D1IjZ̦6nz 8IrL:vM4Iz4/~@ AІfs66*rH=jJt p h5x)Lc:x!F͵T9)~HPGHNM !TS}^` `! ;PKw l g PK 6(A OEBPS/img/app_attribute_tabs.gifGIF87a{ Ĭ䤦tvt̤|~|伺Ƽ̔̄|$V>tN|ldLrĴLnļ̴tT~̤μČ܌ʼdd\\ttԬllll||촲 , { łݬ
o*\ȐW#JH⸇3jȱV? IIy!u50ò˗0cʜI\+kܹ歜<
ɣHJyK'PJJիXz)C˩/`Ê Kٳcr۷p
VݻxB%+ LÈ[D˅X|1`L˘3k\cT$o Mӕ;˺H8ɒ۷t!KhOoȓ+BܵaǺ6ر[quk{ӫL;JUUF@& f$8z bѠi؊)XكaYn8YE߈$3+t`]~ bA+x97c=⇥ z@Nb-b*[v%~_~ebMD ;Yd i!@hfhkfo9l'JRf'6|0Ɵ^1*@tcffꄩiꦃJgz량b
Qa/r%rib"6j*CTs랽~ h&풸뮽bء
ko5a͂z
*ІZص i
ù[:n6+ @b9 pyB+ȩм+_1!ҿ@:1[pW-/ǬXj1H'_ͪCt)!,}k-ص\ Hƀ&:<^ȅ/|h·٦*1f-H4^s+lgn{R.6깷'_JHW v[P