Incorrect rule count in rule set form post upgrade to Pega7
Rule count for 01-03-21, 01-03-22, 01-03-23 is been shown as 0, though we have a number of rules in the particular rule set versions. Due to this it allows to lock rule set with checked out rules and is causing issue in rule migrations.
Posted: 5 years ago
Posted: 3 years ago
When you next see a situation where the screen shown above is giving a wrong count, do a pega trace of the generation of that screen, so you can look at exactly what operation is returning the wrong count. By studying that trace, you should be able to determine whether the operation is a direct db query, or an rdb operation, or an obj-browse, or a report definition being run (which in turn is probably a direct db query). /Eric
This issue may occur due to following reasons.
1. Rule tables might not have been updated properly post upgrade to Pega 7.
2. Triggers might not have been enabled / or not firing properly