Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Adding a relevant record to a specified class in your application

Updated on November 15, 2021
Adding a relevant record to a class

Expand the library of relevant records by adding records and classes that are most likely to be reused for a case or data type.

For efficient management of resources, promote a rule from a built-on application so that you can reuse the rule in another class. By supplementing your inherited rules with relevant rules of your choice, you can create data types and case types in a quicker and more efficient way.
Before you begin: For Pega Platform version 8.5 and earlier, ensure that you meet one of the following conditions to successfully add relevant records to a specific class:
  • Ensure that the classes to which you add relevant records are in rulesets that do not start with Pega- unless you have developer access.
  • The class to which you want to add relevant records is one of the following: PegaSample-Data-Product, PegaSample-Data-ContactInformation, Work-Channel-Triage-Email, Data-Portal, Data-.
  1. In the header of Dev Studio, click ConfigureApplicationInventoryRelevant Records.
  2. On the Relevant Records tab, in the Class Name field, enter the class of a case type or data type in which you plan to use the rule.
  3. Click Add Record.
  4. In the Add Records dialog box, select the type and name of the rule to reuse.
    Note: For data-type classes, you can select only properties.
  5. Click Submit.
    Result:
    Relevant records added for a selected class
    The Relevant Records tab showing the relevant records in the context of a selected class
    The relevant rule is ready for reuse in the list of relevant records that is available in the application.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us