The Destination Settings window allows users to configure where files will be uploaded and apply rules for file handling and filtering.

Destination configuration is completed in steps. Select an endpoint first, then click Next to configure the Path and other options, and then click Save.

Destination tab - endpoint selection

Search for an endpoint or select an endpoint from the list. The list can be sorted by endpoint name or type. After you select an endpoint, its name is shown in the dialog to help confirm your selection.

General tab - configure path, file handling, and filters

Path: Specify the directory path where files will be uploaded. To browse to a folder, an active agent must be assigned to the task and the target endpoint must be accessible from that agent.

When browsing for a destination folder in SFTP or FTPS endpoints, Automate MFT uses the default directory configured on the server for the connecting user. The default directory is determined by the server configuration for the user account. Its location may vary depending on the SFTP or FTPS server implementation.

If a file exists: The options in this dropdown menu define how Automate MFT handles files that already exist at the destination path. The available options are:
  • Overwrite existing file: Replace the existing file with the new one.
  • Fail the task: Stop the task and report an error.
  • Skip file and continue: Ignore the file and proceed with the rest of the task.
  • Upload as a new file: Save the file with a unique name to avoid overwriting
Rename files: The Rename Files option allows users to rename files during transfer operations dynamically using macros. This is useful for organizing files, appending timestamps, or customizing filenames for archival or alerting purposes. An example pattern is: 
[OnlyName]_[yyyy].[MM].[dd]_[HH].[mm].[ss].[OnlyExt]
This pattern renames the file using its base name, current date and time, and original extension.
Filter only specific files: This option allows users to filter which files are downloaded based on file filters and match types. File filters are applied first to narrow down the list of candidate files. After filtering, the match type is applied using AND logic. This means that a file must match the filter and satisfy the defined conditions to be selected for download. For more detailed information, see file wildcards and globs.
  • File Filters: Users can list custom filters, such as file name, extension, and size, to limit the files that are downloaded.
  • Match Type: Users can define rules for filtering files based on specific attributes. These rules are evaluated using logical conditions, and at least one condition must be added for the filter to be active.
    • Match All: Uses AND logic. All conditions must be true for the file to be selected.
    • Match Any: Uses OR logic. A file is selected if any one of the conditions is true.