2.2 Routing Strategies: Worklists, Work Queues, and Teams

2.2 Routing Strategies: Worklists, Work Queues, and Teams

In Pega Platform, Routing is the automated mechanism that ensures human assignments are delivered to the right person or team at the right time. When a case step requires human intervention (such as reviewing an application, approving an expenditure, or inspecting collateral), the workflow engine generates an Assignment record and routes it to an operational destination.

Mastering routing strategies, organizational structures, and the Get Next Work algorithm is vital for ensuring high operational throughput and scoring high on the Pega CSA exam.

---

1. Push vs. Pull Work Distribution

Pega supports two fundamental paradigms for work allocation:

Push Model: Case Step ───────> Specific User Worklist (Assign-Worklist)

Pull Model: Case Step ───────> Shared Work Queue (Assign-WorkBasket)
                                      ▲
             Operator clicks GNW ─────┘ (Evaluates Urgency & Skills)

Push Routing (Worklist)

• Destination: An individual user's personal Worklist (class Assign-Worklist).
• Mechanism: The system directly pushes the task into a single operator's inbox. Only that specific operator (or an authorized delegate/manager) sees and opens the assignment.
• When to Use:
  • Strict individual accountability is required (e.g., a specific account manager owns the client relationship).
  • The task is a follow-up directly related to work the user initiated.
  • The worker has unique personal knowledge of the case history.
• Drawbacks: Vulnerable to bottlenecks. If the assigned operator is out sick, on vacation, or backlogged, the case stalls unless a manager intervenes.

Pull Routing (Work Queue)

• Destination: A shared Work Queue (historically known as a Workbasket, class Assign-WorkBasket).
• Mechanism: Assignments sit in a shared repository accessible to all qualified members of a team. Users retrieve work manually or leverage Pega's automated Get Next Work engine.
• When to Use:
  • High-volume, standardized processing (e.g., claims intake, document indexing, tiered customer support).
  • Load balancing across teams with identical or overlapping job functions.
  • Protecting SLAs by eliminating single-operator dependency.

---

2. The Four Standard Routing Targets

When configuring an assignment step in App Studio or Dev Studio, architects select among four core routing options:

---

3. Pega Organizational Structure

To route work accurately, Pega relies on an enterprise organizational model composed of five foundational entities:

Organization (Data-Admin-Organization)
 └── Division (Data-Admin-OrgDivision)
      └── Unit (Data-Admin-OrgUnit)

Cross-Functional Operational Layer:
Work Group (Data-Admin-WorkGroup)
 ├── Managed by: Work Group Manager (Operator)
 ├── Default Work Queue: Data-Admin-WorkBasket
 └── Members: Operators (Data-Admin-Operator-ID)

Core Entities

1. Organization (Data-Admin-Organization): The top level of the enterprise structure (e.g., UPlusBank).
2. Division (Data-Admin-OrgDivision): The secondary business unit (e.g., PersonalBanking).
3. Unit (Data-Admin-OrgUnit): The granular operational team or cost center (e.g., LoanOriginationEast).
4. Work Group (Data-Admin-WorkGroup): A logical, cross-functional grouping of operators that can span across divisions and units. A Work Group defines:
   • A Manager (an Operator ID responsible for oversight).
   • A Default Work Queue for team-level tasks.
5. Work Queue (Data-Admin-WorkBasket): A centralized queue where assignments reside until pulled by an operator or automated agent.
6. Operator (Data-Admin-Operator-ID): The user record containing credentials, access groups, primary work group, secondary work queues, and skill ratings.

App Studio Abstraction: Teams and Team Members

App Studio simplifies this enterprise hierarchy:

• A Team maps directly to a Work Group and its associated Work Queue.
• A Team Member maps to an Operator ID associated with that Work Group.

---

4. Get Next Work (GNW) Logic & Skill-Based Matching

Get Next Work is Pega's automated pull engine. When an operator clicks Get Next Work in their user portal, the system does not pick assignments randomly. It applies a rigorous multi-tier filtering algorithm:

$\text{Candidate Assignments} = \text{Operator Worklist} \cup \bigcup \text{Authorized Work Queues}$

GNW Selection Sequence

1. Worklist vs. Work Queue Preference: The operator's record specifies whether to check the user's personal worklist first or search team work queues first.
2. Urgency Ordering: Eligible assignments are sorted by assignment urgency (.pyUrgencyAssignWork) in descending order (highest urgency first).
3. Skill-Based Verification (Rule-Admin-Skill):
   • An assignment can require specific skills with minimum competency ratings (range 1 to 100). For example: Spanish >= 75 and UnderwritingLevel >= 3.
   • GNW inspects the operator's skill profile. If the operator's rating is lower than the assignment's required threshold, that assignment is skipped.
4. FIFO Tie-Breaking: If multiple candidate assignments have identical urgency and the operator meets all skill thresholds, GNW selects the oldest assignment based on creation timestamp (.pxCreateDateTime).

---

5. Dynamic Routing with Business Logic

Real-world workflows rarely route to a static queue. Pega enables Dynamic Routing by coupling assignment steps to Decision Tables (Rule-Declare-DecisionTable).

Scenario: Loan Application Underwriting Routing

Consider an enterprise banking application where loan routing depends on the requested amount and the property jurisdiction:

In App Studio, this is configured simply by selecting Route to: Use business logic, choosing the condition properties, and mapping outputs to teams. In Dev Studio, the underlying assignment shape references the router activity ToDecisionTable.

---

6. Architectural Anti-Patterns and Exam Traps