Skip Headers
Oracle® Application Express Application Builder User's Guide
Release 4.2

E35125-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to current chapter
Up
Go to next page
Next
PDF · Mobi · ePub

7.8 Understanding Application-Level Items

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:

7.8.1 Creating an Application-level Item

To create an application-level item:

  1. Navigate to the Workspace home page.

  2. Click the Application Builder icon.

  3. Select an application.

  4. When Application home page appears, click Shared Components.

  5. Under Logic, select Application Items.

    The Application Items page appears.

  6. To create an application item, click Create.

    The Create/Edit page appears.

  7. For Name:

    1. Name - Enter a name for the application-level item.

    2. Scope - Options include:

  8. For Security, Session State Protection:

    • 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.

      Note: If you must set this item's value in session state using Ajax, then an Unrestricted protection level must be used for the item (for example in Dynamic Actions, Set Value, Page Items to Submit or Cascading LOVs, Page Items to Submit).

    • 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 Only (Save State=No)

      • Display Only (Save State=No)

      • Stop and Start Grid Layout (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.

  9. For Build Option, Select a build option for this component. Build options are predefined settings that determine whether components within an application are enabled.

  10. In Comments, enter any notes regarding this item.

  11. Click Create Application Item.

7.8.1.1 About the Application Items Page

Once you create an application item, it appears on the Application Items page. You can customize the appearance of page using the Search bar at the top of the page. Available controls include:

  • Select columns to search - Resembles a magnifying glass. Click this icon to narrow your search. To search all columns, select All Columns.

  • Text area - Enter case insensitive search criteria (wildcard characters are implied) to search for items by name and then click Go.

  • Go button - Executes a search or applies a filter.

  • View Icons - Displays each item as a large icon. To edit an item, click the appropriate icon.

  • View Report - Displays each item as a line in a report. To edit an item, click the name.

  • Actions menu - Use the Actions menu to customize the report view. See "About the Actions Menu".

7.8.2 Viewing Application Item Usage

You can view a list of where application items are used by clicking the Utilization tab at the top of the Application Items page.

7.8.3 Editing Application-level Item Attributes

Once you create an application-level item, you can edit it on the Create/Edit Application Item page.

To edit application-level item attributes:

  1. Navigate to the Workspace home page.

  2. Click the Application Builder icon.

  3. Select an application.

  4. When Application home page appears, click Shared Components.

  5. Under Logic, select Application Items.

    The Application Items page appears. See "About the Application Items Page"

  6. Select an application item.

    The Create/Edit page appears.

  7. To learn more about a specific item on a page, click the item label.

    When help is available, the cursor changes to an arrow and question mark when you pass the cursor over an item. See "About Field-Level Help".

  8. Click Apply Changes.

7.8.3.1 About Navigation Alternatives

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.

7.8.4 Creating an Application-level Item that Functions as a Global Variable

Large applications are often separated into several physical applications that reside in the same workspace. These applications often share session state by configuring the same cookie name in each application.

Another requirement of this type of architecture is the need to share a few global variables. While the number global variables should be kept small, global variables function as an effective means to facilitate communicate between the applications. For example:

  • Properties of the current user (such as email address, employee number, and so on)

  • Current company in a multi-tenant application

You can create a global variable by creating an application-level item with the same name across all applications and setting the scope to Global.

To create an application-level item that functions as a global variable:

  1. Create an application-level item with the same name in each application to share session state.

  2. For Scope, select Global.

  3. For Security, Session State Protection, select Restricted.

To learn more, see "Creating an Application-level Item".