We are currently at PRPC 6.2 SP2 and planning to upgrade to PRPC 7.1.8. Due to scheduling and infrastructure compliance constraint, we can only do tolerance upgrade in production now. We will do compliance upgrade later when we have time to do that. We will also be building new rules in Pega 7 environment to fulfill business requirement that will exist with other older rules. I am trying to understand that if we just do the tolerance upgrade now and do the compliance upgrade later will it cause any issues in production and development.
**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.
In above case mentioned, let us say we just want to be compatible with IE11 fixed resolution (don't need responsiveness initially) what are rule types, changes we have to do over Tolerance upgrade to ensure we don't run into issues.(Tolerance to Compliance Lite)
Dhev has already given answered. In my view to reduce the upgrade cost, you can choose iterative option. You can think of minimum scope of compliance level1 and then can add more iteration. Example initial scope traditional/fix portal, making html5 to application.
yes, you need to at least do a Compliance level-1 upgrade. It is basically all of upgrade steps for tolerance plus html5 compliance. Later, you can go for level-2 which is nothing but making changes to achieve responsive UI.
Certainly tolerance upgrade is not an option for Production in general but you can still do some POC analysis and identify how much of your application if (tolerance upgraded) can work on IE-11/IE-10 (as required) , this will give you clear idea on effort and feasibility for tolerance upgrade .If all portals are composite and minimal non -auto generated controls are used in application , the tolerance upgrade might work on IE 10 by setting up IE emulation for each portal harness.