Posted: 1 Dec 2016 12:23 EST Last activity: 9 Dec 2016 9:51 EST
Deleting older ruleset upon skimming
We did a skimming before 6 months that is skimmed rules in 02 major series to 03-01-01. Now we are planning to delete the older RSVs that are in 02 major.
We have below questions.
1) How do we delete all the ruleset and rsv in 02 major in one shot, instead of giving the rsv and ruleset one by one through delete a rulese in refactor utility in designer studio.
2) Since we will performing this deletion in production, do we have to take an outage of user nodes and perform this in the batch node, or we can perform deletion during any time during the business hours. What would be impact if we perform during business hours? as our application already is operated in skimmed rsv series that is in 03-01-01.
3) What are all the options to perform this deletion activity in shot duration and delete in one shot.
***Moderator Edit: Vidyaranjan| Updated Categories and srexists***
I see that the query you have raised, Using the wizard we can only delete one at a time ruleset/ruleset version, has already been raised as an feedback item FDBK-17303 which is to be considered by our product team and shall be provided as an enhancement in future releases.
While you certainly can determine the tables of interest by monitoring what is being done using tracer when doing a individual ruleset version the recommended way is to use the wizard even if it is more of a lengthy process. I would suspect you could also export the skimmed ruleset as a package then delete the whole ruleset and re-import. If you elected to go that route I would certainly test the sequencing and the behavior in lower environments.
Please note that if you follow the approach suggested by Stilr, then as part of ruleset deletion, system will also delete the non-rule resolved rules (rules with a ruleset but no version - like application, access roles). The application that you will be using to log in and perform the deletion will also get deleted. If you log off post deletion, you wont be able to log in using the same operator. Hence, please make sure that you have operator with accessgroup like PegaRules:Adminsitrators so that you can use it to import your rulesets.
We are not fine with the approach of taking package of skimmed ruleset and deleting the entire Rulese schema and re-importing the skimmed rules package, because i believe it is tough to find the impacts. Is there any alternate that we can consider by deleting the older rules from different set to tables from the DB.
In terms of other options you could trace with db options enabled to see the targeted tables or you could explore the possibility of calling the ootb activity that the UI is a wrapper around in a loop wiht your own list for parameters(exclude the skimmed/open version) Delete_RuleSet_Start.