Please enable JavaScript to view this site.

Altova FlowForce Server 2020 Advanced Edition

A file system trigger allows you to monitor a file or directory for changes such as newly added files or modified files (note that deleted files cannot be monitored). You can flexibly configure the directory polling interval (for example, every 60 seconds), and you can optionally set the start and expiry date of the trigger. You can also use wildcards to filter specific files of the directory.


The following screen shot illustrates a sample file system trigger.


Sample file system trigger

File system triggers have the following structure.



Specifies how the trigger should poll the directory or file. Valid options:


Newly created

The trigger fires whenever any new files or directories are added to the specified directory. In terms of server load, this option requires the least server resources.


When a new trigger is added and the job is saved, any existing files in that directory will be considered as newly created and the job will be executed for each.


If a file is deleted and then added again later, then the job will be executed for it again (note this will happen only if the "polling interval" seconds have already elapsed since deletion). The trigger also fires if a file has been renamed.


This trigger does not fire if any files from the polled directory are subsequently modified. If you need such behaviour, see the next option ("Modified date").

Modified date

The trigger checks the last modification timestamp of all the specified files. If any dates have changed, or a new file has been added, or a file has been renamed, the trigger fires.


This option takes slightly more resources from the server than the previous one.


This option computes and stores a hash code for the specified file. After the polling interval has passed, the hash code is recomputed and compared to the stored value. If there is a difference, the trigger fires. Note that this can place considerable load on the server.


If any dates have changed, or a new file has been added, or a file has been renamed, then the trigger also fires.

Polling interval

Specifies the frequency, in seconds, with which the directory will be polled.

Wait N seconds to settle

Defines the time in seconds that the server will wait before starting the next job.


Defines the trigger's starting date and time. This is an optional field.


Clicking in the Date field opens a pop-up calendar from which you can select the start date.


Defines the date and time when the trigger expires.

Time zone

Defines the time zone applicable to the start and expiry date and time. The default time zone is defined in the server administration settings (see Setting the Default Time Zone).


The enabled check box allows you to enable or disable the trigger. This option is useful when creating and testing new jobs.


The "triggerfile" parameter

Whenever you create a file system or HTTP trigger, FlowForce Server automatically adds a triggerfile input parameter to the job. When the job runs, FlowForce Server set this parameter to:


a) the file that triggered the job (in case of file system triggers)

b) the name of the temporary file that contains the downloaded content of the polled URI (in case of HTTP triggers).




You can pass the value of the triggerfile parameter as input value in any subsequent steps of the job. This way, you can user or process the triggering file as required.


By default, the triggerfile parameter contains the absolute path of the triggering file. To extract portions of the path, use the file path expression functions.


For an example of a job that uses the triggerfile parameter, see Creating a Directory Polling Job.

© 2020 Altova GmbH