Adding a relevant record to your application
Promote a rule from a built-on application so that you can reuse it in another class. By supplementing your inherited rules with relevant rules that you choose, you can create data types and case types more quickly.
You must have permission to add relevant records to a class.
In the header of Dev Studio, click.
In the Class Name field, enter the class of a case type or data type, based on how you plan to use the rule.
Click Add Record.
In the Add Records dialog box, select the type and name of the rule to reuse.For data-type classes, you can select properties (fields) only.
- Managing relevant records
Manage your relevant records to consolidate records that are specific to your cases and data types. Marking records as relevant can reduce time-consuming searching through unrelated records in your cases.
- Marking records as relevant records
Promote reuse in data types and case types by marking a rule as a relevant record on its rule form. For example, you can mark a property as a relevant record to reuse it as an inherited record in child classes.
- 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.