Skip to main content


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

Configuring views for cases

Updated on November 15, 2021
Applicable to Theme UI-Kit applications

Display relevant information and gather data from users by creating views for cases and associating the views with case types. When you create views, you decide what fields the users see and how they interact with the fields as the case moves towards a resolution.

To save time, you can reuse dynamic views, which are standard forms that your application automatically manages for each case type that you define. By default, the dynamic view displays the fields in the contextual data model during different events, such as case creation and resolution. You can edit a dynamic view to ensure that your case meets your specific business needs. You can reuse the following default dynamic views:

Create
Prompts a user to provide information about a case, before processing the first step in the case life cycle.
Edit
Provides controls for modifying case information at run time. Applications display this view with the Edit details label.
Review
Presents case information to a user in a read-only format. Applications display this view with the Case information label.

To increase flexibility and efficiency of your application, you can create your own custom views, and then associate them with steps in your case type. For example, in your case view, you can include fields that are read-only, such as a case ID, and fields that a user fills out, such as personal details or a phone number.

  • Configuring dynamic views

    You can configure dynamic views that your application displays when users proceed through a case. By changing the default fields in these views, you can customize the forms that users access when they create, update, or review the case.

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