Skip to main content


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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Using service levels (SLAs) in Pega 7

Updated on September 10, 2021

Summary

Service level (sometimes called SLA) functionality in Pega 7 lets you employ the most commonly used actions, such as notifications or advance flows, without having to configure activities. The service level form lets you create a series of actions simply by adding them to a list without the need for extra configuration. You can also apply When rules to conditionalize the actions.

Additionally, Pega 7 provides two flow actions that allow users to change a service level, or replace an existing service level, with one that is purpose-built for a specific situation. From the Case Designer, you can enable these service level flow actions at the case level so users from the user portal dashboard can update service levels at any time during case processing. These flow actions can be configured at the stage level, flow level or even the assignment level.

This article describes how to configure actions in a service level record and implement a flow action that lets users apply the record during case processing.

Example

Your application processes program fund cases for projects that several purchase requests can be associated with. This allows for organizing related purchase requests under one pre-authorized budget.

13.png

As currently configured, program fund case assignments have a goal of 2 days, a deadline of 3 days, and a default urgency of 10.

Management has created two program fund levels (silver and gold) based on the program amount. The service level goal and deadline dates are pulled in by one day and their urgencies escalate above the default value.

  • When the goal date is reached, a silver program notifies the assignee by email; a gold program notifies the manager. The system determines which programs are silver or gold using a when condition.
  • When the deadline date is reached, the system enables a local action that transfers the case to the user's manager.

You must design a service level record to meet these escalation requirements and define a case-wide local action so users can apply the record at any point in the case's process.

Create a service level record and When conditions

Do the following:

  1. Create two when records that evaluates the property .ProgramAmount as follows:
  • Silver Level — greater than 5,000 and less than 10,000
  • Gold Level — equal to or greater than 10,000
  1. Create a service level record named Escalated Request.
  2. In the Goal area, enter:
    • 1 in the Days field
    • 10 in the Urgency field
      01.png
  3. In the Escalation Actions (s) section, double-click the Select Action row to display the edit fields.
  4. Select Notify Assignee in the Perform Action field.
    02.png
  5. Select SilverLevel in the When field.
    03.png
  6. Click addrow.png to add a row. Select:
    • Notify Manager in the Perform Action field
    • Gold Level in the When field
      04.png
  7. In the Deadline area, enter:
    • 1 in the Days field
    • 20 in the Urgency field
  8. In the Escalation Action(s) section, open the first row for editing.
  9. Select:
    • Advance Flow in the Perform Action field
    • TransferToManager in the Flow Action field
      04a.png
  10. Save the service level record.

Configure the flow action to adjust service levels

Do the following:

  1. Select the Program Fund case type in the Cases Explorer.
  2. Open the Details tab and select the Case-wide local actionsEdit link. The Case-wide Local Actions dialog appears.
    06.png
  3. Click Add Item to add a row and select pyAdjustSLA (Adjust SLA) in the Flow Action field.
    14.png
  4. Click OK to save your update and close the dialog.

Test

For testing purposes, you can shorten the goal and deadline dates to observe the expected behavior.

Do the following:

  1. Create a program fund case in Stage 1, Program Fund Entry. Enter:
    • 15000 in the Program Amount field
    • Gold level program in the Program Description field
      16.png
  2. After the case is created, open the Information tab on the Review harness to display the amount and description.
  3. From the Actions menu, select Adjust SLA. The Adjust SLA action form appears.​
    20.png
  4. Select Escalated Request in the Specify an SLA field. The system populates the form with the goal, deadline, and action values you entered in the service level form.
    10b.png
  5. To review or edit the action parameter values, hover the mouse pointer over the information icon infoicon.png as shown here:
    10a.png
  6. Click the Submit button to apply the Escalated Request service level record.
  7. Approve the case. The assignment goal is adjusted using the revised 1 day value.
    11a_0.png
  8. When the goal date is reached:
    26.png
    Open the Audit tab on the user form. Note that the system started the Notify Manager action and created an email.
    22.png
  9. When the deadline is reached, the assignment is reassigned to the user's manager (Sales Manager).
    28.png

Updating goal and deadline dates

You can use the Adjust SLA Times flow action to update the dates on the current service level record. In this example, you will use the flow action to reset the goal and deadline dates you set in the Escalated Request service level record.

The flow action does not update the underlying service level record.

Do the following:

  1. Open the Program Fund Details tab.
  2. Open the Case-wide Local Actions dialog as described previously.
  3. Add the pyAdjustSLATimes (Adjust SLA Times) flow action.
    18.png
  4. Create a case and invoke the Adjust SLA Times flow action.
    23.png
  5. Override the current service level goal and deadline dates as shown here (one and two days from the current date, respectively):
    24.png
  6. Submit the flow action. The assignment goal date is reset as defined in the Goal Override field.
    25.png

Tags

Pega Platform 7.1.1 - 8.3.1 System Architect Lead System Architect Business Architect Experience Designer Pega Delivery Leader System/Cloud Ops Administrator Case Management Communications and Media Consumer Services Financial Services Government Healthcare and Life Sciences Insurance Healthcare and Life Sciences

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us