Skip to main content
The “Filesystem: move a file” transformer can be used to move a file from one directory into another one, and to move a file from one filesystem to another filesystem.

​
Fields

​
Path of the file

A required field. The location on the “source filesystem” where the file to be moved can be found. Supports placeholders to use file names from the entity data.

​
Source filesystem

A required field. The filesystem where the original file is located.

​
Destination filesystem

The filesystem where the file will be moved to. By default, the filesystem selected as “source filesystem” will be used. This allows users to move a file on the same filesystem. By selecting different filesystem users can move a file across filesystems. For example, from a FTP server to a S3 bucket.

​
Destination directory

A path where the file will be moved to on the “destination filesystem”. By default, the root directory configured on the selected filesystem will be used.

​
When the destination exists

Determines what happens when a file already exists on the destination filesystem.
  • Skip
    • Do not move the file.
  • Overwrite
    • Move the file, replaces the file on the destination filesystem.
  • Rename
    • If the file exists on the target filesystem, then Alumio tries to find a filename that does not exist on the target system to prevent overwriting existing files.

​
Rename strategy

Becomes available when the option rename is picked and is required. It describes how Alumio is going to react when the file already exists and how the new filename is going to be created. 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 Alumiowhere to place the file and how to name it. Available tokens are /-.

​
Format for the number

How the number is formatted. For example, with a certain amount of leading zero’s

​
Number to start

Where to start the number when a file already exists. Instead of starting from 0 a starting number of for example 1000 can be configured.

​
Always add a number, even when the destination does not exist

When ticked the rename strategy is always applied. The first file should then start with a 0 zero or with the number to start if that override has been configured.