Asset reuse and relevant records

In App Studio, you use relevant records to encourage the reuse of rules in App Studio and the Case Designer. 

As your organization implements its maturity model, more reusable enterprise assets become available. Manage the common assets through a center of excellence (COE). 

Relevant records designate records of a case or data type as necessary or reusable in a child class. Relevant records for a case type can include references to fields (properties), views (sections), processes (flows), user actions (flow actions), correspondence rules, paragraphs, harnesses, service-level agreements, and When rules that are explicitly important to your case. For a data type, relevant records designate the most important inherited fields (properties) for that data type.

The relevant records can include records that are defined directly against the class of the case or data type and fields inherited from parent classes.

Designating a record as a relevant record controls most prompting and filtering in a case type and Data Designer. For example, user actions and processes that you mark as relevant records are displayed when you add a step in the workflow of a case life cycle.

Fields marked as relevant for a case type define the data model of the case. Processes and user actions marked as relevant are displayed as prompts in the case type to encourage reuse. Views marked as relevant appear as reusable views.

When you create fields, views, processes, and user actions in App Studio, Pega Platform™ automatically marks them as relevant records. You can manually designate relevant records on the Relevant Records landing page. It is also possible to add a relevant record by using pxSetRelevantRecord activity in Dev Studio. For more details, refer to community article on how to add Relevant Records. 

Check your knowledge with the following interaction: