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

Multiple When Rules issue of Attachment Category



For an attachment category, the access control is correct when there's only one "When Rule" defined; but it will be always no access if there're multiple "When Rule", and one of the "When Rule" was evaluated to false.

Error Messages

Not Applicable

Steps to Reproduce

  1. Let's say there's a attachment category - OTHER_ATT, and two "When Rule" - pyAlwaysTrue & CanEditOtherAttach; take the "Delete own" access as example.
  2. When there's only one "When Rule" - pyAlwaysTrue, which enabled the "Delete own" access; the attachment deletion is enabled for the uploader.
  3. After adding the CanEditOtherAttach - which will be evaluated to false, and also enabled the "Delete own" access; the attachment deletion is disabled for uploader then.

Root Cause

An issue in the custom application code or rules.


Here’s the explanation for the reported behavior:

When rules evaluation in Attachment Category always uses AND logical condition. This is how it works. Till Pega 7.1.5, there was no AND logical condition evaluation for when rule ‘Delete Own’ and ‘Delete Any’ abilities (not even with OR). This was BUG reported and is resolved in Pega 7.1.6.

Only alternative I think we can have is having a single when rule and add the other when rules in the Advanced tab.

Published May 17, 2017 - 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