Importing and Exporting Applications and Snapshots

You can import and export applications and snapshots as EXP files. (Snapshots are exported as normal applications). With this feature, you can share applications and snapshots with other users directly through the file system.

Importing an Application from your Local File System

You can import an application that was previously exported and saved as an EXP file.

To import an application:

  1. On the Composer Home page, click Create, select Import, and then select Import Application.
  2. Click Browse, then select the application file (.EXP) you want to import.
  3. Enter a name for this application.
  4. Select the space where you want to store your imported application. Alternatively, you can create a new space for the application.
  5. Click Import.

Exporting an Application from the Composer Home Page

Exporting an application to your local file system enables you to share applications. You can export an application from the Composer Home page.

To export an application to an EXP file:

  1. On the Composer Home page, find the application you want to export.
  2. Click Options Options icon, then select Download Application.
  3. Select Save File and click OK.
  4. Select a location on your local file system and click Save.

Exporting Applications or Snapshots from the Application Home Tab

Applications or application snapshots can be exported from Composer’s Application Home tab to your local file system.

To export an application or snapshot:
  1. Open the application or snapshot you want to export.
  2. Click Main menu Main menu icon, select Export, and then select Last Published Application or Export Snapshot.

    The option available is based on whether you open an application or snapshot in step 1. For example, if you open a snapshot, the menu option is Export Snapshot.

  3. Click Save File and then click OK.
  4. Select a location on your local file system, and then click Save.
Your exported application is saved as an EXP file on your local file system.

Exporting an Application to Oracle BPM 12 Series

You can take any application that you created in Oracle Process Cloud Service and export it to your local file system so you can then use it in Oracle Business Process Management (BPM) 12 series.

Applications created in Oracle Process Cloud Service have differences to those created in Oracle BPM 12 series. One of these differences is the start form event, which was introduced in Oracle Process Cloud Service as a way to simplify interactions with forms. In Oracle BPM 12 series, an initiator pattern is used. Applications created in Oracle Process Cloud Service that begin with a start form event can be exported using a specific export action so that they can be used in Oracle BPM 12 series.

If a process has a single start form event, then it’s migrated to an initiator pattern in the same process. However, because processes can’t have multiple initiator patterns but can have multiple start form events, if the process has multiple start form events, each start form is replaced with a start message event in the original process. Additional processes are created to invoke these start events. Each of the additional processes have only an initiator pattern invoking the form, and a send task invoking the original process with the required arguments.

When you export an application for use in Oracle BPM 12 series, a specific export action is triggered and certain tasks are performed when start form events are found.

Start Form Events Tasks Performed

Single Start Form Event

  • Replaces the start form event with a start none event.

  • Adds a user task after the start none event.

  • Verifies that the role isn’t automatic. If yes, modifies the role to Process Owner.

  • Creates a human task with the form information.

  • Copies the mapping from the start form event to the newly created human task.

Multiple Start Form Events

  • Creates a new caller process:

    • Adds a start none event.

    • Defines instance variables required to keep arguments from the form to the send task.

    • Adds a user task after the start none event.

    • Sets the role to Process Owner.

    • Creates a human task with the form information.

    • Copies the mapping from the original start form event to the newly created user task.

    • Adds a send task with its conversation to invoke the original process with the arguments from the original start form event.

  • Changes the start none event to a start message event.

    The start message event keeps the mappings and arguments that were contained in the start form event.

To export an application for use in Oracle BPM 12 series:

  1. Go to the Composer Home page.
  2. Find the application you want to export for use in Oracle BPM 12 series.
  3. Click Options Options icon, then select Download application on-premise compatibility mode.
  4. Select Save File and click OK.
  5. Select a location on your local file system and click Save.

    Your exported application is formatted for use in Oracle BPM 12 Series and is saved as an EXP file on your local file system.

Tip:

If the application is currently open, click Main menu Main menu icon, select Export, and then select Last Published Application on-premise compatibility mode to export the application for use in Oracle BPM 12 series.