We are currently looking to test and implement a Folder Monitor to delete stale files that have been uploaded by our clients. However we believe the file/folder structure of our client repository may be a limiting factor for this configuration. Essentially we have the following folder layout currently:
Client Abbreviation ->
Now… As you can imagine there a many “Client Abbreviation” folders (about 400 to be exact) for each client. Then within that we have the downloads, implementation and customer upload folders. What we would like to do is have the Folder Monitor check all of the “Customer Upload” folders and then delete files within that are older than 30 days.
Please let me know if that will be something that is feasible for us in some way with the Folder Monitor.
That’s an interesting problem. 400+ folder monitors wouldn’t be practical, or efficient, but I think a folder monitor that runs once a day and uses a regular expression to match your files might work.
You could setup the folder monitor on the parent folder for your customers and have the regular expression filter out file paths that only match “Customer Upload”. The hard part would be figuring out the regular expression, although a little research and our regular expression tester in the Folder Monitor should help.