Skip to main content

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

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 creating a view.

Note: In the Options list, you can mark any field as Optional, Read-only, Required, and Calculated (read-only).

Views versus forms

The view is a reusable configuration of UI elements that you can use in any context. 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 following image, click the + icons to learn more about how forms, views, and fields fit together on a page.

Note: Pega Platform™ is built on platform components such as views to create forms.

Check your knowledge with the following interaction:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

100% found this content useful

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice