Managing emergency fix
In our client, they use same QA & STG envs to test both weekly maintenance code and ECR code (emergency change request; SEV1, same day fix & deployment). Since they both use same envs, this sometimes create conflicts in code - e.g. ECR testing sometimes contains weekly maintenance code, which is not deployed to PROD until later.
Client has been asking to create a separate application to test for ECR code only, but we couldn't quite figure it out when both weekly maintenance and ECR codes are using same envs.. Any insight is appreciated.
***Edited by Moderator Marije to add Capability tags***
DXC
AU
@Will Cho Create multiple application so that you can hold the ruleset version based on the application type if you are still going to use single environment, that will be the right option to use.
In the Application rule set the ruleset version to that patch version present so that new rules are not picked even if they are in database.
Pegasystems Inc.
IN
@Will Cho You can create multiple applications and use them if same environment is used for both testing and development. Say for e.g Create ApplicationName, ApplicationNameStg, ApplicationNameDev. ApplicationNameDev and ApplicationNameStg will only have dummy rulesets which will not be moved to prod. ApplicationNameDev will be built on ApplicationNameStg and ApplicationNameStg will be built on ApplicationName, ApplicationName will have all the original prod rulesets. You can use branches for temporary development test it and merge to the original rulesets. Create different AGs (Separate for Development, testing and the ECR) and point it to the respective applications this way it will not create any conflict.