Skip to main content

Marking records as relevant records

Pega Community logo

Note: The following content, referenced from Pega Community, is included here to help you better achieve the module learning objectives.

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 property, click Data Model Property .
    • To open correspondence, click Process Correspondence .
    • To open a flow, click Process Flow .
    • To open a flow action, click Process Flow Action .
    • To open a harness, click User Interface Harness .
    • To open a paragraph, click User Interface Paragraph .
    • To open a section, click 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 .

    Note: 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.

  • App Studio overview

    Turn your application development into a no-code, user-friendly experience by working in App Studio. In this authoring environment, you can configure the main elements of your applications that include templates for your business processes, personas that are involved in the processes, interaction channels, and data.

  • Installing components

    Install a component to make a reusable feature available to applications on your system.

  • Creating a rule

    To save time and ensure that your projects adhere to the unique needs of your clients, create rules and data instances using reusable elements of your application. By combining a rule type, name, class, and ruleset, you provide a unique identity for each rule that you create.

  • Configuring a data model for a case

    Configure a data model to define the data that you want to use in a case. For example, to include a user email address in a case, add an email address field to the data model.

  • Views for cases

    Views in cases represent forms that users interact with to provide information for case processing. When you create views, you decide what fields the users see and how they interact with the fields as the case moves towards a resolution. When you create, configure, and organize relevant fields in a form, you can clearly communicate to users data that they need to provide to process an assignment in a case.

If you are having problems with your training, please review the Pega Academy Support FAQs.

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 Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice