Posted: 2 Jan 2017 6:06 EST Last activity: 9 Jan 2017 4:00 EST
Delete unused/unwanted rules in a pega7.x application
Can anybody say, is there any way to find out all rules , which are not used at all (just created ,not refenced in any other rules) and if possible delete them instantly? (Or we need to go through all rules manually)
***Updated by moderator: Lochan to update Categories***
You can delete the ruleset by running the following wizard.
Designer Studio> System >Refactor > Classes > Delete a Class to start the wizard
This can’t work for the locked ruleset versions. It deletes a class and all of its pattern- inheritance dependent classes and associated objects such as properties, activities, instances (including work items, attachments and assignments).
To delete a rule, open the rule you want to delete and click Delete or Discard . The results depend on whether the rule is checked out to you (and so is deleted from your personal ruleset).
If this rule is in an unlocked ruleset that does not require check out, clicking Deletedeletes the rule.
If the rule is checked out and so is in a personal ruleset, Discard adds a line to the history of the (surviving) rule. You are prompted to confirm the operation.
Restrictions on deleting rules
Several conditions prevent a delete operation from completing:
You cannot delete a rule that belongs to a locked ruleset version. Instead, however, you can in most situations create a blocked rule or withdrawn rule in your application that masks — makes invisible to rule resolution — a rule no longer useful or wanted in your application.
By definition, you cannot delete standard rules, because they are part of the Pega 7 product. Many can be overridden, but none can be deleted.
You can't delete any rule or data instance unless allowed by an Access of Role to Object rule associated with your access role, and also not disallowed by any Access Deny rules associated with your access role.
You cannot delete a rule where the Circumstance or Start Time fields all are blank if your system contains other rules with identical keys that are circumstance-qualified or time-qualified. Delete the qualified rules first, and then delete the unqualified rule.
You cannot delete an Operator ID at a time that the operator has checked-out rules. Have the operator sign in, and delete or check in all rules in the personal ruleset.
You can't delete a concrete class that contains instances.
You can't delete a class — concrete or abstract — when the system contains rules with that class name as the Applies To class. You are prompted with a list of the rules that you must delete before the class rule itself is deleted.
You cannot delete a ruleset version rule that identifies a non-empty collection of rules. Delete each of the rules in the version first.
You cannot delete a ruleset for which a ruleset version exists. Delete each version first.