A service level rule is an instance of the Rule-Obj-ServiceLevel type. Each service level rule defines one to three time intervals, known as goals, deadlines, and late intervals, that indicate the expected or targeted turnaround time for the assignment, or time-to-resolve for the work object. These provide metrics or standards for the business process.

A developer can associate service level rules with assignments in a flow and with the entire flow. For example, a developer can set a goal of 30 minutes to call a customer back and a deadline of four hours. (The time interval starts when the assignment is created, not when a user begins processing the assignment.)

• For assignments, the service level rule is referenced in the Assignment Properties panel of the assignment task. See Flow Rules — Editing in Visio — Associating a service level with an assignment.
• For the overall work object, the service level rule is identified in the standard property .pySLAName, typically set up through a model for the class. (The default value is the Default service level.)

The Pega-ProCom agent detects service levels not achieved — unmet goals or deadlines — promptly. If an assignment is not completed before the time limit, the system can automatically notify one or more parties, escalate the assignment, cancel the entire flow, and so on.

Don't confuse service level rules with service rules (Rule-Service- classes). Service rules define how an external system accesses your Process Commander application to run activities.

Service level rules are sometimes informally called service level agreements or SLAs.

Using the Monitor Activity workspace, managers can compare real-world results of their organization against the goals and deadlines defined in service level rules.

	assignment, deadline, escalation, goal, timeliness, work object, worklist
	About Service Level rules Troubleshooting — Service level rules not executing Working in the Monitor Activity workspace
	Atlas — Standard Service Level rules

Definitions — S