Views
Views
As part of completing work, an application gathers information from or displays information to users with views, also referred to as forms. 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.
Design views so that users can enter the necessary information into relevant fields. Pega Platform™ stores the user input as data, which makes the data reusable. The application can make the stored data 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 and two views.
The first step in the process requires customers to enter a loan application. The view 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 only read but not update the 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
You determine the information users need to see or collect to perform their specific tasks. You create a view in which users enter the specified information.
Before you create a view, ask the following questions:
- What fields do users need to see?
- Are the fields editable or read-only?
- How do users enter values in those fields?
- Are users required to modify the values in fields?
You can prepare by creating a table with the answers to these questions. The following example shows fields for a loan application view.
| Name of Field | How to Enter Field Values | User Entry |
|---|---|---|
| Amount | Enter dollars ($) | Yes – Required |
| Loan Type | Select available options from drop-down list | Yes – Required |
| Requested Terms | Select available options using radio buttons | Yes – Required |
| Origination Date | Entered by system, display date | No – Read-only |
Check your knowledge with the following interaction.
Want to help us improve this content?