|
Navigation: IM Sequencer > Schedule tasks > Triggers > File trigger |
![]() ![]()
|
The File trigger is a trigger that is able to start on file events (adding, updating or deleting)
General setting
All general file trigger settings are described below
| Monitored Directories You can specify witch directories need to be monitored, you can define multiple directories, if one change has been detected the trigger will trigger. |
| Monitor sub folders |
Indicate if the sub folders from the above directories should be monitored also
| File Filter |
You can set a specific filter, for instance only monitor xml files (*.xml) or file that match "SAPHR_*_.csv" where the wilcard can be anything.
| Monitoring options You can set several monitoring options: - Added - Detects that files are being added |
| - Updated - Detects that files are being updated |
| - Deleted - Detects that files are being deleted |
| Minimal Interval |
Set how many minutes should be between file changes, set this option if you expect a high load of file changes.
| Time constraints This option enables you to set the start and end time for the trigger, if not set the trigger will always monitor the directories |
| Enable source file lock detection Before the actual copy takes place the file will be checked if it is locked, this can be useful when the file is already created but the process creating the file is not yet ready writing the file. To detect the lock the file will be opened for reading, if this fails the file is locked. |
| The trigger will not trigger until the lock detection validates to true |
| Enable source file size detection Before the actual copy takes place the file size initial size will be stored, the process will wait 2 seconds and check the file size again, when the size is increasing the process will wait again, until the size no longer changes within 2 seconds. The trigger will not trigger until the size detection validates to true |
| Enable offline changes You can use this option to check the monitored directories if there are still files available that match the configured filter. This can be used when there are multiple files dropped into the monitored directory but they are not processed within the given time frame, so more files are queued and the trigger does not trigger (because it triggers when files are dropped or changed, which no longer occurs). To use this option you will need to move each file out of the monitored directory otherwise the file trigger will trigger every minute because it will still find files that match the filter |
| Impersonate Check this option if you want to impersonate when you are monitoring for file changes. Impersonation can help if the service account for the IM Sequencer Service does not have the appropriate rights to monitor for file changes. |
| - Username Username used during impersonation, you can use Domain\Username combination. |
| - Password Password for specified username. Note: The provided credentials will not be tested during setup, if you provide the wrong credentials the impersonation will fail, impersonation will revert at the end of this step type. |
| - Use remote impersonation |
Use this option if the username and password cannot be validated on the current machine. For instance when you want to monitor files from another computer in another domain or workgroup you should |
| enable this option to forward the credentials for that remote connection. |
![]() |
| File trigger type settings |
Page url: http://www.traxionsolutions.com/imsequencer/help/index.html?filetriggertype.htm