How Applications Manager Processes Conditions

Applications Manager processes conditions before, during, and after a job runs, and after a task is deleted.

Applications Manager determines when each condition is evaluated based on its condition timing. There are four condition timings; BEFORE, DURING, AFTER, and DELETED. The flowchart below shows the evaluation cycle Applications Manager applies to each task's BEFORE conditions.

An evaluation cycle consists of working through the flowchart above until the 'Run task' or 'End processing' step is reached. Applications Manager runs through the evaluation cycle for a task until it completes executing and is moved to History, or until it aborts. Applications Manager evaluates all conditions in the order they are listed with the following exceptions:

• If a condition runs a task, Applications Manager ignores the remaining BEFORE conditions for that task.
• If a condition stops the evaluation cycle, all remaining conditions are ignored for the current cycle. For example if a condition puts a job on hold, all remaining conditions will be ignored until the next cycle.
• If you use the GOTO CONDITION action, the destination condition must come after the condition containing the GOTO action.

Running BEFORE Conditions

When Applications Manager is ready to execute a task, it evaluates its BEFORE conditions. By default, a task will run unless one of the BEFORE conditions modifies its eligibility.

Running DURING Conditions

While a task is running, Applications Manager evaluates its DURING conditions. The frequency that Applications Manager evaluates DURING conditions is based on the DURING_WAIT variable setting.

When the automation engine has no processing to do, it sleeps for the number of seconds entered in the Sleep time field for its local agent. At the end of each sleep cycle, the automation engine evaluates the DURING conditions.

When the automation engine is processing, it checks the DURING conditions. The frequency that it checks them is based on the setting for the DURING_WAIT variable in your awenv.ini file, located in the site directory. You can modify the setting. The default is 60 seconds.

Setting a low DURING_WAIT value may impede performance without evaluating conditions more frequently.

If a task completes executing in a shorter amount of time than the setting for the DURING_WAIT variable, its DURING conditions may not execute.

Running AFTER Conditions

After a task completes executing successfully or unsuccessfully, Applications Manager evaluates all AFTER conditions. If a task is killed, AFTER conditions are still evaluated.

Running DELETED Conditions

If a task is deleted from the Backlog by a user, Applications Manager processes DELETED conditions and skips any AFTER conditions associated with the given job.