...
| Excerpt |
|---|
Time events are one way of starting jobs, job chains and ordersJobs and Orders, with Start Times being set for at a predefined point in time such as time 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 timeTime-slots:
|
Start Times
- 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:
- specified for individual Jobs or Orders as Run Times or be
- grouped together
Read more on this feature in the Run Time Configuration documentation.
...
- in Schedules, which can be stored as separate JobScheduler Objects and reused for Jobs and Orders as required.
- Start times can be specified in the JobScheduler's local time or a time specified for any desired time zone.
Execution Time-slots
Job activities can be limited to time-slots. JobScheduler supports any number of time-slots, which can be configured according to individual job requirements.
...