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

Access to Role Obj does not restrict ruleset version addition



Unable to restrict adding a ruleset version for a specific role by defining the Access Role to Object.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create the Access Role to Object for the class rule-ruleset-version.
  2. Add 0 to modify instances.
  3. Click the + button to add a ruleset version.

Root Cause

This behavior is as  per Pega product design.
There is no restriction to prevent the modal window pop-up.


Perform the following local-change:
  1. Clicking the + button in the Ruleset version Addition form. The modal window opens.
  2. Click Ok on the modal window and click the Save button. An error displays stating that the user does not have the authorization to modify the instance and a save does not happen. As a result, the ruleset version is not added.
  3. Add 0 on the Run Report option on the Access Role to Object to prevent the modal window popup from opening.

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