Posted: 4 Dec 2019 1:31 EST Last activity: 4 Dec 2019 6:43 EST
Ruleset version management
Hi, for my application i have exhausted one major version. Can i directly move to next major version without skimming. Or skimming is necessary before moving to next major version. Does the rule resolution does not look in lower major version if the rule is not found.
e.g. I have exhausted one major version , i.e. 01-01-01 to 01-99-99. For next release can i directly start code in 02-01-01 and rule resolution will pick rules accordingly wherever it is present 02 or 01 major version. Or rule resolution will not look below 02 major version and we would necessary need to do skimming to bring all rules on 02.
In general, we would not be able to add two XYZ:01-xx and XYZ:02-xx ruleset versions in the application record. So if we move to next major version (for example from XYZ:01-xx to XYZ:02-xx) without doing a skimming, you would be able to mention only one major version in application record. If you have mentioned 02-xx in the application, by rule resolution lower major version would not be taken into consideration. The attached document will help you get a better idea of how rule resolution works considering major version. So in our case rule resolution algorithm will not be able to pick any rules from 01-xx version. This is the reason it is always recommended to do a skimming to next major version.
The below link will give other details about skimming.
Generally, it's a safe operation and not very time consuming.
Anyway, in case of oooold legacy system, I can imagine that something may go wrong with skimmed ruleset. So you can try to skim it and if you observe that the application is not working as expected, then just create another ruleset for your development and keep your old one (01-99-99) right below new RS.