File System Triggers
File-system triggers start jobs when a change is detected in a file or folder (e.g., a new file has been added). Note that deleted files cannot be monitored. You can configure the directory polling interval (e.g., every 60 seconds) and optionally set the start and expiry date of the trigger. You can also use wildcards to filter files in a directory. The screenshot below illustrates a sample file-system trigger.
The parameters of a file-system trigger are described below.
Check | Specifies how the trigger should poll the files of a directory. Irrespective of the check option you select, when you add a new trigger and save the job, all existing files in the specified directory will be considered modified, and the job will be executed.
The possible check options are listed below:
•Newly created: The trigger fires whenever a file is added or renamed. In terms of server load, this option requires the least server resources.
•Modified Date: The trigger fires if a file's timestamp has changed or if a file has been added or renamed. This option takes slightly more resources from the server than the previous one.
•Content: The trigger fires if the content of any file changes or if a file has been added or renamed. Note that this option can place considerable load on the server, because the content is computed to a hash code each time the directory is polled.
|
Of file or directory | This is the path in which you would like to check changes. Note that only files in the specified directory are checked. You can also use wildcards to target only the files that match a particular pattern. For example, the path C:\Project\A* will cause FlowForce to check all the files starting with A that are located in the Project folder.
|
Polling interval | Specifies the frequency (in seconds), with which the directory will be polled. The default value is 60 seconds. The minimum value is 1 second.
|
If a change has been detected during the polling period, the server will wait for N seconds (the settle period) before checking the specified file/directory for further changes. If there have been no further changes during the settle period, the job will start. Otherwise, the server will wait again for the specified settle period and then check again if any changes have occurred since the last check.
This option allows FlowForce Server to wait until the file has been fully written before triggering the job.
|
Start | Defines the trigger's starting date and time. This is an optional field. When you click in the date field, a pop-up calendar opens, which allows you to select the start date. You can also type in the date manually.
|
Expires | Defines the date and time when the trigger expires.
|
Time zone | Defines the time zone of the start and expiry date and time. The default time zone is defined in the server administration settings.
|
Enabled | The Enabled check box allows you to enable or disable the trigger.
|