Working with views
You use views to display and collect information in your applicaton, for example, to fulfill requests or process cases. By setting up intuitive views and populating them with fields, you help users process their work with less effort.
Cosmos React introduces a new approach to view authoring. For a brief overview of the most important changes, see Configuring Cosmos React.
Collecting and displaying information
Users interact with your applications by using views, which comprise the interface of each assignment in the case life cycle and each data object. The forms that you can edit to collect user information, tables that display case data, and read-only tabs are all examples of views.
Cosmos React provides you with ready-to-use view templates that cover a many common UX layouts and scenarios. You can edit the views built on certain templates, which enables you to use them to gather user data, while other templates are read-only and are meant for displaying only data that is already in the system. You can reuse most views to improve consistency, and you can make editable views read-only in a different context.
You can find the views associated with your case type or object on the User Interface tab.
The view list on the left side of the tab includes all views in the case, including views that the application does not use currently and views that the application creates automatically, for example, full case views.
You use the central Edit pane to configure the content of your view. The Preview presents an image of what your view might look like in context.
Types of views
The Cosmos React framework includes the following types of views
on the views pane: By default, the system sets
Details and
Summary views as tabs on the full
view page. View Description Editability Configuration Full view The main interface where 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 Configuring a full view Case view (for case types) and
object view (for data
objects) A view that you create for a specific case or object. These
views include custom views that you create during application
development and default views that the application creates,
namely the Details,
Preview, and
Summary views. When enabled, the
Confirmation view also appears in the
case views list. Read-only Configuring case and object views List A view that relies on a data source. Depending on the
configuration, the system can display lists as tables or
tile-based galleries. By default, every case includes a list
that contains open cases. Data objects do not use list
views. Editable and read-only Configuring list views Form A view that the user interacts with when working on the case.
The system creates a from view for each step in the workflow
when you click Configure view on the Workflow tab.
The Create and
Edit views, which appear
automatically in the Form list, represent the opening form of
your application and the form that is connected to the edit
button in the case header respectively. 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 Configuring forms
Populating views with content
You can populate views with UI elements, such as text fields, checkboxes, lists, and other views. You can reuse the same fields in different views and contexts and configure their behavior to meet your business needs. For more information, see Configuring fields.
Depending on whether your view is editable or read-only, the same field, or the same reused view, might look differently.
On the other hand, the same Mortgage type view can be
iin a read-only context. In this case, the view is in the
Details tab of the case.
The application displays the same fields as read-only.
- Creating views in Cosmos React
Create personalized views for your cases and data objects to capture and display the information that your users need. By creating a view, you can lower application development time and costs because you can reuse views for multiple contexts.
- Configuring views
When users interact with your application, the interface they see is composed of views. Views hold UI components, such as fields, widgets, and other views, and organize them by using out-of-the-box layouts that match common interface scenarios. By configuring a view, you decide which template to use, and what kind of content to display in your view.
- Configuring fields
Fields model data in your application UI and define what information you need to provide to reach your business goals.
Previous topic Previewing a portal Next topic Creating views in Cosmos React