THE INFORMATION IN THIS ARTICLE APPLIES TO:
DISCUSSION
When you install the Secure Ad Hoc Transfer (SAT) module, the following
Event Rules are created by the installer. (If you are using a 64-bit system,
the Event Rules and Command need to be updated to reflect the 64-bit paths.)
See below for a description
of the AdHocRunCommand Custom
Command.
If end users are uploading with the Java-enabled
Web Transfer Client, add a second Rule using the "Verified
Upload Succeeded" Event and add the Condition "If Using
Web Transfer client does equal to Yes." Also add the "If
Using Web Transfer client does equal to No" Condition to
the Rule above.
These Event Rules automatically perform tasks that you had to configure
manually in previous versions of SAT. The SAT Event Rules are enabled
by default. You can edit the Rules and disable them as needed.
AdHocRunCommand Custom Command
The AdHocRunCommand Custom Command
is created in EFT when the SAT module is installed. AdHocRunCommand
executes C:\windows\system32\cscript.exe
(or C:\windows\syswow64\cscript.exe
on 64-bit systems) and includes some custom Command
parameters for executing the SAT scripts in the default SAT Event
Rules.
-
In the SAT - Notify
Sender of Upload(s) Received Event Rule, AdHocRunCommand
includes SendUploadNotification.wsf
//JOB:ON_TIMER in the Command
parameters box.
-
In the SAT - Delete
Expired Users Event Rule, AdHocRunCommand
includes EFTDeleteExpiredUsers.wsf
//JOB:DELETE_USERS in the Command
parameters box.
If you edit the custom Command, you might introduce errors, causing
the script to not execute as designed. Instead, you should create a separate
command, if necessary, and then you can add it as a subsequent Action
to the Rule.