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 February 7, 2022

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.

  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 Page title field, enter a descriptive name.
    • To name a form view, in the field in the header of the configuration dialog box, enter a descriptive name.
  6. Click Submit.

Define the fields in your view to collect information from users by completing the following tasks:

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us