Wildcards

In order to monitor files whose name contains a certain text, we can use the File Monitor Trigger using the "*name_content*" syntax in the "Files to Monitor" field.


Trigger Variables

In the Process Designer, the predefined Trigger Variables can be used (Process Designer > Tools > Variables Manager > Trigger Variables) to access some properties of the event.



Network Folders

In case the folder that is being monitored is a network folder, we should use the syntax "\\someserver.com\some\path" in the "Folder to Monitor" field and not the mounted letter. File Monitor Trigger doesn't support monitoring shared folders by mapped directories.


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.


Possible Issues

If the Logs/Audit tab shows a "File Monitor Trigger will not be monitoring <path>" error, it is possible that the WinAutomation.MachineAgent (WinAutomation) / the Sidebot Agent (ProcessRobot) / Solobot Agent (ProcessRobot) - depending on which Agent is monitoring the folder, does not have adequate permissions to view/edit the network folder.


WinAutomation


- Open the properties window of the WinAutomation Machine Agent windows service.

- Set the service to log on as a network user who has access to that network folder.



ProcessRobot


1. A SideBot is monitoring the network folder

- Make sure that the SideBot User has access to the network folder.


2. A SoloBot is monitoring the network folder

- Open the properties window of the ProcessRobot SoloBot Service windows service.

- Set the service to log on as a network user who has access to that network folder.