Try turning on the tracer so you can see where the zeroes are coming from. The tracer will tell you whether it's a report rule, an obj-browse, an executeRDB, or something else, and whether a max limit is causing the items to be missed, or whether some filter is removing them. /Eric
Please check that the pr4_rule_vw table is populated with the expected rules. In versions prior to Pega 7.1.8, database triggers were used to maintain the pr4_rule_vw table so if you find it does not contain the expected entries check to see if the database triggers are enabled.
For example, if you trace the "save-as" action on a rule form in the developer portal, you may find that there are various max limits imposed during the composition of the ruleset dropdown list. Let's say this maxlimit is 2000. What that means is that if you had more than 2000 rulesets, it's conceivable that some of your rulesets might not be available during save-as as a choice.
On the other hand, if you chose to trace another action than save-as, you might see a different maxlimit, so it's hard to determine which maxlimit to regard as the bottleneck. /Eric