DAY 10

Routing Work
Agenda
Day 10

• Routing Assignments

• Push based Routing - Worklist

• Pull based Routing – Workbasket

• Skill based Routing

• Other Routing types.

• Working with case manager/case worker.

2
UseCase
Consider Candidate Onboarding application has developed the user interface for
candidate information along with various property validations in-place.
Now the assignment needs to be routed to the manager who need to either approve or
reject based on result from background verification checks.

1. Route to manager for approval/rejection.

2. Route upload documents step to Workbasket for HR to pickup.

3. Lock Rules to restrict action by other operators.

3
Work Structure
Work Types define the broader view of work to be performed.
Work Items define the work to be executed.
Work Objects are the executed work items which are identified using WorkObject ID or
PYID or CaseID For ex: C-12, D-15 etc

Work Objects are default stored under PC_WORK Table.

1. Covers and folders are two built-in facilities that allow your application to support
collections of work items. In contrast to covers:

2. One work item may be associated with multiple folders, but only with one cover.

3. Members of a folder can belong to different work types, which need not belong
all in a single work pool.

4. The relationships between folder work items and their contents may be many-to-
many.

4
Routing
Routing enables various operators to work upon assignments and complete them.
There are 3 types of routing in PEGA.

1. Push based Routing – ToWorklist

2. Pull based Routing – ToWorkBasket

3. Skill based Routing – ToSkilledGroup and ToSkilledWorkBasket

WorkList – Assignments can be completed by individual operator and the assignment

Is added under the operator’s worklist. Can be completed from caseworker. Called as
push based routing. Stored under PC_ASSIGN_WORKLIST Table.

WorkBasket – Assignments can be stored in workqueue (Workbasket) where operator

who belongs to workgroup can manually pickup the work using “GetNextWork” once its
pickedup, it is now added to operator’s worklist. Called as pull based routing. Stored
under PC_ASSIGN_WORKBASKET Table.
5
Routing
Skill based routing – Assignments can also routed based on operator’s skill. Operator’s
skill rating needs to satisfy the required criteria.

To Route assignment to individual operator – Assignment type – ToSkilledGroup.

To Route assignment to skilled workbasket – Assignment type – ToSkilledWorkbasket

6
 Routing
To WorkList To Skilled Worklist

To Workbasket To Skilled Workbasket

7
Rule Checkout/Checkin
Instances of Rule- can have functionality of Checkout/Checkin while data- class instances does not
incorporate this functionality.

1. A checkout is a private copy of a Rule- instance that you update and later check in to replace a
base rule version. All checked-out rules reside in a ruleset that is only visible to your operator
known as your personal ruleset.

Two types of checkouts are supported:

1. Standard checkout – All other users are blocked from checking out this rule until you check in
your changes.

2. Private checkout – A private checkout is like a standard checkout, except that it does not block
checkouts for other users. Use this option for quick debugging without interrupting
development by other team members.

The check in process replaces a base rule version with a private copy of a Rule- instance that you
checked out and updated.

You can check in two types of checkouts:

1. Standard checkout – When you check in, your version replaces the base version of the rule.

2. Private checkout – When you check in, you can replace the base version of the rule or create a
new rule in a branched ruleset.
8
Private Edit
Private Edit
Rules which are present
In locked rulesets cannot
Be modified.
Inorder to modify them, they needs to be added to an unlocked ruleset or checked out to a branch.

Check Out functionality needs to be configured at 2 areas.

1. Operator > Security Tab > Allow Rule checkout

2. Ruleset > Security Tab > Use Rule Checkout? Should be enabled.

9
Rule Checkout
When you do checkout, we can modify the rule and changes done will be saved once
we checkin. Till then, A Lock is acquired and other operator sees the rule as locked by
the operator ID.
However, He can still modify the rule in PRIVATE EDIT Mode. However, which
operator checks in first. Those changes reflected in the rule. This is called Optimistic
Locking

10
Rule Checkout
When you do checkout, we can modify the rule and changes done will be saved once
we checkin. Till then, A Lock is acquired and other operator sees the rule as locked by
the operator ID.
However, He can still modify the rule in PRIVATE EDIT Mode. However, which
operator checks in first. Those changes reflected in the rule. This is called Optimistic
Locking

11
Rule Checkout
It is also possible to discard any unsaved changes before proceeding with Checkin.
Checkin along with provide comments for changes done.

In Development environment, Developers are advised to checkin the rule once

modifications are done using Bulk Actions tool.

12