Duplicate a Flow
If you want to duplicate the current Flow with a different name, click Duplicate flow
in the Flows window. Then change the Flow name.
Export and Import flows with connections and formats
In Etlworks you can create a copy of the Flow (or multiple Flows) with all its Connections and Formats, using Export/Import
functionality.
Export Flow(s)
To Export a Flow (or multiple Flows), go to the Flows
page, click Export/Import Flow
, and select Export
from the drop-down menu.
Then, select the Flow or multiple Flows, click Export Selected
or Export All
. A file with the extension etld
will be downloaded to your local drive.
If you are exporting a nested Flow, all included Flows, Connections, and Formats will be exported as well.
Import Flow(s)
Step 1. To Import a Flow, go to the Flows
page, click Export/Import Flow
, and select Import
from the drop-down menu.
Step 2. Click Please choose the flow file to import
and select the file with the extension etld
(new) or intflow
(old) that you wish to import.
Step 3. Select the Flow(s) to import, collision policy, and extra tags if needed. Afterward, click Import Selected
or Import All
.
If you are importing a nested Flow, all included Flows, Connections, and Formats will be imported as well.
Collision policies
The following collision policies are supported:
- Add: Etlworks will create new Flows, Formats, Connections, Macros, and Listeners. The following rules are used when creating the Flow's artifacts:
1. When you import a Flow, Etlworks creates new Flows, Connections, and Formats with the same parameters as the original Flows, Connections, and Formats but adds the suffix (timestamp). For example: Create new FW xml file [05-17-2017_14-52-41]
. It makes sense to change all generated names to something else — for example, removing the (timestamp) suffix and modifying the name. Ensure that the new name is unique; otherwise, Etlworks will not allow you to change it.
2. If a Flow uses the HTTP Listener as a source (FROM
) or destination (TO
), the original endpoint will be updated as well (since there can't be two endpoints with the same path). Make sure that you change the URL Pattern before scheduling the new Flow. Once again, the URL Pattern must be globally unique across all the Listeners.
- Replace: Etlworks will replace existing Flows, Connections, Formats, Macros, and Listeners if the name and the type are the same as in the Flow to import.
- Keep: Etlworks will keep existing Flows, Connections, Formats, Macros, and Listeners if the name and the type are the same as in the Flow to import.
- Keep all, replaces Flows and Macros: Etlworks will replace existing Flows, and Macros and keep existing Connections, Formats, and Listeners. Use this collision policy if you are migrating flows from one environment to another and prefer to keep existing connections and formats in the destination environment.
Add tags
If you choose to add new tags, the selected tags will be added to all Flows, Formats, Connections, and Listeners, created or updated during the import.
Export File Encryption
Every export file contents encrypted with the default key. If you would like to override the key used for encryption and decryption of the export files, go to Settings
-> Security
-> Export/Import Encryption
section and provide your own Private Key in PEM format and the optional Private Key Passphrase. Key should be in PEM format (PKCS#1) that starts with the tag "-----BEGIN RSA PRIVATE KEY-----". Such key can be generated with ssh-keygen -t rsa -m PEM
command on Linux or Mac systems. On Windows same command can be used in case OpenSSH Client
has been added under Apps & features
-> Optional features
, or with the help of PuTTY.
Comments
0 comments
Please sign in to leave a comment.