Section-based applications feature a consistent and familiar UI that helps your business build a strong presence across technologies and channels. By relying on ready-to-use templates, patterns, and themes, this architecture helps you reduce development effort and focus on the needs of your business.
In the 8.7 version of the Pega Platform, Theme Cosmos is the recommended architecture for new section-based applications. Theme Cosmos applications use the Cosmos library of UI components by default. For more information, see Theme Cosmos.
More accessible column headers in tables
Column headers in tables now feature an improved experience for users who rely on a keyboard for navigation. For example, the redesign of the column header now limits action items to just one. In addition, keyboard users can now use the Actions menu for all column operations instead of tabbing through column headings, which makes navigation and operations, such as sorting, more convenient.
These updates improve the accessibility of Pega Platform for users with different levels of ability.
Customizable error messages
Pega Platform now includes an out-of-the-box error stream rule pyStatusResponse, which you can modify to adjust the messaging and appearance of error messages. Previously, similar customizations affected deployment files, which adversely impacted application updates. Now, you can safely control the text, style sheet, and visuals in your errors messages to better align with your company policy and branding. With this change, make sure you migrate all existing error message customizations to the new rule.
For more information, see Customizing error messages.
Handlebars library update
Pega Platform now uses the 4.7.7 version of the Handlebars template to generate client-side template files. The updated version, which is the latest available, introduces a wide variety of security fixes and new features that improve application reliability.
Improved confirmation modal dialog boxes
Confirmation modal dialog boxes (dirty forms) now support native web browser configuration to avoid potential issues with the default save option. Previously, when a user attempted to abandon unsaved work by triggering a local action, the default confirmation box appeared, but the save option might not have worked as intended.
For more information, see Configuring confirmation modal dialog boxes.