Job and order triggers

Introduction

JobScheduler jobs and orders can be started / triggered in a number of ways:

Time events (for example from Schedules or date/time objects)
Manually using the JobScheduler's web-based JOC - JobScheduler Operations Center Interface
From run-time events - such as the completion of another job chain
Directory Monitoring and File Watching events - for example, when a file is added to or deleted from a folder
From another job via the API Interface and from another application via the XML Interface

Job activities can also be limited to time-slots:

Jobs are would have to wait for a time-slot to become available, e.g. between 08:00am and 11:00am.
JobScheduler supports any number of time-slots, which can be configured according to individual job requirements.

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

Read more on this feature on the Start Times page and in the Run Times documentation.

Read more on this feature in the Event Handling section and in the XML command documentation.

Job starts can be triggered by Directory Monitoring - should changes in directories or the addition or deletion of files in directories occur.
JobScheduler offers File Watching and will start jobs automatically for individual files arriving in a directory.

Read more on these features in the directory monitoring and file orders documents.

Program-controlled job starts can be made using the JobScheduler API Interface with a Scripting language and using the XML Interface.
Jobs can be started from the command line.

Jobs are would have to wait for a time-slot to become available, e.g. between 08:00am and 11:00am.
JobScheduler supports any number of time-slots, which can be configured according to individual job requirements.

See Start Times for more information.

Content by label

There is no content with the specified labels