Export and Import a Configurable Transaction
In Studio, you can export and import configurable transactions with their dependencies, such as any action library, external service or reusable lambda that is being used within the flow. Exporting transactions and their dependencies allows you to migrate a whole transaction flow and its functionalities to a new environment without having to create it from scratch every time.
Export a Transaction
To export a transaction, go to the Transactions page, select one or more transactions from the list, and click Export. If the transaction contains dependencies, such as lambda processes, external services and/or action libraries, those will be included in the .zip file.
Import a Transaction
To import a transaction and its dependencies from another environment, go to the transactions page and click Import. The Import Transaction modal window opens. In the product drop-down list, select the product to apply it to your imported transaction. Click Select file and select a .zip file from your device.
In the Import Summary page, you see a detail of your transaction and the dependencies you are importing, if any. See below for an example.
Transactions tab. In this tab, you see details of the imported transaction that includes the following information:
Original Code
Transaction code that was set to the transaction in its origin environment.
Imported Code
Code assigned to the transaction when imported to the current environment. If the original code is already in use in the current environment, the system will automatically assign the first code available.
Name
Name of the transaction. This is the name it had assigned when exported from another environment.
Product
Product assigned to the transaction when importing it.
Action libraries tab. In this tab, you see details of the action libraries imported as dependencies for your transaction, including the following information:
Original Name
Name of the action library. This is the name set to the action library in its origin environment.
Imported Name
Name assigned to the action library when imported to the current environment. If the original name is already in use, the system will automatically assign a new name.
Lambdas tab. In this tab, you see details of the reusable lambdas imported as dependencies for your transaction, including the following information:
Original Name
Name of the reusable lambda. This is the name set to the reusable lambda on its origin environment.
Imported Name
Name assigned to the reusable lambda when imported to the current environment. If the original name is already in use, the system will automatically assign a new name.
The import process is confirmed automatically. Click Close to close the modal window and go to the Transactions page.