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

Rule-Access-Role-Obj does not prevent saving Segments



The requirement is to prevent certain users from saving Segments.

To achieve this, an Access Role has been created for Rule-Obj-Report-Definition-Segment class with "write" and "delete" privileges restrictions.

This works fine when performing a Create New segment or Save of an existing segment.

However, no error is displayed when performing a Save-As operation of a segment rule and the system not preventing a new segment rule being created.

The expectation is that system should prevent an segment rule being created in a Save-As operation.  

Error Messages

Not Applicable.

Steps to Reproduce

  1. Create access role for example: <your application>:User4 cloned from PegaRULES:User4.
  2. Create access role for example <your application>:MarketingAnalyst cloned from PegaNBAM_FM:MarketingAnalyst.
  3. Create access group configured with above roles and portal PegaMarketing.
  4. Create a test operator that uses that access group.
  5. Role <your application>::User4 should already have a Rule-Access-Role-Obj for class Rule-Obj-Report- which prevents writing and deleting instances.
  6. In role <your application>::MarketingAnalyst create a Rule-Access-Role-Obj for class Rule-Obj-Report-Definition-Segment which only allows reading instances (set Read Instances = 5) but prevents writing and deleting instances (set Delete Instances = (blank) or 0) and Write Instance = (blank) or 0))
  7. Use the test user to try to save-as an existing segment.
  8. This time observe that snapshot and the buttons are different. No error is displayed preventing the segment rule being created.

Root Cause

This issue was determined to be a product enhancement request. When a Access Role has been defined with read-only option, all the rules within the class will not be writeable. However, when opening a rule in Designer studio, the Save-As button is still enabled giving developer a wrong impression the Save-As operation can be performed.


An enhancement request, FDBK-15334, has been created for consideration by Pega Product Management. to remove the save-as button in rule form in case of read only rules.


Published May 25, 2016 - Updated October 8, 2020

Was this useful?

100% 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