Trigger file

Configuring Source Trigger Files prevents issues related to partial files. It is also used to trigger source or target applications or systems to process files. MFT supports three Trigger File configurations to cover numerous use cases. Trigger Files on the source instruct MFT to check for the specified Trigger File before transferring the file.

Important

Trigger files are required to prevent partial files when using MFT Server Endpoints.

Configuration Name	Function
	The presence of this file indicates that MFT can transfer the data file. Note: Each trigger file will be deleted from the Source Endpoint after the associated data file transfer has completed.
	The presence of the temporary filename indicates that the file is not ready to be transferred.
	The presence of the trigger file (semaphore file) indicates that MFT can transfer all files. Note: The semaphore file will be deleted after all data files are transferred.

By default, Trigger Files are set to DISABLED no trigger file set.

note

By default, clients such as WinSCP upload files with '.filepart' appended to the filename. After the upload is complete, WinSCP removes the added extension by renaming the file. The trigger file configuration must be set to temporary filename with a '.filepart' extension to properly support WinSCP's default behavior.

A separate file, PER FILE

You can specify a file prefix and/or extension to trigger a pull or prevent a pull.

How does it work?

For Example:

• Trigger a Pull: A script on the host can be used to instantly rename files, allowing for the addition of a new prefix and/or extension. Your configured Endpoint will detect the changes in the file and then download the file only if it meets the criteria specified in the “a separate file, PER FILE" configuration.
• Prevent a Pull: Alternatively, you can configure the Endpoint to not download files with specific prefixes and/or extensions, indicating they are not yet ready for transfer. The Endpoint will then download all other files present.

You can skip the following configuration if you are going to use the ONE separate file option.

1. Click Trigger Files.
2. Click a separate file, PER FILE.
3. Optional: Select Replace extension if a new file extension is needed.
4. Enter a value for File Prefix or File Extension, or both.
5. Click Save to apply the changes and return to Flow Studio.

info

Add .ext as a generic file extension or replace and add a custom extension name to your files.

A TEMP FILENAME for each File

You can a assign temporary name to each file to indicate that the file is not ready for transfer.

When MFT finds the temporary file name that you specify in the configuration, either prefix, extension, or both, it will not pull the files. You must rename them in your system to trigger the Source endpoint to pull.

Your configured Endpoint will download all other files. The additional rename settings allow for renaming those files with a new file prefix, file extension, or to remove them.

1. Click Trigger Files.
2. Click a TEMP FILENAME, for each file.
3. Enter a value for File Prefix or File Extension, or both.
4. Click Save to apply the changes and return to Flow Studio.

ONE separate file

This configuration searches for a Batch Trigger File Name to start a file transfer of all files in the file path. In this configuration, you need to specify the name of the batch file that will trigger the file transfer.

1. Click Trigger Files.
2. Click ONE separate file.
3. In the Batch Trigger File Name field, enter a batch trigger file name.
4. Click Save to apply the changes and return to Flow Studio.

Similar to the source, MFT allows you to create Trigger Files on the Target Flow Endpoints, supporting three Trigger File configurations to cover various use cases.