Views
As part of completing work, a View is a component of the user interface that gathers information from a user or displays information to the user. Views display the fields necessary to complete the current assignment.
For example, a loan application might provide online Views with fields for applicants to enter their personal information, loan details, and relevant financial information. The application might provide different Views for an internal loan officer, who sees the applicant's information as read-only fields and enters the resulting approval or rejection decision and explanation into editable fields.
In applications that you build with the Constellation, Views use predesigned workflows, patterns, and components to provide users with a cohesive, intuitive experience. You add relevant fields to the Views, enabling users to input the necessary information. Pega Platform™ stores the name of the field and the value of the user input as a data element, which makes the information reusable. The application can make the stored data elements available for editing or present the data as read-only.
Views for specific tasks
Consider a process for making loans. In this example, there are two steps:
- The first step in the process requires customers to enter information for a loan application. The form contains fields for entering information such as the customer's name, the loan amount, and the loan type. After customers complete the form, the system sends the request to loan officers for review.
- In the second step of the process, loan officers have a Loan officer View that displays the data collected from the application. Loan officers can read but not update the customer information. The loan officer View also contains fields for officers to enter information such as loan insurance eligibility and whether the application is approved or rejected.
In the center of the following image, slide the vertical line to view the steps of the loan application process:
View considerations
During View creation, you determine the information that users need to see or collect to perform specific tasks. For example, you create a loan application View in which users enter specific information.
In the following image of the loan application View, click the + icons to learn more about the items to consider and questions to ask when you create a View:
Field groups
A field group is a cluster of individual fields that, together, present related data inside a View. The individual fields can come from the Case Type Data Model or from various data objects.
Field groups help to organize related fields together under a single header and provide the tools to add instructions or temporarily hide fields in collapsible sections within a View.
You create field groups inside a View and they are specific to that View only.
Views versus forms
The View is a reusable configuration of UI elements that you can use to interact with a Case. The form is an interface for collecting data from users and processing the work. A form can have one or more Views. But the View is not always a form. For example, in an online shopping website, the customer needs to enter personal information and shipping information. Views can have UI elements such as the first name, last name, state, country. The form can have the submit and cancel buttons.
In the Constellation UI architecture, forms are preconfigured with buttons like , , , and .
In the following image, click the + icons to learn more about how forms, Views, and fields work together to create an interactive web page for a Case:
Check your knowledge with the following interaction:
This Topic is available in the following Module:
Want to help us improve this content?