7. Estudio Técnico
7.3 Fases aplicadas al presente Proyecto
7.3.3 G estión de Requerimientos
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 Paths dialog box, specify a path or wildcard, and then click Add to move the path to the right text box. You can add multiple paths.
4. To remove a path, in the right text box, click the path or wildcard, and 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 Paths dialog box, specify a path or wildcard, and then click Add to move the path to the right text box. You can add multiple paths.
4. To remove a path or wildcard, in the right text box, click the path or wildcard, and 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, and then click Add to move the folder name or wildcard to the right text box. You can add multiple folders.
4. To remove a folder name or wildcard, in the right text box, click the folder name or wildcard, and 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, and then click Add to move the folder name or wildcard to the right text box. You can add multiple folders.
4. To remove a folder name or wildcard, in the right text box, click the folder name or wildcard, and 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, and then click Add to move the file name or wildcard to the right text box. You can add multiple file names.
4. To remove a path, in the right text box, click the file name or wildcard, and 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, and then click Add to move the file name or wildcard to the right text box. You can add multiple file names.
4. To remove a file name or wildcard, in the right text box, click the file name or wildcard, and 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, and 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, and then click Add to move the path or wildcard to the right text box. You can add multiple paths.
Appendix C: List of Conditions
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, and then click Add to move the path to the right text box. You can add multiple paths.
4. To remove a path or wildcard, in the right text box, click the path or wildcard, and 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, and then click Add to move the folder name or wildcard to the right text box. You can add multiple names.
4. To remove a folder name or wildcard, in the right text box, click the folder name or wildcard, and 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, and then click Add to move the file name or wildcard to the right text box. You can add multiple names. 4. To remove a file name or wildcard, in the right text box, click the file name or wildcard,
and then click Remove.
5. Click OK to add the Condition to the Event trigger.
Server Conditions
You can apply these conditions to certain Server Events, Operating System Events, File System Events, and the IP Added to Ban List Site Event.
• 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, and 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, and 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, and 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, and 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, and 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, and 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].
Appendix C: List of Conditions