Exporting Application Components

You can export shared components or components of a page on the Component Export page. You can use this wizard to:

• Export shared components or page components to another application or workspace

• Back up a component before editing it

• Create an export to function as a patch to another Oracle Application Express instance

To export shared components or page components:

1. Navigate to the Component Export page:

   1. On the Workspace home page, click the Application Builder icon.

   2. Select an application.

   3. Click Shared Components.

   4. From the Tasks list, click Export Application Components.

      The Component Export page appears.

2. Click the following tabs and select the components to be exported:

   • Components displays shared application components and entire pages. Use the navigation bar at the top of the page to search for components. See "Working with Shared Components" and "Exporting Build Options or Build Option Status".

   • Components by Page lists components of the selected page. Navigate to a specific page by making a selection from the Page. Click Check All to select all components.

   • Application Attributes displays application attributes. Press CTRL or SHIFT to select multiple attributes. See "About the Edit Definition Page".

   • Build Option Status displays available build options. Use this page to turn build options on and off. See "Exporting Build Options or Build Option Status".

3. Click Add to Export.

4. Click Next.

5. On Components to Export:

   1. From File Format, select how rows in the export file will be formatted:

      • Choose UNIX to have the resulting file contain rows delimited by line feeds.

      • Choose DOS to have the resulting file contain rows delimited by carriage returns and line feeds.

   2. Use the As of field to export a page as it was previously defined. Specify the number of minutes in the field provided.

      This utility uses the DBMS_FLASHBACK package. Because the timestamp to System Change Number (SCN) mapping is refreshed approximately every five minutes, you may have to wait that amount of time to locate the version for which you are looking. The time undo information is retained and influenced by the startup parameter UNDO_RETENTION (the default is three hours). However, this only influences the size of the undo tablespace. While two databases may have the same UNDO_RETENTION parameter, you are able to go back further in time on a database with fewer transactions because it is not filling the undo tablespace, forcing older data to be archived.

   3. Click Export Components.