Conditions are used to place additional restrictions on whether a job or step should run. For example, you can specify that a job should run only if a particular file exists.
|
|
Conditions do not cause a job to start—only triggers The signal (such as a schedule) that causes a job to be started. do this. Conditions are evaluated after a trigger starts a job. |
adTempus offers the following kinds of conditions:
The Job Condition depends on the state of another job.
The File Condition depends on the presence or absence of one or more files.
The Process Condition depends on the state of an external process.
The Script Condition allows you to use a script to write your own condition logic.
adTempus Architecture Overview
