Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 8

changes.mady.by.user Alan Amos

Saved on

compared with

New Version 9

changes.mady.by.user Alan Amos

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: 'Configuration' added

...

Excerpt

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.

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 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.

...

Read more on this feature in the Run Time documentation.

Configuration

The JobScheduler Object Editor, JOE provides a GUI for the configuration of Job and Order Run-times, and Schedules.

In addition, the JOC Cockpit Web GUI comes with a Run-time Editor that can be used by users with the appropriate permissions to make temporary changes to Job and Order Run-times and Schedules.