Architectural design for PRPC731 (CRM731 framework) Upgrade.
We are planning to upgrade from PRPC718 to PRPC731 version.As part of this upgrade,we are planning to do an incremental roll out (no outage allowed) of all end users to PRPC731 version (by maintaining two parallel production environment URL's - Different rules schemas and same data schema).
Please rectify and suggest any alternate architectural design.
Below are challenges/recommendation I can think of
• Use cases related to SLA/Email listener/Agents are to be tested thoroughly in both Pega 7.1.8 and Pega 7.31. It’s recommended not to change the existing settings and these agents might have to be configured to run either in 718 or 7.31 rather than in both the environments.
• No new features should rollout during the pilot period when both versions are in Production.
• It’s recommended to minimize the co-existence of pilot period to be lesser, due to any feature rollout or to apply any of the hotfix which needs detailed verification
• Having Pega 718 and Pega 731 run in-parallel sharing the same Business Data or Data schema is never a recommended approach, nor a tested and verified approach by Pega . We always recommend to stay away from that approach as you might have data loss / corruption.
This approach needs to be tested thoroughly before choosing