Kaushik Dutta:
The application is build on Pega customer service 8.7.1
Client is not using the interaction case type therefore they do not want those interaction cases to be stored in Pega DB. _(First Problem Statement)
Also they want Pega customer service framework application to be removed from their application._ (Second Problem Statement)
First Problem statement we resolved it by activating the temporary object checkbox in the starter flow of interaction case type. Could be a quick fix but while doing the analysis found out many new things about Temporary workobject creation in pega.
In Pega 23, whenever we create a case type, Pega automatically generates an Initialisation Stage, under advance tab Temporary case creation checkbox section will be active and we can configure.
When we remove the Initialisation Stage, from case type Temporary checkbox section from cases type will disappear because under pega Ruleform section rule there is a visiblity condition defined by Pega. (Use Live UI to open the section)
In Pega CS 8.7.1 Initialisation stage was not there so that section was hidden in the Case type rule pyDefault. There we have to configure the Temporary Object checkbox from the starter flow itself to achieve this requirement.
Now the second Problem statement. Need some insight how we can approach for removing the Pega CS from the whole application, as there are many final rules, many extented rules which were customised
In my opinion, completely removing Pega CS from an existing application is quite risky, especially since there are many final and extended rules involved. It can break rule resolution and core functionality.
What I’d suggest is:
Gradually decouple your implementation from CS (stop using CS-specific features like Interaction, CPM flows, etc.)
Move your logic to a custom layer on top of Pega Platform
Over time, reduce dependency instead of trying to remove CS directly