On Demand / SLA Console
Preventive Maintenance / SLA Console

Setting Priority Levels for an SLA

Optionally, a request for on demand work can have a priority level, such as High, Medium, Low, Emergency, or Non-Emergency.

For each priority level, you can assign a unique set of response procedures. Thus, similar requests that vary in priority level can have entirely different responses, with different service providers, different approval routings, and so forth. For example, the SLA governing an installation request with a priority of Urgent can define a different workflow than does an SLA for a an installation request with a priority of 1-Week.

There are a few ways to set up priority levels:

Define Priority Levels

You define priorities as part of Step 1 - Request accessed by clicking Add New SLA > On Demand SLA, and then selecting Edit Details from the quick action pop-up form that appears. By default, an SLA does not have priorities.

To specify priorities:

  1. On the Step 1 - Requests form, select the Use multiple priority levels check box.

    The form expands to show additional fields for priorities:

  2. To enable the requestor to select a priority, select the Client Choose Priority check box. This means that the requestor will see all priorities and will be able to select one.
  3. To enter the priority text that will appear to the user, type the text in the box for each Level that you want to use.
  4. If you wish to set one of the priorities as the default (see the second bullet point scenario, above), enter the title for the default priority in the Level 1 field, and do not select the Client Choose Priority check box. For this option, you must define an Approval step for the Request status for the default priority for the work request. See Adding an Approval Step for Work Requests.
  5. Click Proceed to Next Step.

    The Step 2 - Workflow step appears. When you define multiple priorities, the Step 2 - Workflow form will have a separate tab for each priority, so that you can define a different workflow for each for each of them.

Copyright © 1984-2014, ARCHIBUS, Inc. All rights reserved.