||Oracle Tips by Burleson
The Session State process is used to modify values
in the session state for applications, pages, or page items. They are
also used to modify the session state for Preferences.
During normal use of an HTML DB application, it
will become necessary to clear the session state for one reason or
another. For example, if a four-page wizard is used to create an
employee record, the session state for all page items on all four of
the pages must be cleared.
(removes all session state for listed
applications): Will clear session state for all page items in all
the applications listed in a comma separated list. If two
applications that work together exist, like HTML DB does, and the
cache in both apps needs to be cleared, this is the processes to
(removes all session state for current
application): Same as the item above except this only clears the
session state cache for the current application.
: Clears all session state for the current
session id. This can be valuable if two HTML DB applications that
navigate back-and-forth between each other exist. The same session
id between both applications will be used. This process type can
also be used to clear the cache for all applications this session id
: One the most common session state processes used, it
clears the session state for page items. The page items being
cleared do not have to be on the page where this process exists.
Since all page items are accessible on all application pages, this
process can clear them. The page items are separated by commas to
clear multiple items.
: This option is useful when starting a
wizard consisting of several pages. This option easily clears the
session state for all the items on each of the pages listed.
: This process will not only clear the
preferences, but it will remove them from persistent session state.
This process should be used carefully. For example, if one logs in
to HTML DB with username EASYDEV, and also logs into an application
that is being developed with the same EASYDEV username, using Reset
Preferences will remove all preferences. Therefore, all settings
such as preferences for the View, either Icons or Details, or any
sorting for HTML DB reports, such as in Application Builder, will be
lost. This happens because the preferences are stored based on the
username for the session.
: This type of process is what is used to
set the user preference when the page is submitted. The default
value can then be set to the select list to be based on the value of
– This is almost the
same as the item above. The difference is if the page item has a
NULL value, the preference will not be changed.
More information regarding Preferences is included
in an earlier chapter of this text.
above book excerpt is from:
Oracle Application Express
Web Pages with OAE
Michael Cunningham & Kent Crotty
Download your Oracle scripts now:
definitive Oracle Script collection for every Oracle professional DBA