Question6Replies1110Views AshwinK999 Member since 2012 3 posts Stratosphere Consulting Posted: 5 years agoLast activity: 5 years ago Closed Create/Delete/Update a Ruleset Version takes time as their are 1100 different rule set versions available to render in RuleSet Rule FormCreate/Delete/Update a Ruleset Version takes time as their are 1100 different rule set versions available to render in RuleSet Rule Form.Is there an alternate way to let the system load only major versions specified.Example: My application contains Major Versions 01, 02, 03, 05 and 15. Can we specify preferences to load only major version - 15 as most of the time we want to focus on 15-01-XX till 15-99-99. System Administration ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 5 years agosahup1 PEGA replied to AshwinK999Hi Ashwin, Good Morning!Could you kindly comment on the need to have all lower versions when the application rule is pointed to major version 15-XX-XX https://pdn.pega.com/reuse-and-version-management/about-ruleset-versionstrue, having 1100 ruleset versions would run into slowness issues as you mention.Please share your comments/thoughts, Thank you!psahukaru Posted: 5 years agosahup1 PEGA replied to sahup1>>> below copied text is from PDN link: https://pdn.pega.com/reuse-and-version-management/about-ruleset-versionsrule resolution does not look for rules across multiple major version numbers Posted: 5 years agoAshwinK999 Stratosphere Consulting replied to sahup1Sure - I get that but we are looking for options to see if we can avoid other major versions in loading while opening a rule set form to bring more productivity in creating/updating/deleting rule set versions from the rule set form. Posted: 5 years agoAmitShekhar replied to AshwinK999What is the need to keep the older RSVs on the system when it’s not needed and is definitely not picked by rule resolution used.If it’s needed for security/audit purpose then I will suggest taking a backup of older version and keeping them on file system rather than keeping them in Pega DB.This should be part of archival strategy of the application Posted: 5 years agoAshwinK999 Stratosphere Consulting replied to AmitShekharI tried searching for any documentation pertaining to above response and I do not find any. I am comfortable in deleting all the prior rule set versions manually. Posted: 5 years agosahup1 PEGA replied to AshwinK999if we know the ruleset lock/unlock password - we could use delete a ruleset wizard (designerStudio --> System --> Refactor --> Rulesets) as the ruleset version should be in unlocked state.