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

Need to correct RARO instances associated with ruleset version



Due to a problem with the cloning tool system has many Rule-Access-Role-Obj (RARO) instances that are incorrectly associated with a ruleset version. Need to correct this in lower environment and then migrate to upper environments.

Error Messages

Not Applicable

Steps to Reproduce

1. Create an Access Role Name.
2. Create an Access of Role to Object instances to grant that Role Name access to a class.
3. Navigate to PegaButton>Org&Security>Security>Access Roles to open the Access Roles Landing Page.
4. Click the "Add a Row" button to add a new Access Role Name.
5. Enter the required information, and select the Role Name created in step 1 under "Clone From"
6. Submit the landing page to clone the Role Name.
7. Open the ruleform for the newly created role name (you may need to go through the Application or Rules Explorer for this).
8. Open the associated Access of Role to object instance, and note that it has a ruleset version.

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules. The cloning tool is incorrectly associating the rule-access-role-obj with a rule set version.


HFix-9503 needs to be installed via update manager to correct issue with the cloning tool so that no further RARO instances are incorrectly associated with a ruleset version.

To update the existing RARO instances which have been incorrectly been associated with a ruleset version you need to do the following:

1. Create a list view of the RARO instances that need to be updated.

2. Write an activity which will loop over the list view to open each instance, set the ruleset version properties correctly, and then save and commit those changes to the database.  

You need to set the following properties:

pyRuleSetVersion to an empty string ""
pzRuleSetVersionPatch, pzRuleSetVersionMajor, and pzRuleSetVersionMinor properties to -1

Optionally you may also want to set the following properties:

pyUpdateOperator, pxUpdateOpName, pxUpdateSystemID to values to identify who performed the updates
pxUpdateDateTime set to current time.

3. Create a new RAP file in this environment.

4. Import new RAP into higher environments with override option to make the same changes in those environments.

Published April 1, 2016 - Updated October 8, 2020

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