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.For example, in an insurance application, you can mark a value field of an insured object as a relevant record so that it is available to all child classes, such as a class that stores records for jewelry insurance or a vehicle insurance case type.
In the header of Dev Studio, click.
In the Class Name field, enter the class of a case type or data type for which you want to display relevant records.
By default, the system displays only active relevant records for the selected class.Note: The system displays a list of active relevant records for the specified class.
Do any of the following actions:
- To display inactive records for the specified class, select the Show inactive relevant records for the class check box.
- To display records that the current class inherits in the class hierarchy, select the Show inherited relevant records for the class check box.Note: The Mark relevant at column shows at which class level the particular record is relevant.
- To mark a record as active or inactive for the current class, click the Actions icon, and then select an option that meets your need. For example, select Mark active for current class.
- 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.
- 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.
- Rules in Pega Platform applications
A rule is a basic building block of an application that defines its behavior. Pega Platform applications contain many types of rules that specify different types of behavior. Because rules are reusable, by implementing them, you can save time and resources when you build your application.
- 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.