Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Able to lock the ruleset though the rules are checked-out



Despite having checked out rules in the ruleset, user is able to lock RSV. The checked out rule count is not updated.

Error Messages

Not Applicable

Steps to Reproduce

  1. Checkout a rule.
  2. Open a Ruleset. Verify the count for the Checked Out rules and the rules that are currently checked out.

Root Cause

An issue in the custom application code or rules.

The out-of-the-box Data-Rule-Locking pzGetCheckedoutRulesForRSV report definition retrieves the count by querying the pwbv4_rule_locking view in the database. Data-Rule_locking class is mapped to an incorrect database schema. In the Mapped to Schema, where the checked out rules are updated, the user Test connectivity failed for the Data-Rule-Locking class with 'Table ABC.pwbv4_rule_locking does not exist in database PegaRULES' error.
In the database, according to the privileges for pwbv4_rule_locking view, the Select Privilege is not granted on the pwbv4_rule_locking view.


Make the following change to the operating environment:

Add the Select Privilege for the pwbv4_rule_locking View in the database.

Published August 15, 2019 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us