Work Types

A work type is any concrete class derived from the Work- base class. For example, the standard
class named PegaSample-Task is a work type, as this class is derived from the Work-Object- class
(which in turn is derived from the Work- base class.)

In most applications, work types derived from Work- Cover- base class are referred to as case
types.

Applications usually involve more than one work type, based on processing characteristics. For
example, the processing of an application for a jumbo mortgage differs from the processing of
conventional mortgages, requiring different steps, different properties, and so on. An application
that is to support both jumbo and conventional mortgages may have many work types; however,
many properties and other rules that apply to both can still be shared.

Users identify a work type as they enter each new work item. The set of all work types available
to them is determined by the class group entries in their access group.

A work type label is derived from the Short Description on the Flow form, for a start flow rule
(with that work type as the Applies To key part). A starter flow rule is one that creates new work
items.

In some applications, the work type assigned to a work item when the work item is first created is
preliminary. The standard flow action Work-.ChangeClass allows a user (with the appropriate
privileges) to reclassify a work item from one work type to another (within the same pool).

Cover
A cover is a work item that is also a parent to one or a few other related work items. Typically
one work party — such as the customer party — is present in the cover work item and also
present in all the covered work items associated with it. The covered work items are the children
in a parent-child relationship.

A cover may also be a parent of other cover objects (and their children). Use a case type rule in
the cover class to define the covered objects for the parent cover.

Internally, a cover is a work item in a concrete class derived from the Work-Cover- abstract class.

Covers and folders are two built-in case management facilities that allow your application to
support collections of work items.

A cover work item provides a means to coordinate processing of the related work items. Normally,
the system resolves a cover work item once all its member covered work items are resolved.

Folder
A work item folder is a work item in a concrete class that inherits from the Work-Folder- class.
A folder object holds a collection of one or more other work items (which themselves may be
basic work items, other folders, or covers) providing access for analysis and reporting. By
convention, the work item ID of folders has the format.

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

 One work item may be associated with multiple folders, but only with one cover.
  Members of a folder can belong to different work types, which need not belong all in a
single work pool.

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

Example
To review or work with a flow rule that creates a folder work item, examine or test the standard
flow rule PegaSample-Folder.NewWork.

As a business example, consider a purchasing application where a basic work item is a line item
on a single purchase order:

 The purchase order corresponds to a cover object. Every line item belongs to one purchase
order.

 Folders organize open purchase order line items by our part number and also by the
vendor's part number. A folder work item (in Work-Folder-OurPartNum work type) may be
associated with several line items, and one line item can simultaneously belong to a Work-
Folder-OurPartNum work item and a Work-Folder-TheirPartNum work item.