A class group is an instance of the Data-Admin-DB-Class Group class.

A class group instance causes the system to store the instances corresponding to two or more
concrete classes that share a common key format in a single database table. The name of the
class group is a prefix of the names of the member classes.
Class groups are commonly used to cause the system to store instances of similar or related
work item concrete classes together in one relational database table. This is known as a work
pool. Work pools are referenced in access group instances.
Class groups correspond to tables in the PegaRULES database, not tables for external classes.
Each external class has a corresponding unique database table instance (Data-Admin-DB-Table
class) and so cannot be part of a class group.
The work pool for a user is the set of all the work items (open and resolved) of all the Workclasses that a user can enter (in one application).
The system determines which work types (which classes derived from the Work- base class) a
user can enter from a list of class groups. These class groups are specified in an access group
associated with that user.
A single user can create work items that belong to different class groups. For example, suppose
three applications are defined by RuleSets Alpha, Beta, and Gamma. Assume that each
application has one class of work items, with the class names Work-Alpha, Work-Beta, and
Work-Gamma, and that one class group is defined for each application.
Tom's access group can let Tom be a user of only the Alpha application. Tom can create, review,
and update only Alpha work items.
User Mary is a user of both Beta and Gamma applications and so can create, review, and update
both Beta and Gamma work items. User Fred can access all three applications.
The selected work pools also affect the operations of the Application Explorer and the scope of
reports in the Monitor Activity workspace.
On the Requestor page of the clipboard, the property pxRequestor.pxCurrentWorkPool holds the
value of a user's current work pool.
A workbasket is a named queue of open assignments that are not associated with an operator. A
workbasket is defined by an instance of the Data-Admin-WorkBasket class.
A workbasket can be linked to an organization unit, a work group, and a calendar.

To view the workbaskets referenced in your current application, select

> Process and Rules
> Work Management > Workbaskets. To view all workbaskets in the system, use the Application
Explorer or

> Org & Security > Tools > Workbaskets.

During system installation, one workbasket named default@pega.com is created, as a last resort
for routing of assignments.
As work items progress through a flow execution, the system creates an assignments.
Assignments may be associated either with human users (and appear on their worklists) or with
a workbasket. The "contents" of a workbasket is a set of assignments awaiting processing,
ordered in decreasing urgency, similar to the contents of a worklist. These assignments are
sometimes known as the work queue.
Assignments leave a workbasket in three ways:
Users who are qualified can remove an assignment from the workbasket to process the
assignment.
An application can automatically route assignments in a workbasket to users based on work
schedules, due dates, skills, workloads, and other factors.
Managers can transfer assignments from a workbasket to user worklists.
During execution of a flow, a router shape can choose which workbasket is most appropriate to
receive a newly created assignment.
The Data-Assignment-WBSummary class, mapped to a view in the PegaRULES database,
supports reporting on assignments in workbaskets. Standard reports for assignments in
workbaskets appear in the Monitor Assignments area of the Monitor Activity workspace.
A worklist is a list of open, outstanding (not complete) assignments ready and waiting for a user
to perform them. Thus, a worklist display shows selected instances of the Assign-Worklist class.
Worklist displays usually include a column that identifies a work item ID, but a worklist is not
a list of work items. At any point in time, one work item may have two or more open
assignments. These assignments may all appear on one user's worklist, or on the worklist of
various users.
Usually, assignments appear on a worklist because an Assignment shape in a flow created the
assignment. Assignments appear in order of assignment urgency the most urgent assignments
appear first, those with the highest pxAssignUrgency value. (When normally computed by a

Declare Expression rule, the assignment urgency value Assign-.pxAssignUrgency is linked to

but not always the same as the overall work item urgency Work-.pxUrgencyWork.)
Other columns of the worklist often identify the work item ID, work item status, and
instructions.
Information on the worklist display may become stale (outdated) if the user is inactive or works
only in a workspace other than the Process Work workspace. Click the refresh icon (
or interact with the worklist to refresh its contents.

or

Worklist displays on the Case Manager portal

From the My Dashboard tab on the Case Manager portal, you can view a worklist (Urgent
Work) of open assignments for yourself, for anyone else in your work group, or for workbaskets
in your work group. The items on the list represent the 25 case assignments that have the highest
urgency values.

A red urgency clock

in the row header indicates that the item has an urgency value equal to or

greater than 60. A yellow urgency clock indicates an urgency from 30 to 60. The rest are
indicated by a green urgency clock . Remaining assignment goal and deadline intervals appear
in plain text if neither time has been exceeded. A goal time that has been exceeded displays the
elapsed interval in red and the remaining deadline interval in yellow. A deadline time that has
been exceeded displays the elapsed interval in red. See Case Manager portal Using the My
Dashboard tab
Worklist displays on the User and Manager portals
In the composite User and Manager portals, the worklist appears in the Process Work
workspace.
Worklist displays on the WorkUser and WorkManager portals
A worklist appears in the

workspace. The worklist appears in the My Work In

Progress area of this workspace. Details of its appearance vary.

A yellow clock icon (

) next to a row indicates that the goal time for this assignment is less

than 24 hours into the future. A red clock icon ( ) indicates that the deadline time for this
assignment is less than an hour in the future or has occurred. When the deadline occurs but the

assignment remains open (not performed) the assignment is untimely. The standard control rule
TimeLimitUrgency determines the schedule and appearance of the yellow and red clock icons.
Your application can override this rule.
The Where-am-I? icon ( ) links to the diagram representation of the flow rule.
A work group is an instance of the Data-Admin-WorkGroup class. A work group can identify a
user who is a supervisor, and a set of workers and workbaskets that report to that supervisor.
For the supervisor of a work group, the My Group area of the Process Work space provides
quick access to the worklists and workbaskets associated with the group. Work groups are a
primary unit of summarization in standard management reports on the Monitor Activity
workspace.
An Operator ID data instance (Data-Admin-Operator-ID class) usually identifies a work group
to which a user belongs. If left blank, that operator can enter work items but not access a
worklist or workbaskets.
Work group information is not related to the three-level organizational hierarchy consisting of
unit, division, and organization. Work group membership does not affect a user's RuleSet list.