Support for React-based components in Pega Infinity applications
Valid from Pega Version 8.5
React-based components can now conveniently be enabled in any existing Pega Infinity™ application without the need to migrate the application to the full React UI. By selecting a single option, you can enable and experience some of the most modern functionalities, such as intuitive and comfortable landing page authoring, or the more efficient React-based tables.
For more information, see Enabling Cosmos React UI for landing pages.
Better support for custom PDF fonts
Valid from Pega Version 8.5
Pega Platform™ now supports loading custom fonts for PDF files from a binary file by using the CSS @font-face rule. With this enhancement, your application can generate PDF files that use custom fonts without relying on a dedicated font folder or a cloud bundle. As Pega moves away from folder-based solutions, you can migrate font management to a binary rule for quicker development and improved maintenance.
For more information, see Generating PDFs from your UI.
PegaWAI ruleset deprecated in 8.5
Valid from Pega Version 8.5
Accessibility functions that were contained in the PegaWAI ruleset are now integrated into the main Pega Platform™. Consequently, the user interface in your applications now features accessibility functions out of the box, so you no longer need to use the PegaWAI ruleset to ensure accessible behavior in your application.
For more information, see Building an accessible UI.
Tags disappear from Rich Text Editor source mode
Valid from Pega Version 8.5
When you use Rich Text Editor in HTML source mode, some tags disappear from the markup, which causes backward compatibility issues and data loss.
Cause
Pega Platform™ version 8.5.5 introduced the DOM Purifier security plugin. The plugin removes potentially vulnerable tags, including custom tags, from the raw HTML code in the Rich Text Editor source mode.
Workaround
You can disable the DOM Purifier plugin by adding the the window.disableDomPurifier = true markup to the userWorkForm HTML fragment rule.
Alternatively, as of Pega Platform version 8.5.6, you can add a tag to the allow list by including the window.rteCustomAllowedTags = ['myCustomTag'] snippet in the userWorkForm HTML fragment rule.
In Pega Platform versions 8.5.6 to 8.6, the iframe tag is added to the allow list by default.
Build consistent, high-quality sections with design templates
Valid from Pega Version 7.2.2
The Pega 7 Platform provides predefined design templates that you can apply to your sections. Templates eliminate the need to design or copy another layout each time you want to design a section. You also can create custom design templates that can be shared with other users. Custom templates can contain regions (dynamic layouts) that you can further customize for each section.
For more information, see Designing sections by using design templates.
Improved scrollable layouts in a new harness
Valid from Pega Version 7.2.2
By default, you can now create a new harness with a screen layout instead of as a container with a cell structure. This change ensures that you can create an application layout more efficiently; for example, you can specify a scroll area exactly the way you want in a desktop application or a mobile app. You can arrange the header, footer, and main area content at the new harness level by using sections. For example, you can specify headers and footers to be fixed or to scroll with the page. New layout options are configurable in the skin. Different layout selections are available when you use the harness as an app view, a main area, inner harness, or a page view.
For more information, see Configuring a screen layout.
New formats for styling report data grids
Valid from Pega Version 7.2.2
When you view a report, the data grid that is displayed is now styled by using either the List report format or the Summarized report format, depending on the report type. With this enhancement, you can display report data differently, and perhaps more effectively, than other grids in your portal. In the skin of your application, these new formats will be added and upgraded automatically by copying the Default format for the Trees & grids layout type, which was previously used to style reports.
For more information, see Modifying data grid formats for reports.
Limited action set for mobile-optimized grid layouts
Valid from Pega Version 7.2.2
The grid layout supports a limited action set when you select the Optimize for mobile mode. Actions allow you to determine the behavior of the grid. When Optimize for mobile is selected on the General tab of the grid layout properties, the following actions are available on the Actions tab:
- Set focus
- Open work by handle
- Open assignment
- Edit item
For more information, see Optimize repeating grid layouts for mobile.
Grid layout supports heading level
Valid from Pega Version 7.2.2
The grid layout supports the addition of a heading level. The heading level generates semantic markup and makes the UI structurally understandable for assistive technology users. The heading level is selected in the Presentation tab of the grid layout properties.
For more information see Grid layout - Presentation tab.
Include videos within sections
Valid from Pega Version 7.2.2
You can include videos within sections to build an interactive user experience. As with other standard controls, you can configure the video presentation and event properties. Although the Pega 7 Platform supports multiple video types, use the MP4 format as a best practice.
For more information, see Adding a video to a section.