Properties can be assigned to each particular taskAn executable object that is running. Tasks are also referred to as activities. of a Schedule which as a result, can influence their execution. Detailed description about the tabs and the fields/control elements are found in the User Guide. This document serves to explain the particular settings and possible effects. The order in which the different settings are checked is significant.
The following table describes the logical checking order in writing, the Schedule-Logic Diagram gives details in pictures.
Checking Order |
Description |
Tab |
---|---|---|
|
Repeated checks during schedule execution |
|
Periodic turnaround |
In the Attributes of the Schedule, the time span of a period and the specific time for the periodic turnaround can be set. Within a period, tasks are started once. |
|
|
Checking before the start of a task |
|
Start time |
Point in time at which the task should start. |
Start time |
![]() |
||
Start of Period + n days | The start of a Schedule whose period has been
defined for several days can be postponed if the task is not to be started
at the day the period starts. This is especially important when the Schedule's period has been defined so that the period turnaround is not 12:00pm. |
Start time |
![]() |
||
Active |
If a task is part of a Schedule but should not be executed, you can set it inactive. It obtains the statusThis represents the condition of a task (such as active, blocked, generating). ENDED_INACTIVE in this case. |
|
|
|
|
Calendar |
It is also possible to have a task only executed on particular days. These days can be specified in calendar keywords. If the defined calendarAn Automation Engine object type that defines a set of days based on calendar keywords. condition does not apply, the task ends with the status ENDED_INACTIVE. |
|
|
Checking during task execution |
|
A task's runtime can be monitored during the execution of the task, thereby enabling reaction to exceeded maximum runtimes. The task can be canceled or ended and/or another task be executed. |
||
|
Checking at the end of a task |
|
Minimum runtime |
At the end of task execution, it can be checked if the specified minimum runtime was kept. If not, the same settings can be defined as with monitoring the maximum runtime. |
|
|
|
|
OK status |
You can also react to the end status of a task. Tasks can be re-activated and/or any task can be started when the specified status is not met. The Result tab is not considered if a task obtains the status ENDED_INACTIVE. |
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |