Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

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.

SECU0011 alert: Custom SQL in an RDB method must use class directives and not table names when Policy Condition rules have been defined to enforce row-level security when viewing instances

Updated on April 5, 2022

The security SECU0011 alert is generated when row-level security is enforced for viewing instances, and the custom SQL in any of the RDB methods does not use class directives. For more information, see the Class keyword section in Connect SQL form Data mapping. For more information, see Connect SQL form - Data mapping.

Example message text

Custom SQL in an RDB method must use class directives and not table names when Policy Condition rules have been defined to enforce row-level security when Viewing Instances.

If you would like to correct this, modify the custom SQL in RDB method to use class directives instead of table names.

Tags

Pega Platform 7.2.2 - 8.3.1 System Architect Lead System Architect Security Communications and Media Consumer Services Financial Services Government Healthcare and Life Sciences Insurance Healthcare and Life Sciences Manufacturing Consumer Services Consumer Services

Have a question? Get answers now.

Visit the Support 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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us