Skip to main content

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

Managing relevant records

Updated on January 14, 2022

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.
  1. In the header of Dev Studio, click ConfigureApplicationInventoryRelevant Records.
  2. 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.
    Result: The system displays a list of active relevant records for the specified class.
  3. 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.

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

Close Deprecation Notice
Contact us