Question
Pegasystems Inc.
AU
Last activity: 16 Oct 2018 12:03 EDT
Sizing for Update from Pega 7.1.5 to Pega 2.2.2
My customer is planning on an update from Pega 7.1.5 to Pega 2.2.2, and would like to do an effort sizing.
1. What is the process to size the effort required for a Pega 7 update?
2. Is there any tools or sizing sheet that can be used for Pega 7 update?
3. Is it required to run a full application regression test after the update to make sure the update is successful?
Thanks in advance for your help.
**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
Is your application first built on Pega 7.1.5 or did you upgrade it from previous versions(Pega 6.x)).
The following estimator tool will help you identify any custom code in Pega 7.1.5 which may likely to break in Pega 7.2.2.
https://pdn.pega.com/exchange/components/upgrade-estimator-tool
There is no OOTB update sizing sheet is available.
Pegasystems Inc.
AU
Thanks for your reply. The application was first built on Pega 6 and then upgraded to Pega 7.1.5. However, since this application has been deployed across 17 line of businesses and multiple countries, the customer would like to do a deep-dive pre-upgrade assessment on the impacts on the UI, data, process. Also want to know if a full regression test is required after the update?
Appreciate if you can shed some light on this.
Pegasystems Inc.
IN
In Pega 7.1.7 onwards Pega 7 Platform is full HTML5 compliant.
As you have upgraded the application from Pega 6 to Pega 7.1.5 you may have some level of custom or deprecated code.
I strongly recommend to run the upgrade estimator tool to identify the custom and non HTML5 standard rules.
https://pdn.pega.com/exchange/components/upgrade-estimator-tool
If your application has considerable amount of custom or deprecated code then you have do full regression.