Skip to main content

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

Creating views for case types

Updated on May 11, 2022
Applicable to Hybrid mode applications

Create personalized views for your case types to capture the data that the case requires to resolve your business processes. As a result, you improve the flexibility of your application and accelerate case resolution, because you can define specific fields that collect information for specific cases. By creating a view, you can also lower application development time and costs, because you can reuse views for multiple case types.

For example, you can create a view that captures feedback from a customer after resolving a case, such as a loan request, and then save time by reusing the view for other case types in which you need to collect feedback from a customer.
You can create views that are based on a table and display content in columns, or as forms that display a list of fields.
Note: The following procedure describes creating views for Theme Cosmos and classic Pega Platform applications. For information about creating views for Cosmos React applications, see Creating views in Cosmos React.
  1. In the navigation pane of App Studio, click Case types, and then click the case type that you want to open.
  2. In the case working area, click Views.
  3. Click Create new view.
  4. In the Create new list, select the type of view that you want to create:
    • To create a view based on a table, click List view.
    • To create a view based on a form, click Form view.
  5. Name your view:
    • To name a list view, in the View name field, enter a descriptive name.
    • To name a form view, in the New view field in the header of the configuration dialog box, enter a descriptive name.
  6. Click Submit.
What to do next: Define the fields in your view to collect information from users by completing the following tasks:
  • Adding single-value fields to forms

    Collect specific, single pieces of information from users when they process a case by adding a single-value field to a form. For example, you can add a field that references a phone number to a form that prompts users to enter their personal and address details.

  • Adding tables to views

    Help users access and compare data by setting up a form with a table. Tables are a basic component that you can use to create a clear interface in information-heavy contexts.

  • Reusing fields on forms

    Save time and build forms that are convenient to maintain by referencing fields on other, existing forms. For example, you can reuse a field group to capture different user details on a new form, such as name, surname, mailing address and phone number, instead of creating separate fields for each item.

  • Reusing forms

    You can reduce development time and maintain consistent layouts between sets of fields in your case type by embedding forms in other forms. For example, you can prompt users to review their employment history by embedding their Work History form in a Confirmation form.

  • Previous topic Skipping forms to collect information before case processing
  • Next topic Adding single-value fields to forms

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