For information about Globalscape, visit www.globalscape.com.

List of Conditions

Conditions allow you narrow the trigger definition for an Event Rule. Conditions are optional; you do not have to define a Condition on an Event Rule to make it trigger an Action. Conditions allow more control over when an Action can take place. For example, you might create an Event Rule using the User Logged In Event, then add the If Logon Name Condition to trigger the Rule only when a specific user logs in.

Conditions are organized by type:

• AS2-related Conditions—Event is triggered based on criteria such as protocol or AS2 ID.

• Connection Conditions—Event is triggered based on connection information such as remote IP or if user connected via the Web Transfer Client

• File System Conditions—Event is triggered based on criteria such as file size or virtual path.

• Server Conditions—Event is triggered based on criteria such as whether EFT Server is running or log name.

• Site Conditions—Event is triggered based on whether the Site is started or stopped.

• User Conditions—Event is triggered based on criteria such as whether the user account has a particular protocol enabled or login name.

• Event Properties—Event is triggered based on a specific Event reason.

Each of the available Conditions and which Events they can be used with is described below. There are no Conditions available for the Site Stopped or Site Started Events.

AS2 Conditions

You can apply these Conditions to File Uploaded and AS2-related events. (AS2 available with EFT Server Enterprise)

• If AS2 Content Type. Tests whether the AS2 content matches the specified content type.

• 1. Add the Condition to a Rule.

  2. In the Rule Builder, click the linked text to specify whether the content type does/does not equal to [specific AS2 content type]. The Select Content Type dialog box appears.

  3. Click the Select Content Type drop-down list to select a content type (X12, EDIFACT, XML, EDI Consent, Binary, Plaintext).

  4. Click OK.

• If AS2 Partner ID. Tests whether the AS2 Partner ID matches the specified mask.

• 1. Add the Condition to a Rule.

  2. In the Rule Builder, click the linked text to specify whether the partner ID does/does not equal to [specific AS2 Partner ID]. The Select Value dialog box appears.

  3. Click the Select AS2 partner ID drop-down list to select a partner.

  4. Click OK.

You can also specify the AS2 protocol with the If Protocol Condition described below.

Connection Conditions

You can apply these Conditions to Connection Events, File system Events, and certain User Events.

• If Remote IP—a connection is made from a remote IP address that matches/does not match an IP address or IP mask.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text.

  3. In the Edit Value dialog box, type a string and/or wildcards, then click OK to add the Condition to the Event trigger.

  If Local IP—a connection is made to a local IP address that matches/does not match an IP address or IP mask.

  1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text.

  3. In the Edit Value dialog box, type a string and/or wildcards, then click OK to add the Condition to the Event trigger.

  If Local Port—a connection is made/not made on a port/range of ports.

  1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text.

  3. In the Edit Value dialog box, type a string and/or wildcards, then click OK to add the Condition to the Event trigger.

  If Protocol—an FTP/SSL/SFTP/HTTP/HTTPS connection has been made, is being used, or is not being used.

  1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click [ftp/ssl/tls/sftp/http/https/as2]. The Select Connection Protocol dialog box appears.

  3. Click the Select Connection Protocol drop-down list to select the protocol.

  4. Click OK.

• If Using Web Transfer Client—the user connected/did not connect via the Web Transfer Client.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the WTC does/does not equal to Yes/No.

Site Conditions

You can apply this Condition only to the User Account Disabled, User Password Changed, User Account Created Events.

• If Site running—The Site is started or stopped.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the Site Running does/does not equal to Yes/No.

File System Conditions

You can apply these Conditions only to File system Events and the Folder Monitor Event.

• If File Change—a file is/is not added, removed, or renamed in a folder. This Condition is added automatically when you create a Folder Monitor Event.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the file change does/does not equal to added, removed, or renamed.

• If Virtual Path—the file or folder exists, does not exist at a virtual location and/or wildcard.  

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the virtual path does/does not match/start with [path mask].

  3. In the Choose Virtual Path dialog box, specify a path or wildcard, then click Add to move the path to the right text box.

  4. To remove a path, in the right text box, click the path or wildcard, then click Remove.

  5. Click OK to add the Condition to the Event trigger.

• If Physical Path—the file or folder exists, does not exist at a physical location (the full folder path including the file name or wildcard).

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the virtual path does/does not match/start with [path mask].

  3. In the Choose Physical Path dialog box, specify a path or wildcard, then click Add to move the path to the right text box.

  4. To remove a path or wildcard, in the right text box, click the path or wildcard, then click Remove.

  5. Click OK to add the Condition to the Event trigger.

• If Physical Folder Name—the file or folder exists, does not exist in a physical folder (the folder path or wildcard without a file name).

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the virtual path does/does not match/start with [path mask].

  3. In the Choose Folder Names dialog box, specify a folder name or wildcard, then click Add to move the folder name or wildcard to the right text box.

  4. To remove a folder name or wildcard, in the right text box, click the folder name or wildcard, then click Remove.

  5. Click OK to add the Condition to the Event trigger.

• If Virtual Folder Name—the file or folder exists, does not exist in a virtual folder.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the virtual folder name does/does not match/start with [path mask].

  3. In the Choose Folder Names dialog box, specify a folder name or wildcard, then click Add to move the folder name or wildcard to the right text box.

  4. To remove a folder name or wildcard, in the right text box, click the folder name or wildcard, then click Remove.

  5. Click OK to add the Condition to the Event trigger.

• If File Name—the file name matches/does not match a string of characters and/or wildcard.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the virtual path does/does not match [path mask].

  3. In the Choose File Names dialog box, specify a file name or wildcard, then click Add to move the file name or wildcard to the right text box.

  4. To remove a path, in the right text box, click the file name or wildcard, then click Remove.

  5. Click OK to add the Condition to the Event trigger.

• If Base File Name—The portion of the filename to the left of the right most period; provided as a way to support rename. For example, if a file is downloaded as SomeFile.ext.tmp, the Base File Name is: SomeFile.ext.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the virtual path does/does not match [mask].

  3. In the Choose File Names dialog box, specify a file name or wildcard, then click Add to move the file name or wildcard to the right text box.

  4. To remove a file name or wildcard, in the right text box, click the file name or wildcard, then click Remove.

  5. Click OK to add the Condition to the Event trigger.

• If File Size—the file size is or is not less than, equal to, or greater than a specified number of bytes.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the file size is/is not equal to, greater than or equal to, less than, less than or equal to [size (B)].

  3. In the Edit Value dialog box, specify a file size in bytes, then click OK.

• If Physical Destination Path—(for File Moved Event) the file or folder exists, does not exist at a physical location and/or wildcard.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the virtual path does/does not match/start with [path mask].

  3. In the Choose Physical Paths dialog box, specify a path or wildcard, then click Add to move the path or wildcard to the right text box.

  4. To remove a path or wildcard, in the right text box, click the path or wildcard, then click Remove.

  5. Click OK to add the Condition to the Event trigger.

• If Virtual Destination Path—(for File Moved Event) the file or folder exists, does not exist at a virtual location (the full folder path including the file name and/or wildcard).

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the virtual path does/does not match/start with [path mask].

  3. In the Choose Virtual Paths dialog box, specify a path or wildcard, then click Add to move the path to the right text box.

  4. To remove a path or wildcard, in the right text box, click the path or wildcard, then click Remove.

  5. Click OK to add the Condition to the Event trigger.

• If Physical Destination Folder Name—(for File Moved Event) the physical folder name matches/does not match a physical folder name and/or wildcard.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the virtual path does/does not match/start with [path mask].

  3. In the Choose Folder Names dialog box, specify a folder name or wildcard, then click Add to move the folder name or wildcard to the right text box.

  4. To remove a folder name or wildcard, in the right text box, click the folder name or wildcard, then click Remove.

  5. Click OK to add the Condition to the Event trigger.

• If Destination File Name—(for File Moved Event) the destination file name matches/does not match a string of characters and/or wildcard.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the virtual path does/does not match [path mask].

  3. In the Choose File Names dialog box, specify a file name or wildcard, then click Add to move the file name or wildcard to the right text box.

  4. To remove a file name or wildcard, in the right text box, click the file name or wildcard, then click Remove.

  5. Click OK to add the Condition to the Event trigger.

Server Conditions

You can apply these conditions only to Server Events.

• If Server Running—The EFT Server service is currently running.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the Server does/does not equal to Yes/No.

• If Log Type—The log type is/is not a specific type.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the log type does/does not equal to [specific type].

  3. In the Select Log Type dialog box, specify a Log Type, then click OK.

• If Log Location—The log location matches a specific path.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the log location does/does not match [path].

  3. In the Edit Value dialog box, specify a path or wildcard, then click OK.

• If Node Name—EFT Server name matches/does not match a specific character string.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the node name does/does not equal to [name].

  3. In the Edit Value dialog box, specify a name or wildcard, then click OK.

• If Old Log File Path—(Used with the Log Rotated Event only) The old log file path matches a specific path.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the old log location does/does not match [path].

  3. In the Edit Value dialog box, specify a path or wildcard, then click OK.

• If New Log File Path—(Used with the Log Rotated Event only) The new log file path matches a specific path.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the new log location does/does not match [path].

  3. In the Edit Value dialog box, specify a path or wildcard, then click OK.

• If Old Log File Name—(Used with the Log Rotated Event only) The old log file name matches a specific name.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the old log location does/does not match [path].

  3. In the Edit Value dialog box, specify a path or wildcard, then click OK.

• If New Log File Name—(Used with the Log Rotated Event only) The new log file name matches a specific name.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the new log location does/does not match [path].

  3. In the Edit Value dialog box, specify a path or wildcard, then click OK.

User Conditions

You can apply user conditions to User Events and File system Events.

• If User Groups—the user account is or not a member of one or more Groups.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the user group is/is not a member of [specific group(s)].

  3. In the Specify target users and groups area, select the check box of the users/groups that will trigger the Event and clear the All Users check box if you don't want the Condition to apply to all users.

     

  4. Click OK to add the Condition to the Event trigger.

• If Logon Name—the user's username matches/does not match a specific username.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the logon name is/is not one of [specified name(s)].

  3. In the Specify target users and groups area, select the check box of the user that will trigger the Event and clear the All Users check box if you don't want it to apply to all users.

  4. Click OK to add the Condition to the Event trigger.

• If Logon Password—the user's password matches/does not match a specific string.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the logon password is/is not one of [specified password(s)].

  3. In the Choose Passwords dialog box, specify a password, then click Add to move the password to the right text box.

  4. To remove a password, in the right text box, click the password, then click Remove.

  5. Click OK to add the Condition to the Event trigger.

• If Account Enabled—the user account is enable or not enabled

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the account does/does not equal to Yes/No.

• If Settings Template—the user belongs/does not belong to a Settings Template.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the Settings Template does/does not equal to [Settings Template].

  3. In the Select Settings Template dialog box, specify a Settings Template, then click OK. (Even if there is only one Settings Template, you still have to click OK in the Select Settings Template dialog box to complete the Condition.)

• If Full Name—a user's name matches/does not match, contains/equals a specific string.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the user account name does/does not equal to/contain [specific word].

  3. In the Edit Value dialog box, specify a string, then click OK.

• If Description—the user's description matches/does not match, contains/equals a specific string.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the description does/does not equal to/contain [specific word].

  3. In the Edit Value dialog box, specify a word, then click OK.

• If Comment—the user's comment matches/does not match, contains/equals a specific string.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the comment does/does not equal to/contain [specific word].

  3. In the Edit Value dialog box, specify a string, then click OK.

• If EMail Address—the user's e-mail address matches/does not match, contains/equals a specific string.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the email address does/does not equal to/contain [specific word].

  3. In the Edit Value dialog box, specify a string, then click OK.

• If Phone Number—the user's phone number matches/does not match, contains/equals a specific string.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the phone number does/does not equal to/contain [specific word].

  3. In the Edit Value dialog box, specify a string, then click OK.

• If Pager Number—the user's pager number matches/does not match, contains/equals a specific string.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the pager number does/does not equal to/contain [specific word].

  3. In the Edit Value dialog box, specify a string, then click OK.

• If Fax Number—the user's fax number matches/does not match, contains/equals a specific string.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the fax number does/does not equal to/contain [specific word].

  3. In the Edit Value dialog box, specify a string, then click OK.

• If Home Folder—the location of a user's home folder matches/does not match a physical location.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the home folder does/does not match [path].

  3. In the Edit Value dialog box, specify a string, then click OK.

• If Home Folder is root—the user's home folder is/is not their root directory.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether home folder root does/does not equal to [yes/no].

• If Quota Max—the user's account has a size limit less than/equal to/not less than/not equal to a size in kilobytes.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the maximum quota does/does not equal to [size (MB)].

  3. In the Edit Value dialog box, specify string, then click OK.

• If Quota Used—the user's filled disk space is/is not less than/equal to/greater than an amount of allowed disk space.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the home folder is/is not equal to, greater than or equal to, less than, less than or equal to [size (MB)].

  3. In the Edit Value dialog box, specify a string, then click OK.

• If Invalid login attempts—the user's failed login attempts are/are not less than, equal to, greater than a number.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether invalid login attempts is/is not equal to, greater than or equal to, less than, less than or equal to [number].

  3. In the Edit Value dialog box, specify a string, then click OK.

• If User can change password—the user has/does not have permission to change the login password.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether user can change password does/does not equal to [yes/no].

• If Home IP—the user's allowed IP address matches/does not match an IP address or set of IP addresses.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the home IP does/does not match [ip mask].

  3. In the Edit Value dialog box, specify a string, then click OK.

• If User can connect using SSL—the user has/does not have SSL enabled.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether user can connect using SSL does/does not equal to [yes/no].

• If User can connect using FTP—the user has/does not have FTP enabled.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether user can connect using FTP does/does not equal to [yes/no].

• If User can connect using SFTP—the user has/does not have SFTP enabled.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether user can connect using SFTP does/does not equal to [yes/no].

Event Properties

• If Folder Monitor Failure reason—Available only with the Folder Monitor Failed Event.  

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the Failure reason does/does not equal to [reason].

  3. Click the [reason] link to specify which sort of failure to trigger on: any failure, archive failed, or health check failed.

• If Event Reason—The Event was triggered by one of the reasons in the table below. Available reasons depend on the Event trigger (User Connect Failed, User Login Failed, User Logged Out, Download Failed, Upload Failed, Verified Upload Failed, Verified Download Failed). For example, IP address was rejected can apply to the User Connect Failed Event; but cannot apply to any other Event triggers.

• 1. Add the Condition to the Event Rule.

  2. In the Rule Builder, click the linked text to specify whether the Event Reason does/does not equal to [specific reason].

  3. Click the [specific reason] link to specify which sort of failure to trigger on (refer to table below for Event Reasons).

     

     Event Reason	Event Trigger
     	User Connect Failed	User Login Failed	User Logged Out	Download Failed	Upload Failed	Verified Upload Failed	Verified Download Failed
     Aborted by user				X	X	X	X
     Access denied				X	X	X	X
     Account Disabled		X
     Account Locked Out (v6.1 and later)		X
     Connection closed				X	X	X	X
     File is banned				X	X	X	X
     File not found				X
     FTP Session was closed because of error			X
     FTP Session was closed by timeout			X
     FTP Session was closed by user (QUIT)			X
     Invalid password		X
     IP address was banned			X
     IP address was rejected	X
     IP address was rejected and banned	X
     Max incorrect password attempts reached			X
     Protocol not supported		X
     Quota exceeded					X	X	X
     Restricted IP		X
     TCP/IP connections was closed by peer			X
     Too many connections per IP	X	X
     Too many connections per Site	X	X
     Too many connections per user		X
     User was kicked by administrator			X

Related Topics

• Using Conditions

• Condition Placement

• Changing Condition Placement

• Condition Evaluation

• Else Clauses

• Logical Operators

• Evaluating Expressions

• The Compound Conditional Statement

• Events and Available Variables