We can export a flow file, including dependencies used by the flow and all associated metadata, to share it with another builder/tenant. Exporting a flow that uses an authentication service like Salesforce, will export the service credentials as well. We can bypass this by exporting a flow without the service passwords.
A flow needs to have been published, before we can export it.
- Click Import/Export.
- Click Select a Flow.
This lists all the flows in our tenant.
- Select the flow we want to export. (Example: Parent flow.)
- Click Download Package.
This downloads the flow file, including dependencies used by the flow and metadata. This file can be imported into a tenant.
If the tenant we are importing the exported flow file to, already has a service used by the flow installed; we will have duplicate instances of the service.
This can potentially cause all sorts of confusion later! One way to avoid this, would be to create a new subtenant for any flow we may be importing. Another, would be to rename the service either in the tenant we are exporting the flow from or in the tenant we are exporting the service to.
When we import a flow file in a tenant, the services used in the flow are also imported. We want to update those services. Updating a service will update all the types used by that service.
If we do not update the service, any types associated with that service that was not used in the imported flow, will not be recognized by the service subsequently. This can cause problems later, if we want to build flows using that service.