Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Creating a service-level agreement (SLA) rule

Updated on March 29, 2022

Enforce service-level agreements (SLAs) and maintain timely resolution of cases by defining the goal, deadline, and passed deadline time intervals. By creating an SLA rule, you can quickly reuse the SLA settings for multiple assignments.

For example, you can notify a manager about a passed goal and deadline, and then transfer the assignment to another user. You then can reuse the setting for multiple cases and assignments, and as a result, manage time and resources efficiently.
Creating an SLA rule in Dev Studio is appropriate for only advanced developers. To take advantage of low-code tools, define SLAs in App Studio. For more information, see Setting service-level agreements (SLAs) for case resolution and Setting service-level agreements (SLAs) for stages, processes, and steps.
  1. Create an SLA rule:
    1. In the navigation pane of Dev Studio, click Records.
    2. Expand the Process category, and then click Service Level Agreement.
    3. In the Label field, enter a short description for the rule.
    4. In the Context section, select an application to which the rule applies.
    5. In the Apply to field, select a class to which the rule applies.
    6. In the Add to ruleset field, select a ruleset for the rule.
    7. Optional: To enable traceability of the rule, in the Current work item section, enter the work item to associate with the rule, for example, a bug ID.
    8. Click Create and open.
  2. On the General tab, in the Initial urgency field, define the urgency for the assignment that you can associate with the rule by entering an integer between 0 and 99.
    An assignment has the default urgency of 10. The system adds the value in this field to arrive at the initial urgency.
    For example: If you enter 10, the initial urgency is 20.
  3. In the Assignment ready list, define the starting time for the assignment:
    • To send the assignment to a worklist or a work queue immediately after the user or an automation creates an assignment, select Immediately.
    • To define the starting time by using a Date/Time value, select Dynamically defined on a property, and then, in the Get Date Time From field, enter the property that references the value.
    • To start the assignment after a period of time, select Timed delay, and then, in the Days, Hours, and Minutes fields, specify the delay.
  4. In the Service level definitions section, in the Calculate service levels field, select a method of calculating intervals for goal and deadline:
    • To manually specify the intervals, select Interval from when assignment is ready, and then, in the Goal and Deadline sections, enter the intervals.
    • To define the time intervals as values of properties, select Set the value of a property, and then, in the Goal and Deadline sections, in the Property fields, enter the properties that reference goal and deadline dates and times.
  5. Optional: To facilitate timely resolution of work, define escalation actions that occur when the goal and deadline pass:
    1. In the Amount to increase urgency field, enter the number that an application adds to the initial urgency then the time interval passes.
      For example: If the initial urgency is 10, and then you configure the rule to add 20 when the goal passes, the total urgency is 30 after the goal passes.
    2. In the Actions section, in the Select action row, click Edit.
    3. In the Perform action list, select an action that occurs when the time interval passes, and then provide relevant details if necessary.
      For example: To make an application perform a data transform, provide the data transform.
      Note: Ensure that the action that you select does not perform the Commit method because the commit occurs at the end of SLA rule processing ends. Providing an action that performs the Commit might cause issues.
    4. Optional: To perform the escalation action only under specific circumstances, in the When field, enter a when rule.
      Result: An escalation action occurs if the when rule returns a true value.
    5. Optional: To add more escalation actions, click Add an action, and then repeat steps 5.a through 5.d.
    Tip: You can define escalation actions for goal, deadline, and passed deadline events.
  6. Optional: To define the number of the passed deadline events and the time when the passed deadline events occur, in the Passed deadline section, enter the appropriate values.
  7. Click Save.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us