Databases Reference
In-Depth Information
Build Status Override : Lets you select which build status is the default when the application
is imported. The default is Run and Build Application, but you may set the status to Run
Application Only.
Debugging : Dictates whether the application is installed with debugging enabled or disabled
by default. Debugging is useful for applications in development. However, as a best practice,
you should turn off debugging for production applications to prevent users from viewing
things that may only show up while in debug mode.
As Of : Allows you to export the application as it existed a number of minutes ago. For this
feature to work, Flashback Query must be enabled at the database level. The amount of time
you may flash back is controlled by the UNDO_RETENTION parameter at the database level.
although you can select default values for the settings in the export application section, it's important to
understand that they can be overridden when the application is imported. at this point you're merely setting the defaults
for the import.
Note
In the Export Preferences section, several options allow you to decide what is included in the application export.
The following options are available:
Export Supporting Object Definitions : Dictates whether any supporting objects that have been
uploaded are exported with the application. See the “Supporting Objects” section later in this
chapter for a full description.
Export Public Interactive Reports : Dictates whether report definitions saved by end users and
marked as public are exported as part of the application.
Export Private Interactive Reports : Dictates whether report definitions saved by end users and
marked as private are exported as part of the application.
Export Interactive Report Subscriptions : Dictates whether user subscription information for
interactive reports is exported as part of the application.
Export Developer Comments : Dictates whether any comments developers have entered
against APEX components are exported as part of the application.
Export Translations : Dictates whether translation mapping information is exported as part of
the application. Translation text messages and dynamic translations are always included in
the application export, regardless of the setting chosen here.
Once you've chosen the appropriate settings, click the Export Application button to produce the application
export. You're prompted to save it to your local machine. The export file name consists of the letter f followed by the
application ID, with a .sql extension. For example, an application with an ID of 9238 is named f9239.sql .
The downloaded file contains a large script that defines all the contents of the application built in APEX. With
the application pages are the shared components, including authentication schemes, authorization schemes, themes
in the application, UI settings, reports, and so on. This script can, in turn, be imported into the same workspace, a
different workspace, or even a different server.
 
 
Search WWH ::




Custom Search