Events

Operating System Events and AS2-related Events are available only in EFT Server Enterprise. These Events are visible, but unavailable (grayed out) in EFT Server (basic edition).

EFT Server includes over 25 different event triggers, based on the following event types:

Operating System Events (available only in EFT Server Enterprise)

  • Scheduler (Timer) Event - Execute a specified action one time or repeat at a specified interval.

  • Folder Monitor - Monitor a specified folder then execute an action whenever a change is detected.

  • Folder Monitor Failed - Monitor a specified folder then execute a specified action whenever a failure is detected.

Use the File Uploaded file system event to notify you when a file is uploaded to the Site.

File System Events

  • File Uploaded - If a file is uploaded to the Site.

  • File Downloaded - If a file is downloaded from the Site.

  • Verified Upload Succeeded - If integrity check of uploaded file succeeds when transferred using the Web Transfer Client.

  • Verified Download Succeeded - If integrity check of downloaded file succeeds when transferred using the Web Transfer Client.

  • File Renamed- If a file on the Site is renamed by a connected client.

  • File Moved - If a file is moved from one folder in the VFS to another by a connected client.

  • File Deleted- If a file is deleted from the Site by connected client.

  • Folder Created - If a folder is created on the Site by a connected client.

  • Folder Deleted - If a folder is deleted from the Site by a connected client.

  • Folder Changed - If a user navigates to a new folder on the Site.

  • Upload Failed - If an upload fails to transfer successfully.

  • Download Failed - If a download fails to transfer successfully.

  • Verified Upload Failed - If integrity check of uploaded file fails when transferred using the Web Transfer Client.

  • Verified Download Failed - If integrity check of downloaded file fails when transferred using the Web Transfer Client.

  • Before Download - If a download is requested, perform this first.

Server Events

  • Service Stopped - When the EFT Server service stops.

  • Service Started - When the EFT Server service starts.

  • Log Rotated - When the current activity log closes and EFT Server opens a new log file.

Site Events

  • Site Stop - When the Site stops.

  • Site Started - When the Site starts.

User Events

  • User Account Disabled - If the user account is disabled by the administrator or by EFT Server.

  • User Quota Exceeded - If the user has taken too much disk space on EFT Server.

  • User Logged out - If the user closes a session gracefully.

  • User Logged in - If the user logs in to EFT Server.

  • User Login Failed - If the user attempts an incorrect username or password.

  • User Password Changed - If the user or administrator changes a user's password.

  • New User Created - If a new user has been created.

Connection Events

  • User Connected - When a user connects to the Site (this occurs before log in).

  • User Connect Failed - When a user attempts to connect and fails (this can occur before log in).

  • User Disconnected - When a user disconnects from the Site (this can occur before log in).

AS2 Events (available only in EFT Server Enterprise)

  • AS2 Inbound Transaction Succeeded - Triggers if the inbound transmission was successful, MDN Message Disposition Notification; The Internet messaging format used to convey a receipt. This term is used interchangeably with receipt. An MDN is a receipt. was successfully sent, MICs all match, and no other errors occurred.

  • AS2 Inbound Transaction Failed - Triggers if the AS2 file upload failed for some reason, such as bad MIC The message integrity check (MIC), also called the message digest, is the digest output of the hash algorithm used by the digital signature. The digital signature is computed over the MIC., no permissions/access, duplicate message ID, or other AS2 transfer-related error.

  • AS2 Outbound Transaction Succeed - Triggers if EFT Server has offloaded a file to a remote partner, and that partner replied with a receipt asynchronously over HTTP/S, indicating that the transfer was successfully completed.

  • AS2 Outbound Transaction Failed - Triggers if the expected MDN receipt was not received in the expected time or the receipt signature or MIC failed.

 

 

 

Related Topics

Which Actions are Available with which Event Triggers?

List of Conditions