6.2 Understanding Page Types, Features, and Settings

Blank

Create a blank page as a placeholder. Once you create the application, you can create regions on the page in Page Designer.

See online Help when creating this page.

Calendar

Generates a calendar with monthly, weekly, and daily views.

See "Creating Calendars"

Cards

Create a page which displays cards.

See online Help when creating this page.

Chart

Create a page which displays either an area, bar, line, or pie chart.

See "Creating Charts"

Dashboard

Create a dashboard page with multiple charts.

See online Help when creating this page.

Form

Create a page containing a form which enables end users to maintain data. Select the table on which to build the form and specify whether or not to include a report.

See "Developing Forms"

Interactive Grid

Create a page which displays as an interactive grid (similar to a spreadsheet). Functionally, an interactive grid includes most customization capabilities available in interactive reports plus the ability to rearrange the report interactively using the mouse.

You choose a table or view on which to build the interactive grid, or provide valid SQL statement which returns distinct columns.

You also specify whether or not it is editable. In an editable interactive grid, users can also add to, modify, and refresh the data set directly on the page. 

See "Managing Interactive Grids"

Master Detail

Create a master detail form that enables users to query, insert, update, and delete values from two related tables or views. You choose the tables on which to build the master and detail regions. Master Detail options include:

• Side by Side - Create a single page master detail utilizing side by side layout and report regions with modal edit windows. The left side contains a master list to navigate to the master record. The right side contains the selected master record and the associated detail report.

• Stacked - Creates a single page master detail with editable interactive grids. Users select a row in the master grid to update the detail grids.

See "Managing Master Detail Forms"

Report

Creates a page that contains the formatted result of a SQL query. You choose a table on which to build a report, or provide a custom SQL SELECT statement or a PL/SQL function returning a SQL SELECT statement. You then choose the report type (that is, (that is, Interactive Report or Classic Report).

Select Include Form to include a form page for creating or updating records.

See "Creating an Interactive or Classic Report Using the Create Application Wizard"

Timeline

Create a page which displays a timeline. Especially useful for displaying updates.

See online Help when creating this page.

Wizard

Create a collection of pages to be used as a wizard. Generally wizards are used for entering data across multiple steps.

See online Help when creating this page.

Multiple Reports

Create multiple interactive reports based on the tables you select.

Not applicable.

About Page

Include an About page in the application which displays the application description.

See online Help when creating feature.

Access Control

Incorporate role based user authentication within your application. Users can be defined as Administrators, Contributors, or Readers. You can then readily define different access to different roles for various components throughout your application, such as pages, menu entries, regions, columns, items, buttons and so forth.

See "Controlling Access to Applications, Pages, and Page Components"

Activity Reporting

Include numerous reports on end user activity for your application. Determine the most active users, the most used pages, the performance of pages, and errors raised, to better understand how your application is being utilized and areas for improvement.

• Top Users report

• Application Error Log report

• Page Performance, activity and performance by page

• Application activity by page report

• Page Views detail report

Not applicable.

Configuration Options

Enables application administrators to enable or disable specific functionality within the application. This feature is useful if you select features that need additional development effort before they can be used by end users. This feature can also be expanded to application-specific features. If developers define additional build options and associate them with specific functionality throughout the application, then they can be added to the configuration settings for administrators. For example, within the Customer Tracker productivity app, administrators can turn on or off such features as Contacts, Data Loading, Geography, and more.

Not applicable.

Feedback

Feedback provides a mechanism for end users to post general comments for application administrators and developers. The posts include useful session state information to help developers determine where the end user sent the feedback from.

Creating Feedback:

• Creates a Navigation bar icon which users can click to leave feedback.

• Creates a report for viewing and updating feedback.

• Captures the application and page ID, feedback comments, date and time, and user information.

See "Managing Feedback"

Theme Style Selection

Enables administrators to select a default color scheme (theme style) for the application. Administrators determine whether end users can choose their own theme style by enabling and disabling Allow End Users to choose Theme Style is enabled.

If enabld, end users simply click on the Customize link at the bottom of the home page and select from the available theme styles. For example, users with visual impairment may prefer to utilize the Vista theme style which has a much higher color contrast

Not applicable.

Application ID

Unique, numeric identifier for your application. This field contains an automatically generated identifier by default.

Not applicable.

Schema

Select the database schema which stores the database objects you want to use in this application.

Not applicable.

Language

Select the primary language for this application.

Not applicable.

Authentication

Select how you want users to authenticate into your application.

See "Establishing User Identity Through Authentication"

Advanced Settings

Set additional definition, security, and globalization settings. These settings can be applied when creating the application and can be edited post application creation.

Tip: To learn more about these attributes, see field-level Help.

User Interface Attributes:

• Apply User Interface Defaults - Select Yes to have attribute defaults based on existing User Interface Defaults defined within this workspace.

• Copy from Existing Apps - Select Yes to have attribute defaults to be based on existing Form pages, based on the same table, in current applications defined within this workspace.

• Table Prefixes - Enter table prefixes currently used by existing database tables on which pages are based. These prefixes may be different from the framework table prefix (for database objects created by this application when generated).

Description:

• Short Description - Enter text to be displayed as a subtitle, under the application name on the home page.

• Description - Enter text to be displayed on the About This Application page, accessed from the help icon in the navigation bar.

Settings:

• Add "Built with APEX" to Footer - When set to Yes, Oracle Application Express adds the text "Built with Love using Oracle APEX" to the footer of every page.

• Version - Enter the application version. The version is displayed by default on the bottom of each page.

• Logging - Determines whether or not user activity is recorded in the activity log. When set to Yes, every page view is logged, enabling an administrator to monitor user activity for each application.

• Debugging - Determines whether debug mode can be enabled using the browser.

Security:

• Deep Linking - Enables or prevents deep linking to an application.

• Maximum session length in seconds - Defines how long (in seconds) sessions can exist and be used by this application.

• Maximum session idle time in seconds - Defines the time between the last page request and the next page request.

Globalization:

• Document Direction - Set document direction left-to-right or right-to-left.

• Date Format - Determines the date format to be used in the application.

• Date Time Format - Specify the date time format to be used in the application.

• Timestamp Format - Determines the timestamp format to be used in the application.

• Timestamp with Timezone Format - Determines the timestamp with time zone format to be used in the application.

Not applicable.

User Interface Defaults

Set defaults for user interface settings, such as rows per page, and add list of values definitions. These settings are used when generating components within the application.

See "Oracle Application Express SQL Workshop Guide"