Local file-system changes: Since 1.3
Remote file-system changes: Since 4.2
File Event Listeners allow you to monitor changes on a specific local file system path or remote URL – for example, new files appearing in a folder – and react to such an event with a predefined task.
You can either specify an exact file name or use a wildcard or regexp, then set a checking interval in seconds and define a task to process the event.
There is a global minimum check interval that you can change if
necessary in the configuration (the
See Chapter 15, List of Configuration Properties.
Figure 32.6. Web GUI - creating a File Event listener
Table 32.8. Parameters passed from the listener to the task
|EVENT_USERNAME||The name of the user who caused the event.|
|EVENT_USER_ID||A numeric ID of the user who caused the event.|
|EVENT_FILE_NAME||The name of the file (without the path or URL) that triggered the event. Present only when Trigger one task for multiple changed files is disabled.|
|EVENT_FILE_PATH||A resolved (without placeholders) path to the observed directory on the local filesystem. Valid only for a local file listener.|
|EVENT_FILE_PATTERN||A filename pattern.|
The type of the file event.
Possible values: |
|EVENT_FILE_LISTENER_ID||An ID of the listener which triggered the event.|
Full URLs to access the files, e.g. in the File URL attribute of components.
If Trigger one task for multiple changed files is enabled and there are multiple URLs,
they are separated by a separator specified by CloverDX Engine property |
|EVENT_FILE_AUTH_USERNAME||A username/ID to the remote location.|
The same as |
|EVENT_FILE_AUTH_PASSWORD||a password/key to the remote location. It is encrypted by the master password.|
The same as |