Enjoyed this article? See more similar articles in Constellation 101 series. 

Special thanks to Marco Russo who co-created this article.

Why

Views in Pega Constellation are configurable interfaces that serve as the foundation for how users interact with cases and data. They are designed to present information in a way that is both intuitive and efficient for different user roles and scenarios. The Constellation design system includes the building of views and replaces sections found in the traditional UI.  

Purpose and Functionality

Constellation provides you with ready-to-use View templates that cover many common UX layouts and scenarios. 

Key Features

• You can edit the Views built on certain templates, which enables you to use them to gather user data
• Other templates provided 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.

Sections are replaced with Views

When creating assignment from Case Designer a flow action gets created and the section field remains empty, a View is created and assigned to created Flow action (with matching name)

Authorable types of Views in Constellation

Pega Constellation offers several types of views:

Autogenerated Views:

When you create a Data Object or a Case Type, Pega Platform™ generates the following out-of-the-box views:

• Full view
  The Full view is optimized for almost any case or business object, the three-panel layout accommodates a lot of information, much of which is available without scrolling or moving to other views. 
• Summary data view
  You configure the Summary data view to display the most critical data that users should understand as soon as they open the case. The fields that you map into the Primary fields region render inline from left to right, and their values render with a pronounced visual treatment. The fields that you map into the Secondary fields region stack vertically along the summary panel.
• Details view
  The Details view is a default, optional view that can render read-only case data, such as important fields, and other information.
• Create
  The Create view renders a form to capture the data that is necessary to create the case.
• Edit
  The Edit view renders a form when users click Edit. The view includes important fields to edit at any stage of the case.
• Preview
  The Preview offers a quick snapshot of an item's key information, enabling users to assess its relevance or status without navigating away from the current context.

Views created for Cases

• Views can be created by either using the Configure Views button when a step is selected in the Case Life Cycle or through the UX tab designer.
• Full page view (one for each Case Type/Data Object) is on the Full Page View tab, while other types are on the Other Views tab.
• The Pega Platform automatically generates a Form View for each step in a case that is a user assignment
• These views are named after their respective steps and are located in the form section on the Other Views tab.
• If a form view is created using the UX tab, it cannot be directly associated with a step but can be embedded in a task step's top-level form.

Views created for Data Objects

Views can be accessed and managed through the UX tab on the data object's menu, with full page views on the Full Page View tab and partial, list, and form views on the Other Views tab.

• Views can be constructed using fields from the data object and other related views, and they are read-only by default.
• When a data object is linked to a case type, all fields and views become accessible to that case type.
• Data Object views can also be added/accessed view Landing Pages.

View authoring in App and Dev Studio

• Access to the UX tab is available in both App Studio and Dev Studio
• The recommended approach is to utilize App Studio to leverage its low-code capabilities
• Switch to Dev Studio only when advanced configurations are required
• Ensure that any changes made in Dev Studio are compliant with App Studio requirements

Configuring Constellation Views:

Naming of Views

When creating a View from a Step in Case Designer, name the step first and then click Configure View; otherwise, the system will auto-generate a name for a view.

Work views

• Top level views connected to steps - Name them the same as the flow action or stage to help organize what they belong to
• Views to be embedded - Embedded views should follow naming convention as <Parent view name> - <child view name> unless they are used globally

Data views - allowed to be embedded

Best Practices

Design Approach

• • Use out-of-the-box Constellation templates before creating custom solutions
  • Focus on configuration over customization
  • Define clear business outcomes for each view
  • Follow the Constellation design system guidelines consistently

References

• Configuring Views
• Working with Views