...
- Calendar Management with the JobScheduler 1.x branch is focused on
- Run-time Rules based on days, weekdays, monthdays, ultimo days etc.
- Holiday Calendars that specify non-working days.
- Calendar Management with the 1.x branch includes a number of gaps:
- Sequence of Rules
- Run-time Rules are applied in first place,
- Rules for non-working days are applied in second place.
- This makes it hard to define specific rules such as the second last working day in a month.
- Scope of Periods
- Periods are by definition strictly focused on a single day and are re-calculated at midnight.
- This makes it almost impossible to define rules for repeated execution that would not fit into a period, as e.g. to execute a job every 5 hours or every 2nd day of a month.
- Calendar Range
- When used with weekday rules then Holiday Calendars do not specifiy a start or date & end date and therefore cannot be used to specify e.g. a Sunday to be a holiday within the scope of specific months.
- Holiday Calendars cannot expire, therefore it is not possible to e.g. to specify a job not to be executed starting from begin of next year.
- Sequence of Rules
...
- This feature is introduced for the JobScheduler 1.x branch. It will replace the internal run-time calculation module of the JobScheduler Master.
- Holiday Calendars will be dropped with the JobScheduler 2.x branch as holidays can be specified as excluded dates within a Business Day Calendar.
Documentation
References
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|