Table of contents
- General description
- The different parts of the Filesystem: Copy file Transformer
General description
The Filesystem: Copy file Transformer can be used when working with files and APIs that support file-based data exchange. For example, it can help manage a catalog with products in XML. When this file is downloaded in the Alumio platform, its contents can be transformed and the mutations can be stored. After this, it can be copied to another location within the Alumio platform or to any external system, such as an FTP server.
The different parts of the Filesystem: Copy file Transformer
-
Path of the file (required)
This is the file’s location within the provided file system. The field accepts placeholders to allow the use of dynamically generated paths. -
Source file system (required)
This specifies the file system where the original file is located. Alumio supports several file systems, including FTP, with each file system having its own configurable options and requirements. File systems can also be reused when created under the main menu item “Storage file systems”. -
Destination file system (required)
By default, this is set to the same file system as the source. For flexibility, another destination file system can be selected and configured here. Just like with the “Source file system”, it is also possible to choose a pre-configured one. -
Destination directory
This is the path where the file needs to be stored in the destination file system. -
When the destination exists
This determines what should be done when the file already exists on the target system. By default, the file will be ignored, and no copying will take place (Skip). As such, the options include:- Skip: Do not copy the file to the target system
- Overwrite: Replace the file in the target system
- Rename: If the file exists on the target system, Alumio tries to find a filename that does not exist on the target system to prevent overwriting existing files.
-
Rename strategy
This becomes available when the “Rename” option is selected. It describes how Alumio is going to react when a file with the same name already exists and how the new filename needs to be renamed.
When the strategy “Add an increasing number to the filename” is picked, extra fields will become available to configure the behavior.
-
Template for destination
A template with placeholders that tells Alumio where to place the file and how to name it. Available tokens are {dirname}/{filename}-{counter}.{extension} -
Format for the number
Defines how the number is formatted. For example, with a certain amount of leading zeros. -
Number to start
Determines where to start the number when a file already exists. Instead of starting from 0, another starting number can be configured, for example — 1000. -
Always add a number, even when the destination does not exist
When selected the rename strategy is always applied. The first file should then start with a 0 (zero) or with another number, if that override has been configured.
