Pega Onboarding (CLM/KYC) - unwanted class groups after setup of the new application
I observed, that the New Application wizards creates two extra/unwanted class groups (Grp1, Grp2) for "CLM for FS - Corporate and Investment Banking" strategic application, where …-Grp1-… keeps all the CLM/KYC rules and …-Grp2-… has only duplicate of …-Grp1-Requirement class and it’s empty.
Issue described by me seems to be a known problem of the New Application wizard, when a Pega Strategic Application is built on more than one application, like “CLM for FS - Corporate and Investment Banking” is.
In that situation the New Application wizard adds unwanted work groups to the class structure and there is no option to skip that during application setup, so if customer would like to have a clean class structure (without -Grp1-, -Grp2-) and single class group, then a manual refactoring is required.
When we run DCO, it creates a list of “cloneable case Types of application” . It fetches the parent class of each of the case types in this list (cloneable case Types of application) and adds the corresponding class group of the parent class and shows them in setup of the new application.
In CLM, it is fetching “PegaFS-Work-Requirement” as one of the cloneable case types. The parent class of this case type is “PegaFS-Work” . So, PegaFS-Work class group is fetched and displayed in setup of the new application.
You are free to refactor or delete the classes under Grp2 (the class group related to PegaFS-Work and PegaFS-Work-Requirement).
Thank you for response. I've already implemented refactoring, but it'll be good in a future, if the New Application wizard allows to skip those unwanted class groups during application setup, in the situation when Strategic Application in built on more than one application with class group, as it's adds overhead to the implementation.