Exporting and Importing an App

You can export and import apps and use them as templates to quick start development or simply put them in a version control system such as GitHub.

Note: Flogo apps that are exported from TIBCO Cloud Integration- Flogo (PAYG) 2.5.0 and later cannot be imported into previous versions of TIBCO Cloud Integration- Flogo (PAYG).
Note: Here are a few things to keep in mind before you export or import an app:
  • Both exporting and importing apply to all flows within your app. You cannot pick and choose flows to export or import.
  • If any flow in the app uses extensions developed by the community, you need to make sure that those extensions are available to the app into which you are importing when importing. Flows that make use of extensions that are not present will not be imported.
  • Importing an app only works when there are no flows present in the app into which you are importing.
  • Passwords configured in any activity within any flow or connection in the app to be exported will be stripped out in the exported app. You must manually configure the credentials in the flows after importing such apps.
  • Some apps created in Project Flogo™ use the any data type. The any data type is not supported in TIBCO Cloud Integration- Flogo (PAYG). Such apps get imported successfully, but the element of type any gets converted into an empty object. You must explicitly use the mapper to populate the empty object with member elements.
  • When importing an app, be aware that the long and double data types get converted to the number data type.

Exporting an App

To export an app, follow these steps:
  1. On the Apps page, click the app to open the app details page.
  2. Click Export App.

    A JSON file with the same name as your app gets downloaded. This file contains all the data for each flow in the app.

Importing an App

When importing an app containing a connection, if you have an existing connection with an identical internal ID as the connection in the app being imported, a new connection does not get created. The imported app uses the existing connection in such a case. However, since the connection credentials do not get exported with the app, if a new connection gets created, you must re-configure the connection credentials after the app has been imported.

Important: An exported app can be imported into an empty app only. No other flows should exist in the app into which you are importing the exported app.
Note: The suffixes used in the Mapper have undergone some changes, because of which, you may receive a mapper-related warning in the Import app dialog when importing an existing app. Click Continue and the app will import successfully. After the import completes, be sure to re-map the properties in the activities that show errors. This will ensure that they switch to the new suffix format. The following table shows you the changes in the suffixes:
Original suffix appearing in imported apps New suffix used by the Mapper (after you re-map) For example... Used when mapping...
activity_id.activity_parameter $activity[activity_id].activity_parameter Old suffix:

$InvokeRESTService.responseBody.userId

New suffix after re-mapping property:

$activity[InvokeRESTService].responseBody.userId

When mapping to a parameter in the activity's output. Used to resolve activity params.

$TriggerData $trigger Old suffix:

$TriggerData.queryParams.title

New suffix after re-mapping property:

$trigger.queryParams.title

When mapping from the output of the trigger to flow input
N/A

There was no equivalent for this in the old mapper

$flow.headers.parameter

$flow.body.parameter

$flow is a newly introduced suffix which did not have an equivalent suffix in the old mapper

When mapping to any parameter in the flow's header or input schema (schema entered in the Input tab of Flow Inputs & Outputs dialog) which is the same as the output of the trigger since the output of the trigger is mapped to the input of the flow in a blank flow.

Used to resolve parameters from within the current flow. If a flow has a single trigger and no input parameters defined, then the output of the trigger is made available via $flow

Note: In imported apps, the passwords and secrets for any connections configured in the app do not get imported. You must reconfigure any password or secret for the connection after the app has been imported.
To import an app that was exported, do the following:
  1. Create a new empty app if you do not already have one. See Creating a Flogo App for details on creating an empty app.
  2. On the app page, click Import App. If you are using an existing empty app, click the Apps link, then click the app name to open the app details page.
  3. Navigate to or drag and drop the .json file for the app that you want to import.
  4. Click Upload. If any activity in a flow was configured with credentials or a connection, you will be prompted with a reminder to reconfigure them.
  5. Click Continue to finish importing the app.

    All the flows from the imported app will now be added to your new app.

  6. If any of the flows that were imported with the app had credentials such as password or a connection, be sure to re-configure them.