Importing an App
By importing the .json file of an app, you can easily use flows and triggers from another Flogo app. You can import the .json file to a new app (which does not have flows) or to an existing app that contains flows.
Important Considerations
- Flogo apps that are exported from Flogo Enterprise 2.5.0 and later cannot be imported into previous versions of Flogo Enterprise.
- If a flow in the app uses extensions developed by the community, you can import the app even without the extension. You can import the extension later by clicking on the missing extension.
- Some apps created in Project Flogo use the
any
data type. Theany
data type is not supported in Flogo Enterprise. Such apps get imported successfully, but the element of typeany
gets converted into an empty object. You must explicitly use the mapper to populate the empty object with member elements. -
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.
- When you import an app that does not have a Return Activity in any flow (main or branched flow), the Return Activity is not added automatically by default. However, if an existing app already has Return activities in main or branched flows, the app is imported as expected.
- When importing an app, the
long
anddouble
data types get converted to thenumber
data type. -
When importing an app into an existing app, if the existing app has entities with the same name as the ones you are importing, a warning is displayed. You can opt not to import those flows, activities, or triggers. You can go back and rename them using the UI, export the app again, and re-import it.
- When importing apps that were exported from
Project Flogo, be aware of the following:
If the apps being imported use an Activity that is not supported in Flogo Enterprise, a validation error is displayed.
- You can only import apps that were created in Project Flogo version 0.5.2 or above.