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.For example, in a banking application, you can mark a property that holds an interest rate as a relevant record for a loan case type so it is easily available in App Studio when you build your loan application form.
You can mark only certain rule types as relevant records. You can also mark only records that are outside classes that Pega Platform provides by default, such as @baseclass or Work- classes.
Pega Platform automatically marks any records that you create in App Studio, such as properties, as records relevant to an appropriate context.
In the navigation pane of Dev Studio, open the rule form of a record that you want to mark as a relevant record:
- To open a data transform, click .
- To open a property, click .
- To open a decision table, click .
- To open correspondence, click .
- To open a flow, click .
- To open a flow action, click .
- To open a harness, click .
- To open a paragraph, click .
- To open a section, click .
In the list of instances, open the rule that you want to mark as a relevant record.
On the header of the rule form, click.Your application marks the record as relevant for the Applies to class of the record.
To verify that the record is now relevant for the class, on the confirmation message, click View, and then review the relevant records landing page.
- 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.
- 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.
- 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.