Database Reference
In-Depth Information
APEX Application Exports
Like the files in the shared component section, an APEX application export is easy to
acquire. The interface includes a process designed to generate scripts for re-creating
APEX applications.
It's important at this point to know what an application export includes and what it
doesn't. We've already discussed the fact that the underlying database objects aren't in-
cluded, and neither is anything that is uploaded to the Files section of the shared com-
ponents. But all other shared components are included in the export file.
It's worth mentioning that all configured and assigned shared components are in-
cluded in the APEX application export, whether they're being used by the application
or not. For instance, there can only ever be one authentication scheme current for an
APEX application, but more than one authentication scheme may be configured and as-
signed to the application. The same is true for user interface themes.
Although this isn't strictly a problem, it's good practice to delete any shared com-
ponents that aren't being used by the application so that the size of the application ex-
port stays as small and manageable as possible. Most shared components provide a
utilization report so you can see whether they're being used.
The application export capability is located on the Application Builder main page in
the Tasks menu at right on the page, as shown in
Figure 10-10
, or on the application's
Edit page. Both options navigate to the same location.
Figure 10-10.
The Export option is located in the Tasks menu at right on the page
