Major version ruleset deleting – Measuring Benefits
From past 4 years we developed code in major version 01-XX-XX, as part of upgrade to Pega7 we skimmed rulesets to 02-01-01. When we calculated rules count, we have 36k rules in 01- major version and 28k rules in 02- major version.
I remember Pega recommends deleting previous major version, because we may never use that. Now to propose this rule maintenance activity to clients, I have to document benefits of doing this and is there a way to measure the benefit by implementing this in sandbox ? can some how clarify what excet benifits we will have and how to measre that either in terms of cpu use, cache use, memory use or so on....
***Updated by Moderator: Marissa to update categories***
During my research i found some of the recurring skimming questions are as follows: 1. What are the benefits of skimming?, eg, better performance, ruleset version maintenance, quicker deployments due to smaller packages, etc
2. What are some of the drawbacks of skimming? eg. rules history, regression testing, etc
3. What are the risks of not doing a skim? eg, overhead of ruleset version management, etc
4. What is the best practice when to do a skim? eg, before new development starts, deploying a skimmed version etc
5. What is your experience with skimming? eg, performance and accuracy of skimming tool, hotfixes applied, extend of regression testing.
Hope it might be helpful in preparation of your document.