Views in Constellation
You use Views to collect and display information that is relevant to Case resolution.
Users interact with your applications by using Views. Views are the interface for each assignment in the Case Life Cycle and each data object. The forms that collect user information, tables that display list data, and read-only tabs that make primary information readily accessible are all examples of Views.
You can populate Views with UI elements, such as text fields, checkboxes, lists, and other Views. The selection of UI elements that are available for you to populate your Views is determined by your Data Model. It is essential to correctly configure your Data Model before you configure the Views.
The four types of Views
There are four primary types of Views in Constellation applications:
|
View |
Description |
Editability |
Link to configuration information |
|
Full Page View |
The main interface in which the user processes Case work or accesses information about a data object. The system creates one full View for each Case or data object. |
Read-only |
|
|
Partial View |
A View that you create for a specific Case or object to display data. These Views include custom Views that you create during application development and default Views that the application creates, namely the Details and Preview Views. When enabled, the Confirmation View also appears in the Case Views list. |
Read-only |
|
|
List View |
A View that relies on a data source. Depending on the configuration, the system can display lists as tables, timelines, or tile-based galleries. By default, every Case includes a list that contains open Cases and a list that contains Primary Fields. Data objects do not support the timeline View.
|
Read-only |
|
|
Form View |
A View that the user interacts with when working on the Case. The system creates a form View for each Step in the workflow when you click Configure View on the Workflow tab. The Create and Edit Views appear automatically in the Form list. The Create view represents the opening form of your application, and the Edit view represents the form that is connected to the edit button in the Case header. The form list also includes the default Case history list View. Form Views use the default form template or simple column templates. |
Editable and read-only |
Note: For complete information about configuring Views in Constellation, see Working with Views.
The Full Page View
The Full Page View, or the Full Case View, represents a single Case in Pega Platform™. Optimized for almost any Case or business object, the three-pane layout accommodates a lot of information, much of which is available without scrolling or moving to other Views.
In the following image, click the + icons to learn more about the main areas of a Full Case Page built on the Constellation design system:
Creating Views
Views can be created for both data objects and Cases.
Data object Views
Views associated with a data object can be accessed via the UX tab on the data object's menu.
Elements associated with the Full Page View are found on the Full Page View tab. Partial, List and Form Views associated with the data object are on the Other Views tab. Views for the data object can be constructed with fields from the data object and other Views created for the Data object. By default, Data object Views are read-only.
When a data object is associated with a Case Type through a data relationship, the Case Type has access to all of the fields and Views associated with that data object.
Case Views
Case Views can be created in one of two ways. You can create a View for a Step by clicking the button which appears in the contextual properties pane when a Step is selected.
You can also create a View by clicking the UX tab in the Case Life Cycle designer's main menu. This will give you access to the Views list, where you can create any of the View types mentioned earlier. Elements associated with the Full Page View are found on the Full Page View tab, while Partial, List and Form Views associated with the Case are on the Other Views tab.
By default, Pega Platform generates a Form View for each Step in the Case, excluding Automation Steps where Views are not relevant. The name of the View is the same as the name of the Step. These top-level Views can be found in the Form section on the Other Views tab.
If you Create a form View by using the UX tab of a Case, you cannot associate it directly with a Step. In this scenario, you can embed the form View in a top-level form for that Task Step only.
Best practices for configuring Views
When using App Studio to create and configure Views, all of the background work related to Rule creation and class handling is done automatically.
When you embed a field in a Case View (Work-), the system automatically generates a View in the dataclass and names it after the top view. Over the course of app development, the system could potentially create a list of Views with similar names, which makes editing difficult.
As a best practice, build Views from the lowest embedded level upwards. For example, when you want to reuse fields, the best practice is to embed those fields in a View created directly in the target class. For the View maintenance perspective, embedding Views is preferable to embedding fields. The following figure illustrates the process of embedding a Company Bank Details View that is associated with an Account data object into the Step: Capture-Contact details-PI of a Case:
Saving Views
By default, Constellation UI View changes are auto-saved. If you change a View, the UI is changed in real-time. There are no save, cancel, or revert options when configuring Views.
Design for reuse
Views are reusable in applications with multiple Case Types. For example, a View that displays information about a retail product Data Object, including fields such as Product name, Description, SKU, and Price, can apply to Views across an array of sales and distribution Case Types for a manufacturing company.
Check your knowledge with the following interaction:
This Topic is available in the following Module:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?