Not sure of having an OOTB wizard other than delete a ruleset wizard. However, we could attempt the following steps to perform non-associated rules (data rules should be associated to ruleset though) through a report definition & activity.
Create a report definition on class Data-Rule-Summary...
also disable - Paging option under Report Viewer tab.
Create a new activity to call report definition using Call Rule-Obj-Report-Definition.pxRetrieveReportData to build pxResults
issue either 'Obj-Delete' or 'Obj-Delete-By-Handle (pzInskey)' enabling Immediate option.
Note: don't call Obj-Delete. Use "Call Delete" instead to ensure appropriate rule maintenance is performed.
please backup rulesets/rules noting the rule count
ensure there are no rule checkouts from the filtered versions
ensure filter criteria applied on report definition is valid/correct
export pxResults to an excel sheet after running the report definition to match with the rule count
and double check rule eligible-ness for deletion
perform rule deletion with one ruleset version initially to ensure code correct-ness
if the count of rules are very high, incremental deletion of rules would help instead of running into not responding mode.
an incremental deletion would be similar to using OOTB delete a ruleset wizard
through OOTB ruleset deletion process
Delete an entire RuleSet or a specific version of a RuleSet
The deleted RuleSet will be saved in a a file called "RuleSetName_RuleSetVersion_DELETE.zip" in PRPC's explicit temporary directory.
If you would like to restore this file, just enter the RuleSet and Version and press the 'restore' button
through DB scripts - we could delete the ruleset versions. please refer the PDN link for PRPC v4.1. WHICH is NOT recommended as cache won't be updated and many tables are updated in newer PRPC versions...
There is no such thing called "Data Rules" in PRPC.
"Data- Objects" are not rules. They are not rule resolved (or) applied to any specific class.
Some "Data- Objects" are ...
These are not cached anywhere. If there is a need to delete them; lookup the relevant records from pr_data_admin table with a filter on pyRuleSet. Once the records are found you could delete them from your DB client; either run the delete SQL or use delete menu options in your DB client (like TOAD).
Apply caution before deleting data objects ; they might still be referred by other data (or) rule objects in your application. Ensure they are not being referred anywhere and only then go for the delete.