You are currently viewing the legacy RunMyJobs documentation site. This site will be taken down later this month.
All current and future RunMyJobs documentation, including versions 2023.3 and later, can be found here.
Please update your bookmarks. Use the version dropdown menu to select the documentation you need.

← IBP ConnectionsServiceNow →

Privileges Required to use SLA Component

To use the SLA Component, you need one of the following:

  • scheduler-administrator or redwood-administrator role.
  • scheduler-user or redwood-login role in combination with the following system-wide, partition-wide or object-level privileges.

Built-in Roles

  • The scheduler-administrator or redwood-administrator built-in role provides full control over the SLA Component.

Creating an SLA Rule

  • View - on partition REDWOOD.
  • View - on library REDWOOD.Custom_SLA.
  • View - on datum definition REDWOOD.SLA_LastAlert.
  • View - on datum definition REDWOOD.SLA_StartAlert.
  • View - on the process definition for which you wish to set up the alert.
  • View Process - on all queues of the processes for which you want to set up the alert.

Setting up SLA

  • View - on partition REDWOOD.
  • View - on library REDWOOD.Custom_SLA.
  • View - on datum definition REDWOOD.SLA_LastAlert.
  • View - on datum definition REDWOOD.SLA_StartAlert.
  • Submit - on process definition REDWOOD.SLA_Maintenance.
  • Submit - on process definition REDWOOD.SLA_Monitor.
  • JobAdministrator - on a queue that has a process server that can run the process definition.
  • View - on a process server that can run the process definitions.

See Also

SLA Component

← IBP ConnectionsServiceNow →