How to set a service level for a work object

Commonly, service level rules are associated with assignments — steps in a business process that require human input or decisionmaking.

Optionally, you can associate a service level rule with a work object, so that as the work object ages the escalation processing defined in the service level rule occurs. The start time for the goal and deadline periods is the date and time the work object was created (or most recently reopened). Service level processing ends when the work object is resolved.

Examples

Your business objective may be that the user organization resolved any work objects involving amounts of $1,000.00 or more within three business days. You can set a goal time of two business days in a service level rule associated with the work type. For work objects that remain open after two business days, automatic escalation processing can occur. Escalation processing can:

• Increase the work object urgency
• Increase the assignment urgency of all assignments for the work object
• Notify the current operator with an e-mail
• Notify the manager of the operator, and so on.

In another business process, work objects not resolved within 24 hours may automatically be withdrawn or cancelled, an approach sometimes called "fill-or-kill."

How it works

When enabled, this feature causes the standard flow rule Work-.OverallSLA to execute in parallel with other flows for the work object. This flow contains a single assignment that can be ignored; resolution of the work object activates a standard ticket named Work-.Status-Resolved that cancels the assignment. Ordinarily, you don't need to modify or override the flow rule, but you do need to identify a destination for the assignment and identify a service level rule to run.

The Pega-ProCom agent performs work object escalation processing, as with service levels associated with assignments.

Procedure

To enable this capability:

1. Identify or create a service level rule in your application that is to perform the desired escalation, choosing appropriate intervals for the goal time and deadline time. If you create a new service level rule, set the Applies To key part to a work type or work pool as appropriate.
2. In the model rule for a work type, set the value of the pySLAName property to the second key part of the service level rule.
3. By default, the routing activity Work-.ToOverallSLA sends the assignments produced by this flow to a workbasket named [email protected], where org.com is the organization of the originator who entered the work object. Such assignments can be ignored; they are deleted automatically when the work object is resolved. If this destination is suitable in your setting, make sure your system includes a workbasket with that name. Alternatively, you can override the simple routing activity, setting a different workbasket name as the AssignTo parameter.
4. The OverallSLA flow execution starts when a new work object is entered. It continues until the work object is resolved. If a resolved work object is later reopened, the OverallSLA flow execution starts again.

	deadline, escalation, goal, service level
	About Service Level rules Understanding the Pega-ProCom agent
	Atlas — Standard service level rules

Process category