Question
Citigroup technology inc
US
Last activity: 6 Apr 2018 19:26 EDT
Clarification before doing 7.1.8 to 7.2.2
Currently we are in 7.1.8 version we are planning to update to 7.2.X version.
Below is the path of updating each of our env
Dev7(POC Env)--> Dev2(Actual DEV)-->SIT->UAT-->Stress-->Prod
We are trying to think about the possible scenario's, which would occur while we update each env from 7.1.8 to 7.2.X during our Project release.
When we implement the code developed in 7.1.8 to env which is in 7.2.X? will that have any impact, as we see some of the OTB table scehma updates was introduced as part of new version 7.2.X.
Until April Our prod env will be in 7.1.8, we are targetting to do a update of prod by mid of april. Suppose if we do any emer fixes in 7.2.2 and implement in prod which is in 7.1.8, what would be the causes, will all the functionality work as expected.
***Moderator Edit : Vidyaranjan | Updated Categories / Tagged SRexists***
***Updated by Moderator: Marissa to move from Product Support Community to Pega 7 Upgrade Center***
**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.
US
Greetings,
1. "When we implement the code developed in 7.1.8 to env which is in 7.2.X? will that have any impact, as we see some of the OTB table scehma updates was introduced as part of new version 7.2.X."
I am assuming you mean your application rules here, if that is the case there is no impact. The rules and data will be migrated and exisiting applications updated during the upgrade process.
2. "Until April Our prod env will be in 7.1.8, we are targetting to do a update of prod by mid of april. Suppose if we do any emer fixes in 7.2.2 and implement in prod which is in 7.1.8, what would be the causes, will all the functionality work as expected."
I am not very clear about your second question/concern above. Do you mind clarifying in detail. If I assume you are talking about making application rule changes in your lower environment (which is 7.2.x) and promoting the RAP to production which is still in v7.1.8, then this is not a good idea. Any application changes that you make in lower environment has dependencies with a higher version of Pega ruleset versions and its very likely that these code changes will fail in a lower stack (v7.1.8) when imported.