Relevant records are a design-time feature specifically created to enhance the low-code experience in App Studio. Their primary purpose is to allow Lead System Architects (LSAs) to curate a list of pertinent rules for citizen developers. This curation has two main benefits. First, it filters the options presented in App Studio, preventing developers from being overwhelmed by irrelevant technical rules and reducing search time (Benefit B). Second, it enables LSAs to deliberately "promote" specific, pre-approved rules from built-on or framework applications for reuse in the current application layer, ensuring consistency and leveraging enterprise assets (Benefit C).

A: This is incorrect. Relevant records are a design-time feature for App Studio. They do not control the run-time availability or performance of rules; that is managed by rule availability settings (e.g., Available, Withdrawn).

D: This is incorrect. Relevant records apply to configurable rules (metadata such as properties, views, and flows), not transactional data or case instances. You cannot "promote" a data instance using this feature.

1. Pega Platform™ 23.1 Documentation

"Marking records as relevant": This document states

"To provide a record to application developers in App Studio

you mark the record as relevant... You can mark a record that is defined in a built-on application as relevant to make it available in your current application." This directly supports promoting rules from built-on applications for reuse (Option C).

2. Pega Platform™ 23.1 Documentation

"Relevant records for citizen developers": This source explains

"As a lead system architect (LSA)

you can curate records for citizen developers in App Studio to streamline the user experience and accelerate application development." This directly supports the concept of regulating design-time prompting and filtering to simplify the developer experience (Option B).

3. Pega Academy

"Low-Code App Builder" Module

"Relevant Records" Topic: Courseware explains that relevant records are used to expose rules to developers in App Studio

filtering out records that are not meaningful in the context of a case type. This prevents low-code developers from having to navigate through long lists of inapplicable rules. This supports the core idea of Option B.