Hi @Vigneshk2107,

Pega maintains two separate tables: Assign-Worklist (WorkList) and Assign-Workbasket (WorkBasket) instead of a single table to support the platform's design principles, performance, and flexibility. Below are the key reasons:

 1. Separation of Assignment Types

• WorkList: Assignments assigned to individual operators (users).
• WorkBasket: Assignments assigned to a group or team (work queue).

Keeping them separate simplifies access and routing logic depending on the assignment type.

 2. Performance Optimization

• When retrieving assignments for a user or work queue, Pega can query smaller, more targeted tables, which improves performance, especially in large-scale applications.

 3. Routing and Assignment Logic

• System processes like Get Next Work treat worklist and workbasket assignments differently.
• Separate tables allow more efficient and specific routing logic to be implemented.

4. Security and Access Control

• WorkLists require user-specific access, while WorkBaskets follow queue-based roles/skills.
• Separation simplifies enforcing access policies and authorization.

 5. Ease of Reporting and Auditing

• Since they serve different business purposes, reporting is clearer and more manageable when assignments are stored separately.
• You can easily track user workload vs team queues.

 6. Scalability and Maintainability

• Supports modular and scalable architecture by logically separating concerns.
• Reduces complexity when handling escalations, SLA monitoring, and reassignment.