Help files

File Monitor Trigger

This Trigger monitors files in a Folder (and subfolders, if chosen), and fires if a file is created, modified, changed, or deleted within the folder(s). Specify the event(s) to look for, and file types you wish to include or exclude. With wildcards, this allows monitoring of a folder to see if any folder of the type .doc is created, for example, or any file other than an executable file is changed.

File_Monitor_Trigger_Image.png

The File Monitor Trigger, when fired, assigns values to four Trigger Variables that are made available to the Process:

%FileTriggerFileName% which will contain the name of the file that fired the Trigger,

%FileTriggerOldFileName% which will contain the original name of the file if it has been renamed,

%FileTriggerFilePath% which will contain the complete path (along with the filename) of the file. Note that this value is a File object meaning that has the properties of every file object. For example you can retrieve the size of the file that triggered the Process by specifying: %FileTriggerFilePath.Size%

and

%FileTriggerEventType% which will contain 'Created' or 'Changed', 'Deleted' or 'Renamed'.

You can create Actions in the Process to show this information, for example you can create a Process Trigger that fires when an executable file in the Windows directory (with subfolders) is changed, and the Process then puts up a Message Box informing you of what happened.

NOTE: File Monitor Trigger doesn't support monitoring shared folders by mapped directories. You need to use paths such as "\\someserver.com\some\path"

The proper method for monitoring such shares, is not to mount them locally on your computer and monitor them using the folder-paths you've assigned to them, but monitoring them directly with paths such as the one shown above.

Also you have to make sure that the WinAutomation.MachineAgent is running with the user's credentials who has access to the monitored folders.