Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Data models for case types

Updated on February 8, 2016

A data model for a case type displays the fields that are relevant to the case type. You define fields when you build a form or create a view. You also inherit fields by default when you create a case type. By managing fields in the context of a case type, you can make focused edits to your data model.

You can access the data model for a case type by clicking the Data model tab in Case Designer. On this tab, you can review, add, and remove fields. You can also configure a field based on the field type. For example, you can define the choices in a picklist or calculate a subtotal by adding together decimal values.

Contextual data model for a Job Application case type

Contextual data model for a Job Application case type

Review your data models periodically because they are updated with new fields as your team builds forms and creates views. If your team members have access to Designer Studio, they can use the Relevant Records landing page to customize the inherited fields that are relevant to your case types. These fields are displayed in Case Designer when you select the Show reusable fields check box.

Inherited fields in a contextual data model

Inherited fields in a contextual data model

By staying aware of the changes to your data models, you can encourage reuse of fields in your case types and avoid duplication.

Related content


Pega Platform 7.1.1 - 7.4 Case Management Data Integration Low-Code App Development

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