Question

1
Replies
271
Views
Dineshsb1 Member since 2013 25 posts
JP Morgan Chase
Posted: March 26, 2019
Last activity: June 18, 2019
Closed

Case Type Creation in Customer Service for Comms

All,

Pega Platform :- 8.x / Customer Service for Comm's

We are building our application on top of Pega Customer Service for Comms framework . One thing we observed was that Pega has 2 class groups PegaComm-FW-CF-Work (for Comms Case Types ) & PegaComm-FW-CPMCFW-Work (For Customer Service cases ) . For each case type in Comms class group Pega has a wrapper case type created in the "PegaComm-FW-CPMCFW-Work" class group with a direct inheritance to Comm's class .For example consider the “AddNewService” case type . I believe the reason for this is there are lot of customer service artifacts which needs to be leveraged when we open these case within an interaction portal .

Question :- When we create a new application and select some OOTB Case type like “AddNewService” , “ChangeService” etc we see that Pega creates 2 class groups one extending the Comms class group and second extending Customer Service class group .In addition it also creates “AddNewService”,”ChangeService” in the newly created class group for Comms but IT DOESN’T CREATE WRAPPER case types in the newly created class group for Customer Service. This is different than the behavior we have currently within the Comms framework .Also we dont see the wrappers created for other case types like "ActivateDevice" etc .

So what is the best practice for Case Types .We would want to follow what we have in product and create wrapper case types in "Customer Service class group" .Appreciate your responses.

Thanks

Dinesh

***Edited by Moderator Marissa to update SR Details***

Pega Customer Service Case Management SR Exists
Moderation Team has archived post
Share this page LinkedIn