Skip to main content

Published Release Notes

Find release notes for the selected Pega Version and Capability

Browse resolved issues for Platform releases.

This documentation is for non-current versions of Pega Platform. For current release notes, go here.

Tour IDs and Test IDs in UI controls

Valid from Pega Version 7.3

Many UI controls now support the Test ID and Tour ID fields in the General tab of the layout properties. The Test ID setting generates a data-test-id attribute to provide a fixed reference to a UI control for automated testing. You can use Tour IDs to create a guided tour of your user interface for users. For more information, see Test ID and Tour ID for unique identification of UI elements.

Test IDs and Tour IDs have been extended to the following UI controls.

Both Test IDs and Tour IDs are supported in the following types of controls:

  • Autocomplete
  • Button
  • Check box
  • Date time
  • Drop-down
  • Formatted text
  • Icon
  • Label
  • Link
  • Radio button
  • Text area
  • Text input

Test IDs are supported in the following controls:

  • Grid
  • Hidden text
  • Tree
  • Tree grid

Tour IDs are supported in:

  • Dynamic layouts

Security landing pages and features require privileges

Valid from Pega Version 7.3

Security-related landing pages and features are no longer visible and accessible to every user. To view and configure the following security features, you must have the appropriate privileges:

  • Attribute-based access control (ABAC) policies require the pzCanManageSecurityPolicies privilege.
  • The Authentication Services landing page requires the pzCanCreateAuthService privilege.

Authenticate users in processes with a JSON Web Token

Valid from Pega Version 7.3

You can generate and process a JSON Web Token (JWT) in Pega® Platform to secure communications in Pega Platform applications. JWTs are intended to securely transmit small amounts of information between two parties. Because the JWT is signed, the integrity of the information is assured. The contents of the JWT can be used to authenticate a user or to exchange information.

For more information, see Token Profile data instance.

Flexbox support for all default layouts

Valid from Pega Version 7.3

To improve scalability, Pega Platform supports flexbox-based layouts by default in all its screen and column layouts and layout groups. You can convert existing layouts to flexbox-based layouts by selecting the Optimized code option on the Presentation tab of the layout.

For more information, see Screen Layout Properties.

Portals can refresh a single page in a dynamic container

Valid from Pega Version 7.3

You can use a single-document dynamic container in a portal that allows you to refresh a single page in the container without reloading the entire portal, which improves performance and security. From the Properties panel, you can configure an existing dynamic container for this purpose by setting the mode to Single Document and selecting Render as a single page.

For more information, see Dynamic container settings.

Tab groups are deprecated

Valid from Pega Version 7.3

Beginning with Pega 7.3, tab groups have been replaced with layout groups, which offer better performance and flexibility. Tab groups are based on the Yahoo User Interface (YUI) library, which is no longer supported on the Pega 7 Platform.

User interface rule forms now use layout groups instead of tab groups to place layouts in forms.

For more information, see Adding a Layout Group.

Layout groups support icons and titles in headers

Valid from Pega Version 7.3

You can now include icons or cells to enhance the design of layout group headers. On the properties panel, select Include icon with title under Container settings to add icons and titles in the layout headers. Also, the layout group control can now refresh the content of a dynamic layout if the layout is active.

For more information, see Adding a Layout Group.

Property-level security for full-text search

Valid from Pega Version 7.3

Property-level security has been added to full-text search so that you can limit access to sensitive data. From the Search landing page, you can specify whether to include properties with access control policies in search results. In addition, for custom search, you can select which properties to include in full-text search by selecting options on the Search landing page and Custom Search properties instance.

For more information, see Specifying custom search properties and Excluding properties with access control policies from search results.

Add custom controls to section palettes

Valid from Pega Version 7.3

You can add custom controls to the Basic or Advanced palettes in sections. With this enhancement, Pega® Platform developers have easy access to custom controls. The Show in authoring menus check box is available in the HTML tab of the custom control rule. You can add a custom icon to display in the menu with the custom control.

For more information see Adding custom controls to the section palette in Designer Studio.

New service for generating OAuth 2.0 client credentials

Valid from Pega Version 7.3

Pega® Platform now includes the oauthclients service package that provides a REST service for generating OAuth 2.0 client credentials. By using the client registration service, you can dynamically register OAuth 2.0 clients. The new service is secured by an existing OAuth service. Access tokens that are issued by the existing OAuth service are accepted as initial access tokens by the new service.

For more information, see OAuth 2.0 Client Registration data instances.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us