Executing Objects: The Completion Stage

Executable objects go through four execution stages. The completion stage is the last one and it includes the following steps:

  1. The completion stage starts.

  2. The task report is saved.

    You specify where to save it in the Job Report section of the object definition page.

  3. Is the object a Job?

    • No: Processing continues with the next step.

    • Yes: The following steps take place:

      1. Job report storage.
      2. The script that is written on the Post Process page is processed.

  4. Minimum runtime check.

    Is the expected minimum runtime reached?

    • No: The Else condition specified on the Runtime page is processed.
    • Yes: The execution ends.

The following diagram illustrates the steps that a task goes through during the completion stage:

Flowchart that illustrates the sequence of actions that occur during completion. It starts with saving a task report, with the save location specified in the Job Report section of the object definition page. The flowchart then diverges based on whether the object is a Job. If it is not, the process skips to the minimum runtime check. If the object is a Job, the process checks if the job report should be saved as a file. If yes, it saves the report in the file system. If not, it checks if the job report should be saved in the AE database, and if so, submits the report to the AE database. After saving the job report, the script on the Post Process page (JOBS and JOBQ) is processed. Finally, the process checks if the minimum runtime has been reached. If not, the Else condition specified on the Runtime page is processed. If yes, or after the Else condition is performed, the execution ends.

See also: