Appendix C: Task Action Order

The actions for tasks from insertion to the Backlog to notification of completion status are listed below in the order they occur.

Applications Manager will take the actions listed below in order they are listed for all tasks regardless of whether they are jobs, process flows, or process flow components. Some actions will not be relevant for every task. For example, a stand-alone job may have no predecessors. If an action is not relevant, the next action can be taken.

1. A task is inserted into the Backlog by being a:
   • Scheduled job or process flow.
   • Scheduled and staged job or process flow.
   • Requested job or process flow.
   • Component in a process flow that is scheduled, staged and scheduled, or requested.
2. A task may be skipped if is:
   • Inactivated in its job, process flow, or process flow component definition.
   • A component with a run or skip calendar that prohibits it from running.
   • A component with the current day of the week unchecked for eligibility.
3. The task waits until start time is not in future. Start times may be in the future when tasks are staged or when requests are post-dated.
4. Applications Manager waits for the task's predecessor requirements to be met.
5. Applications Manager waits for the task's necessary automation engine, agent, and queue capacity to be available.
6. Applications Manager evaluates and executes any BEFORE conditions.
7. The task is started.
8. Applications Manager evaluates and executes any DURING conditions.
9. The task finishes.
10. The task executes any output scans.
11. Applications Manager evaluates and executes any AFTER or DELETED conditions.
12. A record of the task's success or failure is written to History. Whether a task remains in the Backlog when it fails is determined by the Stay in queue on abort setting in its job definition.
13. The task executes notification.