Update approaches from Pega 7.1.4 to Pega 7.2
When we are updating from Pega 7 to Pega 7, I understand the below concepts are applicable:
- In-Place vs. Out-of-Place
- Split-Schema (not sure if Single-Schema is possible in Pega 7)
- Enterprise Application Upgrade Approach
However, consider the below environment update:
(Pega 7.1.4 + CPM 7.1.2 + CPMFS 7.1.2) to (Pega 7.2 + CPM 7.1.4 + CPMFS 7.1.4)
There are quite a lot of features introduced / changed from Pega 7.1.4 to Pega 7.2 (Pega 7.1.7 seem to have introduced lot of changes).
Similarly quite a lot of features introduced / changed from CPM 7.1.2 to CPM 7.1.4 (CPM 7.1.3 seems to have introduced new CPM Harnesses, Portals, Interaction flows etc).
Note: Please see the Changes Reference section at the end of this comment, for a high-level list of changes that we might need to consider while updating our environment:
Can you please answer the below question with respect to the above update?
Q1. Are the below concepts applicable for Pega 7 to Pega 7 update? My understanding is that the below concepts are mainly related to Pega 6 to Pega 7 upgrade only.
- Tolerance – Applications and Frameworks work on the Pega7 platform, without taking advantage of any new features or operational architecture
- Compliance – Applications and Frameworks work with the Pega7 Standards Mode Responsive UI and enhanced Pega7 operational features
- Enhancement – Applications and Frameworks work on the new Pega7 architecture and exploit new Pega7 business and operational functionality
Q2. Can we still keep the CPM 7.1.2 harness, portal, interaction flows (CAInteraction etc), instead of porting customizations to new rules (CPMInteraction)?
Q3. If we are using IAC, BIX, can we still do update, but just get the prgateway war file Pega-BIX ruleset jar from upgrade distribution and install, rather than running upgrade as suggested in the update guide?
Changes Reference:
-----------------------------------------------------------------------------------------------------------------------------------
Changes from CPM 7.1.3:
CPM Portals – auto-generated from CPM 7.1.3
CPM Interaction flows – CPMInteraction, CPMInteractionDriver now replace CAInteraction, CAInteractionDriver flows heavily customised in Capita.
CPM Harnesses – all harnesses updated with Pega 7 OOTB features
CACopyParentData – This rule is no longer used to ‘Copy Data from Interaction to Service Items’. Instead use CPMSetDefaults, NewDefaults.
Composite (CUstomer 360) – new CPMCompositeContainer harness introduced
Wrap Up flow – CPMWrarup replaces CAWrapup
Changes from Pega 7.1.7:
Data Tables – now deprecated, leave as-is or replace with new ‘Local Data Sources’. Featuers to check – delegated, Edit in excel, export,
Starting in Pega 7.1.7, the underlying platform for full-text search transitioned from Lucene to Elasticsearch. Rebuild Indices.
Redeploy the applications (prweb.war etc) if you are updating from Pega versions earlier than 7.1.7.
-----------------------------------------------------------------------------------------------------------------------------------
**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.
Pegasystems Inc.
IN
Q1. Are the below concepts applicable for Pega 7 to Pega 7 update? My understanding is that the below concepts are mainly related to Pega 6 to Pega 7 upgrade only.
Q1. Are the below concepts applicable for Pega 7 to Pega 7 update? My understanding is that the below concepts are mainly related to Pega 6 to Pega 7 upgrade only.
- Tolerance – Applications and Frameworks work on the Pega7 platform, without taking advantage of any new features or operational architecture
- Compliance – Applications and Frameworks work with the Pega7 Standards Mode Responsive UI and enhanced Pega7 operational features
- Enhancement – Applications and Frameworks work on the new Pega7 architecture and exploit new Pega7 business and operational functionality
Yes these approaches are only applicable for PRPC 5.x and 6.x to Pega 7 Upgrade
Q2. Can we still keep the CPM 7.1.2 harness, portal, interaction flows (CAInteraction etc), instead of porting customizations to new rules (CPMInteraction)?
Pega always recomend to use the Interaction portal even though old portals are still supported as you wont be able to leverage new features of Customer Service
Refer to the following articles
https://pdn.pega.com/converting-cpm-csr-portal-cpm-interaction-portal
https://docs-previous.pega.com/pega-customer-service-migrating-interaction-portal-tech-note
Q3. If we are using IAC, BIX, can we still do update, but just get the prgateway war file Pega-BIX ruleset jar from upgrade distribution and install, rather than running upgrade as suggested in the update guide?
Yes, you cna perform the update and all the additional components linke BIX, prgateway.war files you need to get it from 7.2 upgrade build.
Pegasystems Inc.
US
You can also find more information about Tolerance upgrades here: Upgrade approaches for upgrading from PRPC to the Pega 7 Platform.
Pegasystems Inc.
IN
Dear carbs,
The link you provided is for upgrading from Pega 5.x / 6.x to Pega 7. My questions were around updating from Pega 7.x to Pega 7.x (ML Update)
Pegasystems Inc.
US
There are quite a lot of features introduced / changed from Pega 7.1.4 to Pega 7.2 (Pega 7.1.7 seem to have introduced lot of changes).
Similarly quite a lot of features introduced / changed from CPM 7.1.2 to CPM 7.1.4 (CPM 7.1.3 seems to have introduced new CPM Harnesses, Portals, Interaction flows etc).
There are quite a lot of features introduced / changed from Pega 7.1.4 to Pega 7.2 (Pega 7.1.7 seem to have introduced lot of changes).
Similarly quite a lot of features introduced / changed from CPM 7.1.2 to CPM 7.1.4 (CPM 7.1.3 seems to have introduced new CPM Harnesses, Portals, Interaction flows etc).
Note: Please see the Changes Reference section at the end of this comment, for a high-level list of changes that we might need to consider while updating our environment:
Can you please answer the below question with respect to the above update?
Q1. Are the below concepts applicable for Pega 7 to Pega 7 update? My understanding is that the below concepts are mainly related to Pega 6 to Pega 7 upgrade only.
- Tolerance – Applications and Frameworks work on the Pega7 platform, without taking advantage of any new features or operational architecture
- Compliance – Applications and Frameworks work with the Pega7 Standards Mode Responsive UI and enhanced Pega7 operational features
- Enhancement – Applications and Frameworks work on the new Pega7 architecture and exploit new Pega7 business and operational functionality
Q2. Can we still keep the CPM 7.1.2 harness, portal, interaction flows (CAInteraction etc), instead of porting customizations to new rules (CPMInteraction)?
Q3. If we are using IAC, BIX, can we still do update, but just get the prgateway war file Pega-BIX ruleset jar from upgrade distribution and install, rather than running upgrade as suggested in the update guide?
Changes Reference:
-----------------------------------------------------------------------------------------------------------------------------------
Changes from CPM 7.1.3:
CPM Portals – auto-generated from CPM 7.1.3
CPM Interaction flows – CPMInteraction, CPMInteractionDriver now replace CAInteraction, CAInteractionDriver flows heavily customised in Capita.
CPM Harnesses – all harnesses updated with Pega 7 OOTB features
CACopyParentData – This rule is no longer used to ‘Copy Data from Interaction to Service Items’. Instead use CPMSetDefaults, NewDefaults.
Composite (CUstomer 360) – new CPMCompositeContainer harness introduced
Wrap Up flow – CPMWrarup replaces CAWrapup
Changes from Pega 7.1.7:
Data Tables – now deprecated, leave as-is or replace with new ‘Local Data Sources’. Featuers to check – delegated, Edit in excel, export,
Starting in Pega 7.1.7, the underlying platform for full-text search transitioned from Lucene to Elasticsearch. Rebuild Indices.
Redeploy the applications (prweb.war etc) if you are updating from Pega versions earlier than 7.17
Cognizant Technolgy Solutions
IN
Hi tallr1,
We are also doing a similar ML Update - from PRPC v 7.1.7 to PRPC v7.2 which might also include CPM update. Can you kindly share the documents you created to list out the plan/steps for your update?
Also, what all are the aspects that we should keep in mind when doing such updates - please share insights from your experience.
Thanks in advance for your kind cooperation.
AB