CPM-UI Rules Merged into PegaAppCA Rules previously contained in the CPM-UI RuleSet have been merged into the PegaAppCA RuleSet, in CPM7.1 release, eliminating duplication of rules to help simplify implementations and upgrades. If your implementation rulesets has CPM-UI as pre-requisite, replace it with PegaAppCA.
However, I do not see CPM-Portal class that the CPM CSR and CPM Manager portal applies to exists in PegaAppCA. Could you confirm if the class CPM-Portal has been removed?
The legacy CPM end user portals (CPMCSR_Portal, CPMSalesRep_Portal, CPMSalesManager_Portal) have been deprecated. They will continue to function in this release, but may be de-supported in a future release of CPM. Pega recommends that you use the Interaction and Account Manager Portals going forward.
Therefore, CPMCSR_Portal is deprecated but not de-supported. Hence, can you let me know if this class is really removed. Do you find this class in a fresh installation of PCS 7.1.4 at your end?
If we move to interaction portal, our earlier interactions cant be worked upon and we have thousands of interactions open any day in production.
When importing PegaCS jar, there is a step where it shows pre-existing rule conflicts. It displays the rules that are present in other rulesets and the recommendation it provides is to refactor existing application or repackage the bundle without affected rules.
At that time we were not aware that CPM-UI rules are moved to PegaAPPCA and hence we did not import conflicting rules. We now re-imported only conflicting rules in other ruleset and we are able to see CPM-Portal class.
When you look at below link, there is a warning which states:
"Existing interactions are not backward compatible. An Interaction created in previous versions of CPM cannot be processed after upgrading to CPM 7, but it can be opened in review mode. However, all service items are backward compatible."
We are currently working with ECS team and will post response. At this stage we cant wrap up all interactions in a weekend when we golive and looking for workaround from Pega where both Interactions can co-exist.