Introduction to Event Rules

Event Rules automate management tasks. Define an Event Rule to trigger an Action, or several Actions, when specified criteria are met. For example, event triggers (Conditions) can be used to initiate additional activities after a file has been uploaded/downloaded. You can synchronize content across systems, provide an automatic response, or you can trigger a custom command to run a custom application or script. You can specify Event Rules in the Server consist of Events, any optional Conditions affecting the Event Rule, and the Resulting Actions that are carried out.

When multiple Actions are defined for a single Event Rule, the Server carries out the actions in the following order:

  1. Execute Custom Command

  2. E-Mail Notification

  3. Stop Processing Rules

It is possible to configure Event Rules that create infinitely recursive cycles. Since all Event Rules operate synchronously, a file upload event cannot be completed until all corresponding event actions are finished. This could lead to unpredictable server behavior due to conflicts with shared access to the same files or deleting open files. Be careful not to create circumstances where such recursive cycles might occur. For file upload events, recursive cycles are not typical. It is recommended that you move files on the same server using the filesystem - not FTP.