Forecast
It is possible to retrieve information about different runtimes of tasks
because forecasts also consider calendar conditions and the settings specified
for the runtime monitoring and the earliest and latest start and end times.
All executable objects - excluding workflows, groups and schedules -
use the estimated runtime (ERT) for the creation
of forecasts. One minute is the default value for tasks that do not yet
have an ERT.
- Runtimes of workflows
and schedules are calculated on the basis of all individual tasks in these
objects.
- Scheduled tasks which
run before the forecast's starting point in time are not taken into account
(this also holds for ENDED_TIMEOUT).
- The estimated runtimes
of scheduled tasks are used for calculating the runtimes of groups. The
ERT values that are stored in the tasks are used. Therefore, it is not
possible to change the result by means of subsequent specifications for
ERT calculation in objects.
- It is also possible
that no tasks are scheduled for groups at the time of forecast calculation.
Therefore, the ERT of the relevant group or a fixed value for all groups
can be used.
- Scheduled tasks are calculated several times if they
are used for the calculation of a group and this group is available several
times. This causes results to be distorted.
Non-executed (skipped) tasks are taken into account with a calculated
runtime of one second. This is the time the Automation Engine requires for handling
the particular tasks.
Settings Considered in Forecast Calculations
- According to the entry
made in the Dependencies tab (task
properties in workflow).
- An ELSE action is executed if the required "earliest"
dependency conditions are not met.
- According to the entry
made in the Calendar tab (task properties
in workflow) and the specified logical date
of the forecast.
- The task is only evaluated with its runtime if the
set calendar conditions are met.
- According to the entry
in the Earliest tab (task properties
in workflow) and the specified real date and the
forecast's start time.
- The task is only started if the specified start time
for the earliest start has been reached or exceeded.
- According to the entry
made in the Earliest tab (task properties in workflow), the
specified real date and the forecas's start time.
- If the task's specified start time for the latest
start has already been exceeded at the determined latest starting time,
the task is not processed (ENDED_TIMEOUT).
- According to entry made
in the Earliest tab (task properties in workflow), the specified
logical date and the forecast's starting time.
- The task is not processed
if its estimated runtime (ERT) would exceed the
point in time specified as the latest end (ENDED_TIMEOUT).
- If the scheduled tasks are taken into account when
calculating the group, only tasks that can be processed within the remaining
runtime (difference between start time and latest end) are included in
the calculation.
- According to the entry
made in the task's Runtime
tab or in the Runtime tab
(task properties in workflow).
- A message is displayed if the specified maximum runtime
of the estimated runtime is exceeded. Depending on the specification made,
the task is then canceled or ended. Tasks that should be
processed when maximum runtime is exceeded are not taken into account.
- According to the entry
made in the task's Runtime tab or in the Runtime
tab (task properties in workflow).
- A message is displayed if the specified minimum runtime
of the estimated runtime is not reached. Tasks that should
be activated when runtime falls below minimum runtime are not taken into
account.
- According to the entry
made in the General tab (task
properties in workflow).
- A message is only displayed if the specified time
is exceeded and the task itself has not yet started.
Settings Not Considered in Forecast Calculations
- Current conditions of Sync objects are not considered.
- The syntax of script
statements and functions is not checked.
- Existing ACTIVATE_UC_OBJECT, :EXIT, :STOP, :WAIT
etc. are not recognized and not taken into account.
- Forecasts do not take Include objects into
account.
- The agent setting regarding the maximum number
of jobs that can be processed at the same time is not considered.
See also:
User Guide - Forecast
