As a reminder, this is the current setup of the environment.
The example setup
Performing the Clone
We will clone the Company 1 Group and create a new Group called "Connection Clone". To perform the clone, follow the steps described here, this time updating the Group name to "Connection Clone". Be sure to validate all of the screen to ensure no unexpected objects are exported or cloned!
The Results
In addition to new Sources being created, a new Output was created named "Connection Clone Single Group Output" because of the Single Group Connection attached. A new channel was added to Multi Group Output named "Connection Clone - SalesOrderDetail" because of the Multi Group Connection.
Newly created Connection Clone Output
Newly created Connection Clone - SalesOrderDetail channel
The Multi Group Connection
First let's take a look at the Multi Group Connection that already existed in the environment before the Clone. Navigating to that Connection, the Applied Objects tab shows that the Sales Order Header Sources from both Groups are attached to the Connection. The Multi Group logic has been successful!
The Connection is applied to both Groups
The Single Group Connection
Next, let's take a look at the Company 1 Single Group Connection. Navigating to the Applied Objects tab for that Connection, we can see that it is still only applied to the Company 1 Source as we intended.
The Company 1 Single Group Connection is still only applied to Company 1 Sources
Looking at the list of Connections, there is a newly created "Connection Clone Single Group Connection". Looking at its Applied Objects tab, it is associated only with Sources in the Connection Clone Group that we just created! The Singe Group Connection logic has also been cloned successfully!
The Connection Clone Single Group Connection
One EXTREMELY IMPORTANT note: When a Single Group Connection is created by the Clone operation, it will not have any sensitive credentials. Because DataForge stores all credentials encrypted, it is unable to copy over the existing credentials from the original Connection. Users must manually update the Connections with proper credentials. A warning is printed in the description of the Connection to warn users of this fact.
The newly created Connection with warning message
The clone has been completed successfully and preserved the desired user logic! The image below shows the new environment setup with the Connection Clone objects added.
The final result of the Clone
Updated