Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Upgrade from PRPC v.6.1 SP2 to v.7

SA-1004

Summary



Questions pertaining to a planned PRPC v6.1 SP2 to v7.1.6 upgrade:-

1. How do we upgrade our platform? From v6.1 SP2 to v6.3 and then to v7? Alternatively, is there a guide how to upgrade from 6.1 SP2 to v7 directly? If there is no way to upgrade directly, do we need to fix everything twice - after moving to v6.3 and then after moving to v7?

Please provide us links to the most appropriate upgrade guides for our situation.

2. How do we know which part of system will break after upgrade? We have a lot of customized rules to deliver bespoke solutions. The project is not small so it's hard to find problems pre-emptively.

Could you please provide a small guide to things that may possibly break after upgrade?

3. Due to point 2 it is difficult to estimate amount of work we'll need to do to make application work after the upgrade, but we have to tell our estimates to our customer in order to start working on it.

Can you please provide any help with this too?



Resolution



For this type of project evaluation, please contact your Pega Account Executive and/or Practice Lead, who will be happy to assist you further, possibly under the remit of a consulting engagement.

Product documentation covering various upgrade and deployment scenarios can be found on our PDN site:-

https://pdn.pega.com/resources/deployment-guides

Published June 12, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us