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.

Security of relevant records

Updated on April 5, 2022

You can define a list of relevant records in one or more case types or data types in your application before you deliver the application to customers or other development teams. By updating a related when rule, you can enable or disable certain access groups to add or remove relevant record entries from a class.

You can secure relevant records by updating the pyEditRelevantRecords when rule, which is part of the .pzEditRelevantRecords internal when rule. The .pzEditRelevantRecords when rule, which contains default conditions to secure relevant records, consists of the following when rules:

.pxEditRelevantRecords (non-editable)
This rule restricts changes to relevant records entries associated with classes in Pega- rulesets. You cannot change the relevant records that are delivered with Pega classes, such as the Work- class.
.pyEditRelevantRecords (editable)
This rule is an extension point that you can override in your applications to define custom logic in order to secure the relevant records that you deliver with your applications. For example, you can save this rule to your application ruleset and modify the access group condition. For more information about modifying rules, see Copying a rule or data instance.

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

Close Deprecation Notice
Contact us