...
A number of behaviors can be specified for each Period in addition to the default suppress execution used above. These are:
- before non-working day
- i.e. execute on the last preceding day that is not in a Non-Working Day Calendar
- after non-working day
- i.e. execute on the first succeeding day that is not in a Non-Working Day Calendar
- (the default) suppress execution and
- ignore the non-working day
| Info | ||
|---|---|---|
| ||
Consider the following example:
|
...
The effect of changing the different On Non-Working Day settings will have on execution dates will be described next. The effect of these changes can be best seen in the Daily Plan for the Order.
Behavior with
...
Execution before non-working day
The last execution date in 2017 is the Wednesday, 27th of December and the last Working day the 29th. The execution for Monday, 1st January 2018 will be moved to Sunday, the 31st December, as can be seen in the next two screenshots below showing parts of the Daily Plan for 2017 and for 2018 respectively.
2017
2018
Behavior with
...
Execution after non-working day
...
With this setting the Order will be executed, for example, on the day after the first of January as shown in the next screenshot:
...
Note that the screenshots shown here have been generated after changing the On Non-Working Days behavior for both the 15:00 and 21:00 Periods. It could be readily conceived that there would be a use case for one Period in a Working Day that would be suppressed on Non-Working Days and another Period where execution took place, regardless of whether or not a day was defined as Non-Working. In this case the day will be marked in the Daily Plan as an execution day and there will be no indication that not all Periods will be executed on that day.
...