Securing relevant records
You can define a list of relevant records against one or more case or data types defined in your application before shipping your application to customers or downstream development teams. The .pzEditRelevantRecords when rule manages whether users are permitted to add or remove relevant record entries from a class.
This rule comprises the following when rules:
- .pxEditRelevantRecords, which restricts changes to relevant records entries associated with classes defined in Pega- rulesets. End users cannot change the relevant records that ship with Pega classes, such as Work-.
- .pyEditRelevantRecords, which is an extension point that you can override in your applications to define custom logic for securing the relevant records that ship with your applications.
- Managing relevant records
Speed up your application development by curating records that you need to include in your case types and data types. Relevant records control design-time prompting and filtering in several areas of App Studio, and as a result, reduce time-consuming searching through unrelated records in your cases.
- Marking records as relevant records
To save resources and speed up application development, promote reuse in data types and case types by marking a rule as a relevant record. Relevant records control design-time filtering options in case types and data types in App Studio. As a result, when you create an application, you receive a set of relevant options, instead of an extensive or incomplete selection of choices.
- Understanding relevant records
Relevant records describe the rules that refine the behavior, presentation, and definition of a case type or data type. They commonly designate records from an inherited class as important or reusable in a child class, and control the majority of the prompting and filtering in the settings for case types and data types. Relevant records are also used to build conditions, for example, to determine whether a customer should receive a particular proposition.