Table of Contents

Marking records as relevant records


Only available versions of this content are shown in the dropdown

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.

  1. 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 Records Data Model Data Transform .
    • To open a property, click Records Data Model Property .
    • To open a decision table, click Records Decision Decision Table .
    • To open correspondence, click Records Process Correspondence .
    • To open a flow, click Records Process Flow .
    • To open a flow action, click Records Process Flow Action .
    • To open a harness, click Records User Interface Harness .
    • To open a paragraph, click Records User Interface Paragraph .
    • To open a section, click Records User Interface Section .
  2. In the list of instances, open the rule that you want to mark as a relevant record.

  3. On the header of the rule form, click Actions Mark as relevant record .

    Your application marks the record as relevant for the Applies to class of the record.
  4. Optional:

    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.

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.