Views

Consider a Process for making loans. In this example, there are two Steps:

1. 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.


2. In the second Step of the Process, loan officers have a Loan officer View that displays the collected data. Loan officers can read but cannot update the customer's information. The Loan officer View contains fields for officers to enter information such as loan insurance qualification and approval reason.

In the center of the following image, slide the vertical line to view the Steps of the loan application Process:

During View creation, you determine what information users need to see or enter to perform specific Tasks. For example, a developer creates a View for drivers to quickly and easily report to a trucking logistics company when their trucks kick up rocks and cause minor windshield damage. Various design decisions must be considered to ensure the best user experience. What fields should users see? What types of values do users enter into the fields? In what order do you want to display the fields? Do the fields need to be editable or read-only, visible or hidden, required or optional?

The following image of a Report problem View shows one example of many possibilities when these questions are answered:

Check your knowledge with the following interaction:

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 values together under a single header and provide methods 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.

A View is a reusable configuration of UI elements that you can use to interact with a Case. A form is a reusable interface for collecting data from users and processing work.  A form is a type of View, but not all Views are forms. For example, in an online shopping website, the customer needs to enter personal information and shipping information when placing their order. A form is used to collect the customer's first name, last name, email, phone number, and address. A View is later used to display a read-only order confirmation with the contents of the user's purchase and their order total once the transaction is completed.

In the Constellation UI architecture, forms are preconfigured with buttons like Cancel, Next, Previous, and Submit.

The following image shows the completed form from the first section of this topic; in the first View, there is a radio button field that is used to conditionally show the second View based on user input: