Enum SchedulerAccess
- Namespace
- Quartz
- Assembly
- Quartz.dll
How much an operation on a scheduler may change, which is what an operator role grants: every operation the HTTP API, the dashboard and the dashboard agent carry needs one of these three. Added in 4.8.
public enum SchedulerAccess
Fields
Administer = 2What changes what a scheduler holds, or ends it: adding, scheduling, rescheduling, editing and deleting jobs, triggers and calendars, the execution limits, clearing, shutting down, and triggering a job now with job data.
Operate = 1What changes what a scheduler is doing without changing what it holds: start and stand-by, pausing and resuming, triggering a job now without job data, interrupting, resetting a trigger from its error state, and backfilling.
View = 0Every read: the listings, the details, the history, the live events, and the three bulk fetches, which take a body of keys and change nothing.
Remarks
The levels are ordered, and each includes the one below it: an operator may view, and an administrator may operate. The table of which operation needs which level is in the HTTP API's documentation, under "Operator roles", and a test holds it to the routes.
Triggering a job now is Operate, except with a non-empty job-data map, which is
Administer: a stored NativeJob reads the command it runs from its job data, so
supplying data is naming what runs. Nothing below Administer can name a job type or
supply job data.