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

Unable to update the Role Access Names in application

SA-40483

Summary



User is unable to update the Role Access Names in application with Pega 7.2.2.


Error Messages



pyAccessRole:<Application Name : Role Name> does not exist or is not a valid entry for this ruleset and its prerequisites


Steps to Reproduce



1. Create application ABC with version 01-01-01, So PRPC will create RuleSet ABC with version 01-01-01.
2. Create RuleSet version 03-01-01.
3. Point the RuleSet ABC:03-01-01under Application RuleSets:



4. Create RuleSet Version ABC:04-01-01
5. Open the RuleSet ABC rule and mention ABC:03-01-01 and ABC:04-01-01


6. Create Access Role Name under ABC:03-01-01 RuleSet


7. Try to update the Access Role Name


Root Cause



Access Role Name does exists under ABC:03-01-01 RuleSet and user has added ABC:04-01-01 version in RuleSet stack.

​ So while saving the Access Rule Name, PRPC is checking whether Access Role Name rule exists under ABC:04-01-01 RuleSet.

As there is no such rule under ABC:04-01-01 version, PRPC is throwing error message.


Resolution



Local-Change 1:

Change RuleSet Validation to Application Validation in RuleSet rule:


Local Change 2:

Remove the ABC:04-01-01 RuleSet from RuleSet stack.

Local Change 3:

Mention the RuleSet ABC:04-01-01under Application RuleSets and Save-As the Access Role Name to ABC:04-01-01 version.

Suggest Edit

Published September 25, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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