![]() Navigate to Event Manager > Event Rules and click 'New' to add a new rule. Next, you will create a rule that will be triggered off of the Scheduled Task. This creates a list of four File Scanned Events, one for each of the four files File A-D in the folder. ![]() In the example provided, the folder “C:\ftproot\uploads” is the target folder, with either an empty filter string or a wildcard * in the filter string. ![]() For example, *.txt will create events for every text file in the directory. It will append the filter string to the folder path if it’s in the form of * for a wildcard, and ? for single characters. The filter string is a way to pick up only a single type of file. If you’d like not only the defined folder, but all of its children, simply check the “Recursively transfer all sub-folder content” box. This path must be a directory and Cerberus FTP Server will create a File Scanned Event for each file in that directory. “Scan Folder Path” is the directory you’d like to scan. These options all work together to determine if this action failed in terms of the prior checkbox. There is even the case where this is a failure if any one of the event rules that handled the new File Scanned Event returned an error. Is a Failure state one where it can’t create an event for every file in the given folder? Or is it a failure state only if every file scanned fails, continuing if there is even only one found file? Or, if nothing is processed, then perhaps that is a failure state where you don’t want to send a confirmation email if nothing was scanned. The first subsection is “Fail If.” This section helps define what Scan A Folder should consider a terminal failure state, and when it will ignore and continue to process the next action. This action has the same top elements as all other actions: An action type and ‘using’ field gets filled in for Scan A Folder and is not editable and the standard “Stop on Failure” checkbox as all actions have, which determines if processing will continue to the next action if this action fails. In this example case, the action will occur daily at midnight.Ĭreate a new action by using the new button and choosing Scan A Folder in the Action: drop-down menu. Navigate to Event Manager > Scheduled Tasks and click the 'New' button to add a new task.ĭefine a time for this task to occur, and how often it will repeat. ![]() The first step to using this new feature is to define when this action is to occur. The Scan A Folder workflow is broken into two steps. Otherwise, the location of the archive is sent by HTTP post to another server. If one of the actions (file sends/moves/zipping) fails due to an error, the Failure Action will send an email to notify the administrator. The second rule only triggers on the last scanned file in the folder, and, only when all files have been moved, zips up the directory for archiving. In this example, the first rule sends scanned files somewhere, then moves the file to another folder. These events are processed in order by the Events System, each time looking for rules that trigger off of the given File Scanned Events. The Scan A Folder action looks at the uploads folder and, for each file there, sends out a File Scanned Event. This example has a scheduled task that triggers every night at midnight. This might be a case of a teacher automating their homework submission folder such that CerberusFTP takes all files uploaded to a folder by midnight and archives them. These instructions give an example as to how a Scan A Folder workflow might occur. With this event’s ability to specify a condition on the generating task’s name, the rule can be restricted to only occur for a specific Scheduled Task. These events can trigger Event Rules to perform operations on the files in the folder. Add a folder path to this Scan A Folder scheduled task action and, for each file in that folder, the task will trigger File Scanned Events you have defined in Event Rules. This Scheduled Task action allows a user to manipulate every file in a folder without needing to know the specific files in the folder.Īdministrators have previously needed to know ahead of time the names of files for use with actions such as Send a File, Get a File, file operations, and others.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |