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

Performance issue with ABAC conditions generating "IS NULL"



Performance degrades when the Attribute-based access control (ABAC) policy condition generates the IS NULL Where clause.

When an application uses ABAC, the ABAC policy conditions are automatically added to the generated queries. When the the Right Hand side (RHS) of the policy condition is NULL, the Where clause is added to the generated query and performance degrades

Error Messages

Not Applicable

Steps to Reproduce

  1. Create a table with multiple (millions) rows.
  2. Create an ABAC policy condition which states that an operator can read a row.

    When the IF Attribute1 = OperatorID.Value1 OR IF Attribute2 = OperatorID.Value2 If the OperatorID.Value2 is empty, the query generated from the report definition still includes the WHERE clause of the 'OR Attribute2 IS NULL'.

Root Cause

This issue was determined to be a product enhancement request.


An enhancement request, FDBK-29067, is created for consideration by Pega Product Management.


Published January 31, 2019 - Updated December 2, 2021

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