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

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

Why

Main purpose of Partial View is to display data in Read-Only mode. Partial Views for Cases and data objects include custom Views that you create during application development and default Views that the application creates automatically, such as the Details View.

Purpose and functionality

1. Read-Only Configuration

• Designed specifically for reviewing previously entered or referenced information
• Ensures data integrity through controlled access
• Maintains consistency across all view instances

2. Technical Capabilities

• Flexible configuration options for specific case types
• Seamless integration with Full Page Views
• Support for multiple data display formats
• Optimized performance through efficient data loading

3. Integration Features

• Can be embedded within other views for enhanced functionality
• Works harmoniously with Full Page Views
• Supports modular application design
• Enables consistent information display across different parts of the application

You can find forms in the UX tab of Case or Object, under Other Views.

To learn more about Partial Views, see the “Configure Partial View” section below.

Business use cases

1. Terms and Conditions Review

• Description: A read-only view displaying legal agreements or policy documents that users need to reference during case processing
• Business Value:
  • Ensures compliance by making critical legal information easily accessible
  • Reduces risk of errors by maintaining document integrity
  • Speeds up case resolution by providing instant access to relevant policies

2. Customer Profile Summary

• Description: A concise, read-only display of key customer information that can be embedded within other views
• Business Value:
  • Improves customer service by providing instant access to relevant customer details
  • Reduces errors by ensuring consistent customer information display
  • Increases efficiency by eliminating the need to switch between screens

4. Service Level Agreement (SLA) Status

• Description: A real-time, read-only view of current SLA metrics and commitments
• Business Value:
  • Ensures SLA compliance by making commitments visible
  • Improves customer satisfaction through consistent service delivery
  • Enables proactive management of service levels

Benefits

Partial Views are beneficial when:

• Modular Design
  • Enables breaking down complex UIs into smaller, manageable components
  • Facilitates better organization and maintenance of UI elements
• Reusability
  • Components can be included in multiple forms or views
  • Reduces redundant code and development effort
• Maintainability
  • Changes to a partial view automatically reflect everywhere it's used
  • Centralizes updates for consistent modifications
• Consistency
  • Ensures uniform display of information across different parts of the application
  • Maintains a cohesive user experience
• Performance
  • Enables an individual view (IE Partial Views) of a page to be refreshed without reloading the entire page. Allows for updating parts of a UI in response to user actions or data changes, thereby optimizing loading times and reducing server load.

Configure Partial View

Views Hierarchy

When embedding a Page-property from the Work-class Pega will generate a view in the data class with the name of the TopLevel_ view added as prefix
  

Tip: A Better way is to create the view directly in the target class, have a proper meaningful name and then reference this view from top level view

Build from Lowest Embedded Level

• View named Company Bank Details is created with proper naming conventions in mind on Account Data object that is referred by Account Data Reference field on given case type
• View is embedded from main case view (accessed via Data Reference field defined on case type)

You can find forms in the Views section of the User Interface tab.

Partial Views support the following functionalities:

• • Can change template
  • Possibility to provide heading (for whole view)
  • Can specify Highlighted Fields (described later)
     

To learn more about specific types of partial Views, see:

• • Configuring details Views
    • Build Case-wide UI modules by defining the form and content of a details View.
    • Configuring tabs Group fields together in your application by category with a tabbed View template. By using tabs, you can create an intuitive UI that saves screen space and helps users find the information they need with less effort.
• Configuring dynamic tabs
  • • Source your UI from data objects to keep your UI up to date with minimum effort. By linking a dynamic tab in your application to a data objects, you can ensure that the system automatically updates the UI to match any changes to the data.

• Configuring a confirmation View

• Help your users better understand the next steps in their work by configuring an out-of-the-box confirmation View.

Re-use View

Help users complete their work efficiently by configuring supplementary Views for Cases and data objects in the UX tab. For example, you can create a table that displays information about open work items and, when needed, reuse that View in different contexts throughout the application.              

See how to configure for reuse here: https://docs.pega.com/bundle/platform/page/platform/user-experience/creating-views.html 

Embedded Image

Tip: If you add URL field into Form and store in it URL to image it will always render in view image rather than link to it.

Setup helper text\tooltip for a field

 Instruction text can be configured as inline below the field as shown below:

Note: The configuration to add the tooltip as an overlay is available in Infinity 24.1. We can verify the configuration settings on this link - https://docs.pega.com/bundle/platform/page/platform/data-integration/adding-help-icon-field.html

This will be added as part of the data field and not as part of the view configuration. Hence there can be a challenge to move the existing helper text from Infinity 23 to Infinity 24.1.

Best practices

Design Considerations

• Keep Partial Views focused on a single, specific purpose
• Design for reusability across different contexts
• Ensure the view is self-contained with minimal external dependencies

Implementation Guidelines

• Use appropriate templates based on content type
• Configure proper visibility conditions for different channels (mobile, desktop, etc.)
• Implement proper error handling and loading states

Maintenance

• Document the purpose and usage of each Partial View
• Regularly review and update Partial Views to meet current requirements
• Test partial views thoroughly in all contexts where they are used

Summary

Partial Views in Pega Constellation provide a powerful approach to creating modular, reusable UI components. They help break down complex interfaces into manageable pieces while ensuring consistency across your application. Strategic implementation of partial views improves both development efficiency and user experience through reusable, maintainable UI components that can be easily updated and managed centrally.

References

1. Pega Platform Documentation: Configuring Partial Views
2. Working with Views in Pega Platform