Discussion
TCS
SE
Last activity: 6 Apr 2018 19:26 EDT
Equivalent of CPM-UI ruleset in PegaCS7.1.4?
Hi,
What is the equivalent CPM-UI ruleset found in on CMP 6.2 in PegaCS 7.1.4? Is this ruleset removed in PegaCS 7.1.4?
Regards,
Naveen
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
TCS
SE
I just read below from upgrade guide
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?
Pegasystems Inc.
IN
In new CPM 7.1.4 or call it as PCS, you have to update your CPM CSR portals to CPM interaction portal. Please follow the below link for same.
https://docs-previous.pega.com/converting-cpm-csr-portal-cpm-interaction-portal
TCS
SE
Hi Chetan,
Thanks for your quick response.
From the academy, I read below:
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.
Regards,
Naveen
TCS
SE
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.
Accenture Technology Services
IN
Naveen , Curious about your last point "If we move to interaction portal, our earlier interactions cant be worked upon and we have thousands of interactions open any day in production." .
What did you do to resolve the above problem ?
TCS
SE
Hi,
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."
https://docs-previous.pega.com/converting-cpm-csr-portal-cpm-interaction-portal
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.
Regards,
Naveen Ravindra