This screen allows the scheduling of a new task. A task is based upon a pre-defined workflow.
The details of the screen:
Text description of the scheduled task
An identifier used for Event/Action mappings (see: Setting Up Event-Action Configuration)
Drop down list, allows the selection of a pre-defined workflow.
Drop down list, allows the selection of a pre-defined What-if Scenario.
The first task run is done at the Start time. Since 2021.01 secondes can be specified as well.
Scheduling of the task stops at the End Time. Since 2021.01 secondes can be specified as well.
Mode with several options,
once only - add to queue in order to run the task immediately
fixed interval - schedules tasks at fixed interval
One or more times each day - schedules a task on fixed times each day
one or more days each month - schedules a task a series of days per month to be selected, configurable options for timezone with daylightsaving can be used for this option
Yearly - Since 2020.02. Schedules a task on a specific day of the month and will be repeated yearly. Start time is always GMT-0.
Allows to define a period of time over which the T0 of the forecast itself should be set back in relation to the Start time of the forecast run.
|Forecast length||Optional element for overruling the pre-defined forecast length. NB. if an end time is specified in the timeseriesSet, it needs to be made overrulable in order for this forecast length option to have effect|
Allows to set the expiry time of data produced by taskruns. Default is to take the runExpiry time of the workflow. If this is not defined, the expiry time configured on the MC is the default.
Allows workflows to be split up run in parallel on multiple Forecasting Shells (e.g. for ensembles).
This needs the attribute maxEnsembleParts in the Workflowdescriptor to be set to a value > 1.
The value entered is the number of parallel parts the task should be split into.
Tasks can have priority High or Normal.
Where before 2018.01 a task was either a failover task or not, a task now has three different options
1. Run Duty - Run this Task only on the Master Controller that owns it (default).
2. Run Duty and Failover - When the Duty Master Controller is in Failover mode, run this task on the top priority Failover Master Controller, but also run this task on the Duty Master Controller that owns it.
3. Suspend Duty in Failover - When the Duty Master Controller is in Failover mode, run this task on the top priority Failover Master Controller and do not run this task on the Duty Master Controller that owns it. This option also requires that the Duty Master Controller is not made the top MC in its own list of failover priorities.
Ticking the approve box will set the status of the forecast automatically to current after it has been completed.
Mode with several options,
All -No limitations on how many Forecasting Shells can run this workflow at the same time (default).
All One At a Time - The Task will not be dispatched when there are TaskRuns with the same workflowId present.
All Most Recent Only - If there are any taskRuns for this Task's workflowid already pending, those are cancelled first.
The different repeat modes have specific configuration options:
One or more times each day
One or more days each month
Since 2020.02. The days of month can be specified using the Month/Day day notation. Multiple dates can be specified by separating them with a spaces. So for example to schedule a task yearly on the 16 of july, you specify: 7/16. The task will be run yearly at midnight GMT-0 on july the 16th.
In case a MC_SystemAlerter workflow is selected, it is required to upload the task properties for the task.
For example, email alert properties can be uploaded. See also: 05 Setting up sending emails on events