Time events are one way of starting Jobs and Orders, with Start Times being set at a particular time of day, weekday, day of month etc. Start times can be single or repeating and can be grouped together in Schedules.
Job scheduling activities can also be limited to Time-slots:
- Jobs would have to wait for a time-slot to become available, e.g. between 08:00am and 11:00am.
- Jobs and Orders can be started when a predefined point in time has been reached: time of day, weekday, day of the month, a date relative to end of month etc.
- Start times can be:
- single - e.g. 12:00
- repetitive - for example:
- every 30 minutes between 09:00 and 18:00, Mondays to Fridays
- on the last day of every month at 18:00
- Time events can either be:
- Start times can be specified in the JobScheduler's local time or a time specified for any desired time zone.
Job activities can be limited to time-slots. JobScheduler supports any number of time-slots, which can be configured according to individual job requirements.
- Planned system outages or system backup intervals can be configured that prevent any jobs from being executed.
- Time-slots are the allowed operating periods for jobs, e.g. between 8:00am and 10:00am. They can be configured independently of the event that triggers the start of a job, e.g. at 8:30am.
- Job starts that are triggered outside of a time-slot will be automatically postponed until the next available time-slot.
- Exclusive time-slots for holidays can be configured either for individual or for all jobs.
Read more on this feature in the Run Time documentation.
The JobScheduler Object Editor, JOE provides a GUI for the configuration of Job and Order Run-times, and Schedules.