Import and Export Applications

You can export a visual applications as an archive to your local system that you can then import to create a new visual application. You can use the import and export mechanism to share application sources and to move applications between instances.

Export a Visual Application

You can use the Export action to download an archive of a visual application and its resources to your local system. After exporting the archive, you can import it to create a copy of the application and share the archive with team members.

When you export the application you can choose if you want the archive to include the data contained in the application’s custom business objects. Some information, such as credentials for external REST end points, is removed when you export an application. This information needs to be provided after the archive is imported.

To export a visual application:

  1. On the Visual Applications home page, open the Application Options menu for the application version you want to export and select Export.

    If there are multiple versions of an application you must use the Options menu of the version that you want to export.

    Description of export-application.png follows
    Description of the illustration export-application.png

    Alternatively, when a visual application is open, you can choose Export in the application’s options menu in the toolbar.

  2. Select the export option for the application.

    You can choose to include the data stored in the application’s custom business objects when exporting the application.

    When you choose to export the application with data, the archive will include a json file (entity.json) and spreadsheet (entity-data.csv) for each custom business object. The json file describe the business object and the spreadsheet contains the business object data. If you choose to export the application without data, the archive will only contain the json file describing the business objects.

    The archive will always include the data for any business objects that are identified as containing Application Setup Data.

The visual application and its resources are exported as an archive file. The archive is saved to your local system in the location specified for your browser’s downloads.

Import a Visual Application

Use the Import action to import an archive of a visual application, for example, to create a new application from a shared archive.

To use the import tool to create a new visual application, you will need an archive file of a visual application that was previously exported.

You can also replace all the source files of an existing visual application with the contents of a visual application archive using the Import command in the Options menu in the toolbar of the existing application. When you click Import, the Import Resources dialog box will open where you can import a ZIP archive. If you select Delete existing files and resources in the dialog box all the files and resources in the existing visual application will be deleted. The resources are imported into the root directory of your visual application. You might want to select this option when you want to replace all the existing files with new files to prevent duplicating files.

To import a visual application:

  1. Navigate to your Visual Applications home page and click Import.
  2. Click Application from file in the Import dialog box.
  3. Drag your visual application archive file on your local system into the dialog box.
    Alternatively, click the upload area in the dialog box and use the file browser to locate the archive on your local system.
  4. Enter a valid application name and ID in the dialog. Click Import.

After you import a visual application, you might need to provide additional details such as service credentials in the new the application. For example, if the application you are importing contains Process definitions, you will be prompted to specify an existing Process application that contains all the process definitions required by the application you are importing.

About Classic Applications

Classic applications were created in earlier versions of Oracle Visual Builder and used a structure that is not compatible with the visual application structure now used in Oracle Visual Builder. There will be no additional feature development work to support classic applications. If you have any classic applications, you should migrate them to use the visual applications structure if you want to retain the business objects defined in the classic application.

Some older Oracle Visual Builder instances might still allow you to manage classic applications, but newer instances will not provide the tools for viewing and managing classic applications. If your Oracle Visual Builder instance supports classic applications, you can export your classic applications as archives and then import them as visual applications, but the UI of web and mobile apps cannot be migrated. Importing a classic application archive only preserves the details of business objects.

Import Classic Applications

You can use the import tool to create a new visual application that contains a copy of the business objects and data in an archived classic application. Importing a classic application will not recreate the pages in the application, and the credentials and settings used in the application are not imported. To import an archived classic application, the archive must be exported using the most current version of Oracle Visual Builder.

If you have an archived classic application that was exported using an earlier version of Oracle Visual Builder, you might need to import the application as a classic application and export it again as a newer archive before you can import it as a visual application. An archive of a classic application created using earlier versions of Oracle Visual Builder will not be recognized when you try to import it as a visual application. You will see an error message that an archive is “outdated” if you try to import an older archive of a classic application.

Description of homepage-importapp-warning.png follows
Description of the illustration homepage-importapp-warning.png

You should contact your service administrator if your Oracle Visual Builder instance does not support viewing and managing classic applications and you need to import or export a classic application.

To import an outdated archive of a classic application:

  1. Open the Oracle Visual Builder Home page.
  2. Open the Application Switcher menu and select Classic Applications to switch to the Home page for Classic Applications.
  3. On the Classic Applications Home page, click Import.
    Use the Import Application dialog box to upload the archive of the application.
    Description of homepage-importapp-dialog1.png follows
    Description of the illustration homepage-importapp-dialog1.png
  4. Upload the classic application archive from your local system.

    You can drag the archive from your local system into the dialog box or click Upload a file to navigate to the location of the archive.

  5. Type the application name and application ID. Click Import.
    The Application Name and ID are automatically populated based on the archive, but you might need to modify the name and ID because they must be unique in your identity domain.
  6. Open the Application Options menu of the application you imported and click Export.
  7. Open the Application Switcher menu and select Visual Applications to switch back to the Home page for Visual Applications.

You can now import the new archive as a visual application.

Description of homepage-importapp-classic.png follows
Description of the illustration homepage-importapp-classic.png

When you import the new archive of the classic application, the dialog displays a warning message that only the business objects and data in the archive will be imported into the new visual application.