Having gone thru SAE I and II training, the discussions were all around Case Management, Case objects, etc. Now that I am working with a vendor on implementing some Pega applications, they are using "work objects" - which were not discussed in our training.
I have searched PDN but have not found a good comparison of "Case" vs. "Work Object". Can anyone here give a brief overview, and when you want to use one versus the other? Or are they the same thing?
***Updated by moderator: Lochan to add Categories***
***Updated by moderator: Marissa to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
My understanding (and I look forward to hearing a more official answer from someone on the "case management" team) is that in general a "case" could be a group of work objects, but if it is only one work object, then "case" and "work object" are the same thing.
A slightly more complicated example would be when a "case" involves a cover object and one covered object within that cover. In that situation (I almost said "in that case" but realized that would be confusing), the "case" involves two work objects, the cover and the covered object.
Some of the available rule types such as "Case Type" allow automatic generation of subcases, which are actually just work objects. To read more about all this, go to app explorer, right-click one of your work classes, and start creating a rule of type "process - > case type" and when you get to the rule form choose "actions - > get help". /Eric
Instead of talking in vague definitions, how about I give you an example for context?
Imagine I am implementing an application for event planning at a large venue. I want to track all the work associated with the booking and execution of a single event, like a concert: such as giving a quote for the event, booking it, arranging for shuttles to the parking lots, and seating arrangements.
The event is the case and, based on how I implement it, the specific tasks I gave as examples would be the work items. They would have their own flows and data structures necessary to complete each task. But, since they are part of the case, that data can be propagated in order to give a comprehensive view of what has been performed for the event.