Cloning allows you to keep the original flow or integration unchanged while modifying a duplicate version. This is particularly useful when cloning between environments for development and testing purposes.
This article describes how to clone custom flows and integrations. For instructions on cloning integration app flows, see Clone integration app flows with the template utility.
Note
-
You can’t clone shared integrations or shared data flows.
-
Referencing integration resources with aliases makes cloning more efficient, removing additional steps to configure the new integration.
-
The Next flow run and flow schedule settings are not included in a cloned flow, but you can modify the copy to match the original.
-
If you clone an integration with flow groups, the groups and flow assignments are also cloned.
Use the following steps to clone an integration:
-
Ensure you're in the correct environment by looking for the environment name at the top, right-hand side of the screen. If you only have one environment you won't see any other environments available.
-
On the Home page, go to the integration.
-
Based on the integration view you use, follow the steps given below.
-
Tile view: Click the overflow (...) menu in the upper-right corner of the tile and select Clone integration.
-
List view: In the Actions column, select Clone integration from the overflow (...) menu.
-
Integration dashboard: Click Clone integration.
-
-
In the Clone integration page, enter details.
-
Name: Enter a unique name for the clone. Make sure that it is unique enough that you can identify it later. You can always rename your integration tile or flow outside of the cloning process.
-
Environment: Select your environment. Only active environments you have Manage access to (or above) are visible. After cloning to a new environment, you must complete the setup steps; however, you can choose to complete the setup later. Learn more about using multiple environments.
-
-
Review the list of all cloned items contained within the new integration.
-
Click Clone integration at the bottom of the list of cloned integration components.
-
If you've successfully cloned your integration, you'll see a success message asking if you'd like to configure your cloned integration now or later. If you've cloned to a different environment, you'll be asked if you want to switch to that environment to configure the integration.
Depending on the integration, you must complete one or more steps to configure the cloned instance of the integration. Connections are not copied into the cloned integration, so the first step is configuring each app's connections.
For each connector, click the Configure link, then provide the requisite information for the connection and test your connection. See Connector solutions for help setting up connections for particular connectors.
Once you’ve successfully configured your connections, the Integration details page will open, showing all of your data flows. Here, you can turn flows off and on, schedule or run them and modify their field mappings.
-
Open the integration tile that contains the flow you want to clone.
-
Click the Actions overflow (...) menu in the Flows dashboard and select Clone flow.
-
In the Clone flow page, enter details.
-
Name: Enter a unique name for the clone.
-
Environment: Select your environment. Only active environments you have Manage access to (or above) are visible. After cloning to a new environment, you must complete the setup steps; however, you can choose to complete the setup later. Learn more about using multiple environments.
-
Integration: Select the integration tile to save the cloned flow.
You may also see an option for Standalone flows. Add it here if you're not ready to put your flow in a particular integration. It will then be accessible from the Standalone flows tile on the Home page.
-
Flow group: This option appears if your selected integration uses groups to organize flows. Select a group for the cloned flow or set it to Unassigned.
-
-
Review the list of components included in the duplicate flow.
-
At the bottom of the list of cloned flow components, click Clone flow.
Depending on the flow, you must complete one or more steps to configure the cloned instance of the flow. Connections are not copied into the cloned flow, so you'll need to configure the connections for any app connectors.
Once you’ve successfully configured your connections, the cloned data flow is stored in the integration tile you selected while cloning.
Comments
Tom Santiago There are some configuration settings that do not carry over when cloning a flow - like Next Flow step. I'm guessing there are others I'm not recalling of the top of my head. But it would be really helpful to list what these are, so that folks can make sure their flow behavior is truly replicated after cloning.
Hi, Rob. You are correct that a cloned flow, like any uploaded integration newly installed, is disabled by default. It also would lack scheduling information (from the source flow), which you'll have to recreate, relative to other flows in the new integration. We'll make that explicit in a future revision here.
As far as other settings, I've looked into the JSON definitions that are preserved between the original and clone, and they're fairly comprehensive and time-tested. If you ever run into functional differences, I would recommend contacting support so we can address them. (Reminder: you can always view the differences in Integration Lifecycle Management [ILM].)
Please sign in to leave a comment.