Import Certain Ruleset Version to Production Environment (skip some previous ruleset version)
I have 2 PEGA Environment :
1. Development Environment, already have ruleset A : version 01-01-01 to 01-01-18
2. Production Environment, already have ruleset A : version 01-01-01 to 01-01-09
I get urgent requirement which I must import ruleset A : version 01-01-16 only from Development Environment to Production Environment. But in the next time I will to import ruleset A : version 01-01-10 to 01-01-15 and 01-01-17 to 01-01-18 to Production Environment.
Is safe to do that requirement?
Thanks for all advice.
Regards,
Maulana
Accepted Solution
Pegasystems Inc.
US
I think it is risky. You would need to test thoroughly in another environment to be sure you do not have any dependencies.
Pegasystems Inc.
US
I think you could potentially encounter scenarios where a certain rule does not exist in the Production environment. What if you had a rule in version 01-01-16 that referenced another rule but that rule was in 01-01-15?
Sinarmas MSIG Life
ID
Hi CarissaW_GCS,
Thanks for your answers.
So if ruleset A version 01-01-16 is clear (not referenced to version 01-01-10 to 01-01-15), this requirement is permissible?
Accepted Solution
Pegasystems Inc.
US
I think it is risky. You would need to test thoroughly in another environment to be sure you do not have any dependencies.
Sinarmas MSIG Life
ID
Anamata
NL
Suggestion:
Create ruleset B (01-01-01), copy the rules from ruleset A (01-01-16) to ruleset B, package it, deploy it to your production environment and add it to your application rulestack in production. At any moment you can remove it from your application rulestack.
Sinarmas MSIG Life
ID