Options tab allows configuring File & Folder Watcher specific options such as condition repetition and delay before execution. Smart file operation detection cooldown setting makes File & Folder Watcher to wait until no file operations are performed for specified amount of time and only then to detect which file operation has actually happened with watched file.
Enabling Trigger only file is accessible option ensures that no operations will be attempted while some file operations are still in progress thus making the file inaccessible for automatic processing.
|Trigger after delay of||Specifies the amount of time for Automation Workshop to wait upon Trigger activation before executing the Action.|
|Trigger after conditions have been met||Specifies number of times the conditions must be met to active the Trigger. Note that only variables present at the moment of Trigger activation will be passed to Action.|
|Smart file operation detection cooldown||Automatically translate file operations from technical to user perspective. More precisely, upon detection of relevant file activity the File & Folder Watcher continues monitoring the file until the specified amount of time passes without further activity and only then decides what file operation has actually happened and whether to launch the Task therefore (e.g., if File & Folder Watcher monitors for new files, yet the creation of a new file is merely a transitional part of modifying the old one, the Task will not be executed).|
|Trigger only after file is accessible||If enabled, Trigger is activated only when file stops being used by other processes (i.e., becomes accessible).|
|This Trigger is enabled||Enable or disable the Trigger. When disabled, the Trigger is neither monitoring the file system for changes nor performing any other operations.|
|Time units||Define and set a time frame in any given preferred format—be it milliseconds, seconds, minutes, hours or days.|
- Smart file operation detection cooldown. Multiple everyday file operations, while simple in concept, are a bit more complex in practice. For example, when saving a recently edited file, from user perspective it may seem as modification of a file. However, technically it can consist of many sequential file operations, e.g., creating a new temporary file, deleting the old file and then renaming the new file with original file name. Similarly, what seems to be a simple overwriting when copying files, may in fact technically consist of deleting the old file, creating a new one and modifying (writing) its contents.
- Trigger after conditions have been met. When Trigger is set to launch the Task after the conditions have been met for a specified number of times, the number of already counted triggering instances will reset to zero when the Task is disabled and enabled or current user is changed (when different credentials are used for logged in and logged off scenarios).
Ask for more…
If you have any questions, please do not hesitate to contact our support team.