William Baeyens (baeyw)
Sr. System Architect - Pega Consulting
Pegasystems Inc.
baeyw Member since 2019 8 posts
Posted: April 26, 2021
Last activity: May 4, 2021
Posted: 26 Apr 2021 3:29 EDT
Last activity: 4 May 2021 2:22 EDT

LSA Course : Class Group design


I've been wondering what are the real impacts of separating case types into different class groups. This is not really discussed in the LSA course but I feel it's a very important design choice as it has a strong impact on long-term application maintenance. 

I've encountered some LSA that have a habit of creating a new class group for each case type (And I found that it has some advantage, for archival for example). But I've also seen a project where even 2 separate applications were sharing the same Table for all their case types. 

So what exactly are the cons of having separate workgroups for each case type?

I suppose it has impacts on reporting but what exactly are those impacts?

Does the "report on descendant property" doesn't work anymore? Or Is it only a question of performance because several tables are queried?

Do the "standard" reports that are found in the case manager keep on working? 

Any insights on what kind of problems have been encountered when having multiple class groups would be greatly appreciated ;). 

Kind regards. 



Pega Platform 8.5.3 Senior System Architect Pega Academy