Relevant records
Relevant records are rules that have been marked for reuse automatically by Pega or manually by application developers in Dev Studio. More technically advanced developers might configure advanced behavior on a rule in Dev Studio, then mark the rule as relevant so that the rule is accessible by other developers from prompts in App Studio. For example, a developer creates a standard approval service level agreement (SLA) with a passed deadline interval and marks it as a relevant record. Leveraging relevant records allows developers to design and configure application behavior using developer-approved records. Using relevant records during application development improves application quality and reduces development time.
When you create records in the Data Designer or Case Designer, Pega automatically marks the records as relevant. For example, Pega automatically marks fields, views, and processes as relevant records when you create them in the context of a case type or data type. You can manually mark the following rule types as relevant records:
- Properties
- Sections
- Harnesses
- Paragraphs
- Correspondences
- Service Level Agreements
- Flows
- Flow actions
Caution: Verify that a record is guardrail-compliant before you designate the record as a relevant record.
Developers access relevant records in the Data Designer or the Case Designer when adding a step to a process, adding fields to a user view, or applying a service level. For example, when configuring a user view for a step in the case life cycle, the Fields and Views lists are populated with relevant records.
