A Policy condition rule used to enforce row-level security when Viewing Instances cannot reference linked or unoptimized properties
We have a requirement to restrict specific State and Line of Business combination rows for offshore users.
So, we have created Access Control Policy where State and Line of Business columns are used. Creating new reports are working fine, but on existing reports are not getting fetched. On tracer and clipboard, we see error
“A Policy condition rule used to enforce row-level security when Viewing Instances cannot reference linked or unoptimized properties”
pzInsKey is referred
Please suggest
HCA Healthcare
US
@Anushree The error occurs because the Access Control Policy condition references linked or unoptimized properties, which cannot be used for enforcing row-level security. To resolve this, ensure that the properties used in the policy condition (State and Line of Business) are optimized for reporting. You can do this by running the "Optimize for reporting" wizard in Pega, which creates dedicated database columns for these properties. If optimization is not possible or feasible, consider storing the required data directly in a separate optimized property during case processing to avoid linked property references. Additionally, verify that pzInsKey or any other linked properties are not part of the condition. After making these changes, clear the cache, re-save the Access Control Policy, and test to confirm the existing reports are fetched correctly.