After you add an action and define the conditions that trigger the action, you must define one or more tasks to execute when the action is triggered. After you define tasks for a post-processing, scheduled, or monitor folder action, activate the action as described in Operating Actions.

A post-processing action is triggered for each file based on the criteria configured in the action. The action is triggered by a file upload, file download, or a file delete. The action is executed for one file at a time. If an error occurs in the action, the file processing is stopped after processing the files in the current task.

For scheduled action, the “find” task is the first task that you define, by default. Otherwise, the scheduled action will fail. The files listed by the find task is the source of input files for the action. If the find task returns more than one file, the subsequent tasks will operate on all the files. Each task configured in the action will complete the operation on all the files in the list and pass on the set of files to the subsequent task.

A monitor folder action is triggered for each file based on the criteria configured in the action. The action is triggered by a file create or a file delete in a local or shared file system. The action is executed for one file at a time. If an error occurs in the action, the file processing is stopped after processing the files in the current task.

One type of task that ActiveTransfer Server can execute when an action is triggered is a file operation. File operations include finding, copying, moving, renaming, deleting, encrypting and decrypting, zipping or unzipping files, or writing content to a file. For each file operation, you should define specific properties that apply to that operation.

If an error task is configured in the action, one error task is executed for each file transaction that has an error. If the find task returns an empty list, subsequent tasks will be executed with 0 files as input.