Page 1 of 1

File Monitors - what indicates a modified file?

Posted: Thu Oct 23, 2014 1:30 pm
by LPrendergast
Hi, I am looking for a information on how file monitors work - specifically on how does the modified file action detect a modified file? What are the criteria?


Currently I have 2 monitors created. One to move new files, then delete the original (from the network share). and a second to move modified files, and then delete the original (from the network share).

First, I placed a new file on the windows share, and it was copied to the IFS and then deleted.
Then I modified the file slightly (added some records to the text file), placed on the windows, and nothing.

Re: File Monitors - what indicates a modified file?

Posted: Fri Oct 24, 2014 10:57 am
by Support_Rick
There are three ways to trip a monitor.

When a new file is added between snapshots
When a file is deleted between snapshots
When a file is changed between snapshots. Changed means if the File Size changes or the Last Modified Date changes. (The last modified date is measured in milliseconds, so it's very unlikely that a file could be changed between snapshots and still have the same last modified date as before.)

================

Processing is:

Place a file into the Monitor Folder
Trigger the GAD Project (Delete the file)
Place the same file into the folder again before the next trigger
The Monitor does NOT pick up the new file!
Monitor does not see the "new" file as it already existed in the previous snapshot

**NOTES**

Even though it has a new Modified Date/Time ... it is not considered a "New" file according to the Snapshot Comparison

If the file exists in the NEW snapshot, but not the old, it will trigger a File Created Monitor Action

If the file exists in BOTH Snapshots, but is different (Date/Size) it will trigger a File Modified Monitor Action