You are here: Record management > Adding relevant records > Relevant records

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 to control the majority of the prompting and filtering in the settings for case types and data types.

Relevant records for a case type can include references to fields (properties), views (sections), processes (flows), or user actions (flow actions) that are explicitly important to your case. For example, fields marked as relevant define the data model of the case. Processes and user actions marked as relevant appear in prompts for case-type settings to encourage reuse. Views marked as relevant appear as reusable views.

For a data type, relevant records designate the most important inherited fields for that data type. These relevant records can include fields that are defined directly against the class of the data type and fields inherited from parent classes. View data types by their relevant records to see a complete and succinct data model for a data type.

You do not typically need to manually manage relevant records associated with a case or data type. Fields, views, processes, and user actions are automatically marked as relevant records when you create them in the context of a case type or data type.

Relevant records control design-time prompting and filtering in several areas of case types and data types.

Relevant records in Data Designer

New fields that you add to the data types in these areas are marked as relevant records.

Relevant records in case types