Pega - Case Management Interview Q&A

Explain about Work Object?

A work object is the primary unit of work completion in an application, and the primary collection of data that a flow operates.

As an application is used work objects are created, updated, and eventually closed (resolved).

Every work object has a unique ID (property pyID), an urgency value, and a status (property pyStatusWork).

 Explain about Work Object ID?

A work object ID is the permanent, external identifier of a work object.

If we do not specify a prefix (on the Details tab of the application rule), the Work-.GenerateID activity uses W- as the prefix and no suffix. The Work-Cover-.GenerateID activity uses C- as the default prefix. Conventionally, the F- prefix is used to identify folder work objects.

 Where we determine the prefix and suffix of the Work Object ID?

The prefix and suffix are determined by a model rule pyDefault for the work type or the class corresponding to the class group. The model is referenced on the Process tab of the flow rule that creates the work object.

Cover:

Explain about Cover?

A cover is a work object in a concrete class derived from the Work-Cover- abstract class

A cover work the object is a parent to one or a few other related work objects.

Typically, one work party such as the customer party is present in the cover work object and present in all the covered work objects associated with it. The covered work objects are the children in a parent-child relationship.

A cover work object provides coordinate processing of related work objects. By default, the system prevents the resolution of a cover work object unless all of its “member” covered work objects are resolved.

 How do we create the Cover Work Object from Activity?

In the activity, we are creating Work Object and Add to the Cover at a time by using the method AddCoveredWork.

AddCoveredWork Creates a new covered work object using the primary page data.  This activity assumes the cover is already locked. Due to the above, Reason, we have locked the cover by using Activity Obj-Refresh-And-Lock.

This activity saves the newly covered work object on the deferred list.

 How the Cover Work Objects are working?

For example, if a single customer request causes a user to create three separate work objects, these work objects may follow separate flows, be handled by separate departments, and not otherwise affect each other. The cover object provides a way to consolidate, view, and manage the outstanding service requests of this customer. After all, three covered work objects become resolved; the cover work object can be resolved.

How the Covers saw by application users?

Work object forms support working with covers and it's covered objects:

·         Click the View Contents button () at the top right of the cover work object form to access the member work objects.

·         From the ALL tab, select any single cover member work object using the drop-down list or click a row.

·         Click the yellow cover ID link to return to the cover-only display.

 By convention, the work object IDs of covers have the format C-999999; basic work objects have the format W-99999.

 Folders:

Explain about Folder?

A work object folder is a work object in a concrete class that inherits from the Work-Folder- class.

A folder object holds a collection of one or more other work objects (which themselves may be basic work objects, other folders, or covers) providing access for analysis and reporting.

By convention, the work object ID of folders has the format F-12459

 How do we create a Folder by using Activity?

AddToFolder Activity Adds a work item to the folder.

This activity creates a link between work item and folder and adds appropriate status messages.

 What is the difference between a Cover and a Folder? Which one is tightly coupled?

A cover is a work object that is also a parent to one or a few other related work objects. Internally, a cover is a work object in a concrete class derived from the Work-Cover- abstract class. A cover work object provides a means to coordinate the processing of the related work objects. Normally, the system resolves a cover work object once all its “member” covered work objects are resolved.

A folder is a work object in a concrete class that inherits from the Work-Folder- class. A folder object holds a collection of one or more other work objects (which themselves may be basic work objects, other folders, or covers) providing access for analysis and reporting, but not for primary processing.

The cover is tightly coupled because a Work object can be associated with many folders but it can be associated with only one cover.