Study guide

2.3 Service Level Agreements (SLAs) & Urgency Calculations

Pegasystems Certified Pega System Architect CSA

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Architecture Foundations

1.1 Certified Pega System Architect Exam Format, Blueprint & Strategy 1.2 Pega Architecture & Enterprise Class Structure (ECS) 1.3 Studio Environments: App Studio, Dev Studio, Admin Studio & Prediction Studio

2 Chapter 2: Case Lifecycle Design & Core Workflows

2.1 Case Types, Stages, Processes, and Steps 2.2 Routing Strategies: Worklists, Work Queues, and Teams 2.3 Service Level Agreements (SLAs) & Urgency Calculations

3 Chapter 3: Advanced Case Management Patterns

3.1 Multi-Step Processes, Parallel Processing & Sub-processes 3.2 Child Cases, Data Propagation & Wait Steps 3.3 Optional Actions, Approvals & Case Resolution 3.4 Duplicate Case Detection, Automation Shapes & Automated Correspondence

4 Chapter 4: Data Modeling & Data Page Architecture

4.1 Data Objects, Property Modes & Page Types 4.2 Data Pages: Scope, Types & Refresh Policies 4.3 Data Transforms & Object Mapping

5 Chapter 5: Business Logic, Calculations & Decisioning

5.1 Declare Expressions & Declarative Network Chaining 5.2 Decision Tables & Decision Trees 5.3 Integration Connectors, Systems of Record & Error Handling

6 Chapter 6: User Interface & User Experience Design

6.1 Traditional UI vs Constellation Architecture 6.2 Views, Dynamic Layouts, Design Templates & Action Sets 6.3 Form Validation, Edit Validate & WCAG Accessibility 6.4 Form Views: Default vs Hierarchical Forms, Field Groups & Primary Fields

7 Chapter 7: Rule Architecture & Rule Resolution

7.1 Rulesets, Versioning & Ruleset Stack Hierarchy 7.2 The Rule Resolution Algorithm 7.3 Circumstancing & Rule Specialization

8 Chapter 8: Security & Access Control

8.1 Authentication, Operator Records & Access Groups 8.2 Role-Based Access Control: Access Roles, ARO & Privileges 8.3 Attribute-Based Access Control (ABAC), Encryption & Audit Trails 8.4 The Security Checklist & Secure Deployment

9 Chapter 9: DevOps, Testing & Application Quality

9.1 Guardrail Compliance, Best Practices & Performance Profiling 9.2 Automated Testing: Pega Unit Test Cases & Scenario Testing 9.3 Packaging, Branching & Deployment Manager CI/CD

10 Chapter 10: Reporting & Operational Analytics

10.1 Report Definitions: Querying, Columns, Summaries & Joins 10.2 Filtering, Parameters & Column Exposure Optimization 10.3 Insights, Visual Dashboards & Business Metrics

11 Chapter 11: Mobility, Digital Channels & Portals

11.1 Mobile Channel Configuration & Offline Processing 11.2 Web Mashup, Digital Channels & Constellation Embed 11.3 Channels, Personas, Portals & Landing Pages

12 Chapter 12: Center-out Architecture, Enterprise Reuse & Agile Delivery

12.1 Center-out Business Architecture & the Case for Pega 12.2 The Situational Layer Cake, Modules & Enterprise Reuse 12.3 Agile Workbench, Workspaces, Branches, Delivery Roles & the Estimator

13 Chapter 13: Pega GenAI for System Architects

13.1 Pega Blueprint: Creating, Importing & Modifying an Application Design 13.2 Pega GenAI Autopilot & Pega GenAI Coach 13.3 Pega GenAI Connect Rules, Knowledge Buddy, Agents & Tool Rules

2.3 Service Level Agreements (SLAs) & Urgency Calculations

Key Takeaways Explain This Topic AI

Service Level Agreements (Rule-Obj-ServiceLevel) enforce business commitments for work timeliness by establishing milestone intervals and automated escalation actions.

The four SLA intervals are Start of interval (trigger event), Goal (target completion), Deadline (required completion), and Passed Deadline (recurring overdue intervals up to a maximum repetition limit).

Total assignment urgency (pyUrgencyAssignWork) dynamically sums assignment initial urgency (default 10), case urgency (pyUrgencyWork), and milestone increments, capped strictly at 100.

Escalation actions execute automatically when milestone intervals expire, enabling urgency adjustments, manager/assignee notifications, or automated reassignment to work queues.

SLAs operate across three hierarchy tiers—Case-level, Stage-level, and Assignment-level—with assignment SLAs directly driving operator prioritization in Get Next Work.

Last updated: September 2026

2.3 Service Level Agreements (SLAs) & Urgency Calculations

In enterprise operations, completing work accurately is only half the battle—work must also be completed on time. A Service Level Agreement (SLA) in Pega Platform defines business commitments for work timeliness, tracks milestone deadlines, and triggers automated escalations when those commitments are at risk of breach.

SLAs directly manipulate Urgency , a numerical metric that drives the Get Next Work engine to prioritize critical tasks across the enterprise.

1. SLA Rules and the Four Time Intervals

An SLA is defined using a Service Level rule ( Rule-Obj-ServiceLevel ). An SLA rule measures time across four standardized operational intervals: Start of Interval ────[ Goal ]────> [ Deadline ] ────[ Passed Deadline ]────>

  • (T=0) Target Time Required Time (Repeats N times)
  • The Four Milestone Intervals

Start of Interval ( T = 0 T=0 T = 0 ) :

Defines when the SLA timer begins ticking.

For an assignment SLA, the interval typically starts the moment the assignment shape is instantiated ( pxCreateDateTime ).

Can be configured to start dynamically based on a future DateTime property (e.g., .PolicyEffectiveDate or .ScheduledAuditDate ) or calculated via a When rule.

Goal Interval :

Defines the targeted or ideal duration within which the work should be completed.

Represents organizational excellence and optimal customer service.

Example: "Review insurance claims within 4 business hours."

Deadline Interval :

Defines the mandatory duration within which the work must be completed before it is officially late.

Represents contractual commitments, legal compliance limits, or regulatory boundaries.

Example: "Adjudicate claim within 24 hours of filing."

Note : Deadline time is measured from the Start of Interval , not from the expiration of the Goal!

Passed Deadline Interval :

Begins after the Deadline has expired without the task being completed.

Unlike Goal and Deadline (which fire exactly once), the Passed Deadline interval can be configured to repeat at fixed increments (e.g., "Every 2 hours") up to a defined repetition limit (e.g., "Repeat 3 times").

Used for escalating alerts and urgency increments until the overdue task is completed.

2. Urgency Calculation Mechanics

In Pega, task priority is quantified through Urgency —an integer value that spans from 10 to 100 .

Core Urgency Properties

.pyUrgencyWork : The baseline urgency of the case instance. Configured on the case type or case-level SLA (default value = 10 ).

.pyUrgencyAssign : The initial baseline urgency of an individual assignment step (default value = 10 ).

.pyUrgencyAssignWork : The final combined urgency of an active assignment, evaluated by Get Next Work.

The Platform Urgency Ceiling Rule Maximum Urgency = 100 \mathbf{\text{Maximum Urgency} = 100} Maximum Urgency = 100

No matter how many urgency increments an SLA applies, the platform strictly caps .pyUrgencyAssignWork at 100 . Any calculated value exceeding 100 is clamped to 100.

Master Urgency Formula pyUrgencyAssignWork = min ⁡ ( 100 , pyUrgencyWork + pyUrgencyAssign + Δ Goal + Δ Deadline + ( N repeats × Δ PassedDeadline ) ) \text{pyUrgencyAssignWork} = \min\Big(100,\; \text{pyUrgencyWork} + \text{pyUrgencyAssign} + \Delta_{\text{Goal}} + \Delta_{\text{Deadline}} + \big(N_{\text{repeats}} \times \Delta_{\text{PassedDeadline}}\big)\Big) pyUrgencyAssignWork = min ( 100 , pyUrgencyWork + pyUrgencyAssign + Δ Goal ​ + Δ Deadline ​ + ( N repeats ​ × Δ PassedDeadline ​ ) )

Where:

pyUrgencyWork \text{pyUrgencyWork} pyUrgencyWork is the current case urgency (default 10).

pyUrgencyAssign \text{pyUrgencyAssign} pyUrgencyAssign is the assignment starting urgency (default 10).

Δ Goal \Delta_{\text{Goal}} Δ Goal ​ is the urgency increment applied if Goal expires.

Δ Deadline \Delta_{\text{Deadline}} Δ Deadline ​ is the urgency increment applied if Deadline expires.

N repeats N_{\text{repeats}} N repeats ​ is the number of completed Passed Deadline intervals.

Δ PassedDeadline \Delta_{\text{PassedDeadline}} Δ PassedDeadline ​ is the urgency increment applied at each Passed Deadline repetition.

3. Automated Escalation Actions

When an SLA milestone (Goal, Deadline, or Passed Deadline) expires, Pega can automatically trigger one or more Escalation Actions :

Adjust Urgency : Adds an integer value to the assignment's current urgency, elevating its position in Get Next Work.

Send Notifications : Dispatches correspondence (email, SMS, or mobile push) to:

The assigned operator (e.g., "Your assignment is nearing deadline").

The operator's reporting manager ( .pyReportTo ).

The Work Group Manager or case parties.

Transfer Assignment : Programmatically moves the assignment from an individual's stagnant worklist to a senior operator, a supervisor, or a shared team Work Queue.

Execute Custom Action : Invokes a custom activity or workflow to log audit records, notify external monitoring systems, or trigger compliance workflows.

4. Hierarchy of SLA Levels

Pega allows SLAs to be attached at three different architectural tiers in the Case Life Cycle:

SLA Level Scope of Operation When It Starts When It Ends Impact on Urgency

Case-Level SLA Entire case life cycle When the case is instantiated ( pyID created). When the case achieves a Resolved- status. Establishes the baseline case urgency ( .pyUrgencyWork ) for all assignments.

Stage-Level SLA Specific stage When the case enters the stage. When the case exits or transitions from the stage. Monitors cumulative time spent in a stage; can escalate if a stage stalls.

Assignment-Level SLA Specific assignment step When the assignment is created and routed. Immediately when the user completes the assignment. Directly increments .pyUrgencyAssignWork to drive Get Next Work.

SLA Interaction Rules

When an assignment is active, its total urgency combines the Case-level urgency with the Assignment-level urgency .

If an assignment is completed before the Goal expires, the assignment SLA terminates immediately: no Goal or Deadline increments apply, and no escalations fire.

Completing an assignment does not stop the Case-level SLA; the case SLA clock runs continuously until the case reaches resolution.

5. Comprehensive Worked Mathematical Example

To see how SLA mathematics and escalation actions operate in practice, trace the following real-world scenario:

  • Case Configuration Parameters
  • Case Baseline Urgency ( .pyUrgencyWork ): 10
  • Assignment Initial Urgency ( .pyUrgencyAssign ): 15

Goal Interval : 2 hours | Urgency Increment: +15 | Escalation: Send notification to Assignee.

Deadline Interval : 4 hours | Urgency Increment: +30 | Escalation: Send notification to Manager ( .pyReportTo ).

Passed Deadline Interval : 1 hour | Urgency Increment: +15 | Repeat Limit: 3 times | Escalation: Adjust urgency.

Step-by-Step Chronological Progression

Elapsed Time Life Cycle Event Urgency Calculation Math Total Assignment Urgency ( pyUrgencyAssignWork ) Triggered Escalation Action

T = 0 h T = 0\text{ h} T = 0 h Assignment Created Case (10) + Assign (15) \text{Case (10)} + \text{Assign (15)} Case (10) + Assign (15) 25 Initial assignment routed to work queue.

T = 2 h T = 2\text{ h} T = 2 h Goal Reached 25 + Goal Increment (15) 25 + \text{Goal Increment (15)} 25 + Goal Increment (15) 40 Notification email sent to Assignee.

T = 4 h T = 4\text{ h} T = 4 h Deadline Reached 40 + Deadline Increment (30) 40 + \text{Deadline Increment (30)} 40 + Deadline Increment (30) 70 Escalation email sent to Manager ( .pyReportTo ).

T = 5 h T = 5\text{ h} T = 5 h Passed Deadline #1 70 + Passed Deadline (15) 70 + \text{Passed Deadline (15)} 70 + Passed Deadline (15) 85 Urgency incremented; task rises in GNW.

T = 6 h T = 6\text{ h} T = 6 h Passed Deadline #2 85 + Passed Deadline (15) 85 + \text{Passed Deadline (15)} 85 + Passed Deadline (15) 100 Urgency achieves platform maximum ceiling.

T = 7 h T = 7\text{ h} T = 7 h Passed Deadline #3 100 + 15 = 115 → 100 100 + 15 = 115 \rightarrow \mathbf{100} 100 + 15 = 115 → 100 100 (Clamped) Final repeat executed; urgency remains capped at 100.

T > 7 h T > 7\text{ h} T > 7 h Further Repeats Halted Max repeats (3) reached 100 No further SLA actions fire; assignment remains at urgency 100.

6. Business Days vs. Calendar Days

Pega SLA rules can calculate milestone intervals using two distinct timing models:

Calendar Time (24/7) : Standard elapsed clock time. 24 hours equals 24 continuous clock hours regardless of weekends or holidays.

Business Days (Calendar-Driven) : Evaluated against a business calendar ( Data-Admin-Calendar ). Pega takes into account company operating hours (e.g., Monday through Friday, 8:00 AM to 5:00 PM) and recognized company holidays.

Example : If an assignment with an 8-hour business day SLA is created on Friday at 4:00 PM, the Goal interval does not expire until Monday at 3:00 PM!

Loading diagram... Service Level Agreement (SLA) Progression and Urgency Curve