Substitution tokens allow you to specify dynamic content for command lines, notification messages, and other strings. That is, the contents of these items can change at execution time.
A substitution is an environment variable or script parameter name, enclosed in percent signs ("%"). Wherever substitution tokens are supported, they are replaced just before they are used with the value of the corresponding environment variable or script parameter.
For example, if you are setting up a notification message, you can specify the following notification message:
The current path is %path%
Before it adTempus sends the message, it will replace %path% with the current value of the "path" environment variable.
If your message is
Job triggered by file "%FileName%"
adTempus will replace %fileName% with the name of the file that triggered the File Trigger (because the File Trigger automatically sets the FileName parameter for the job).
If you have a parameter and an environment variable that share the same name, the value of the parameter is used. The names of environment variables and parameters are not case-sensitive.
Environment variables can be set in three ways:
Outside of adTempus. When you run a job, the job inherits the environment variable settings for the user account under which it is run.
Specify additional Environment Variables for a Program Execution Task. These values are available only to the program run by the task, and to any scripts run by the step to which the task belongs.
Use a script to modify the Environment collection.
Some parameters (such as the "FileName" parameter cited above) are set automatically by various triggers (see the individual triggers for information on the parameters you set).
You can also set parameters by executing scripts. For example, before you execute a Notification Action, you could execute a Script Action that sets the parameter values you need for your notification message.