Support Article
Performance issue with ABAC conditions generating "IS NULL"
SA-68817
Summary
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
- Create a table with multiple (millions) rows.
- 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.
Resolution
An enhancement request, FDBK-29067, is created for consideration by Pega Product Management.
Published January 31, 2019 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.