Move Classes to Latest Major Version post Skimming
Hi Team,
We have skimmed our rulesets form 01-xx-xx major version to 02-01-01 version. Have a query regarding classes present in 01 version .
Is it required to repoint all the classes from 01 version to 02 version as this will be a manual task. Do we have some wizard to do the same if this task is mandatory?
Accepted Solution
Updated: 7 Jul 2022 6:13 EDT
IQZ Systems
US
@ShwetaB96 Again, as Created in version field is not used for rule resolution, Your class will be visible to all rules in ruleset version 01-ab-cd & no issues with rule resolution/execution.
IQZ Systems
US
@ShwetaB96 Classes are non versioned rules & its fine if you don't update 'Created in version' in them as its not used in rule resolution.
How ever you may need to update ruleset version in Created version field later when updating the class definition (when current ruleset version value if not available in that system - for eg. you set up new dev server using the skimmed application bundle)
Infosys
IN
Thanks for your reply.
Just want to understand one more point. We have skimmed 01 version to 02 and done some development in 02 and created classes with pointing to 02 version .
But as part of rollback plan for this release if there are many issues as part of Skimming we will go back to some version of 01 and copy all the code that we have developed in 02 to 01 .
So we will repoint our application to 01 and not move the code from 02 instead move the copied code from 01. But the classes were created in 02 , in this scenario should we point back our classes or this will also work?
Accepted Solution
Updated: 7 Jul 2022 6:13 EDT
IQZ Systems
US
@ShwetaB96 Again, as Created in version field is not used for rule resolution, Your class will be visible to all rules in ruleset version 01-ab-cd & no issues with rule resolution/execution.