Trigger file

Configuring Source Trigger Files can help eliminate the problem of partial files but are also used to trigger source or target applications or systems to process files. MFT supports 3 Trigger File configurations to cover numerous use cases. Trigger Files on the source are telling Thru to look 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 additional file Per File, indicates 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 Thru can transfer all files. Note: The semaphore file will be deleted after all data files are transferred.

By default Trigger Files are 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 will remove the added extension by renaming the file. The trigger file config must be set to temporary filename with a '.filepart' extension to properly support WinSCP's default behavior.

A separate file, PER FILE

Specify a file prefix and or extension to trigger a pull or keep a pull from occurring. How does it work? Here is an example: Where files are being hosted, the files can be instantly renamed with a script to indicate a new prefix and/or extension. Once detected by your configured Endpoint, each file will be downloaded as it meets the required criteria specified in the “a separate file, PER FILE configuration”.

Alternatively, set up the configuration to NOT download specific file prefix and or extensions because they are not ready for file transfer. Your configured Endpoint will then download all the other files in the Endpoint.

You can skip this configuration if you are going to use ONE separate file

1. Click Trigger Files.
2. Click a separate file, PER FILE.
3. Select Replace extension if required.
4. Enter a File Prefix and/or a File Extension. One, the other, or both can be used.
5. Click Save to save the changes and return back 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

Each file can be given a temporary name to indicate that the file is NOT ready to be transferred.

When MFT sees the Temp 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 Source endpoint to pull.

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

1. Click Trigger Files.
2. Click a TEMP FILENAME, for each file.
3. In the File Prefix field enter file prefix and/or enter the file extension in the File Extension field
4. Click Save to save the changes and return back to Flow Studio.

ONE separate file

This configuration looks 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. Enter a batch trigger file name in the Batch Trigger File Name field.
4. Click Save to save the changes and return back to Flow Studio.

On the Target Flow Endpoints, MFT allows you to create Trigger Files. MFT supports 3 Trigger File configurations just like in the source, to cover numerous use cases.