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.

All search data is encrypted

Valid from Pega Version 8.2

All search data in Pega Cloud deployments is now encrypted, both at rest and in transit. The encryption of search data makes search compliant with regulatory requirements.

For more information about search, see Full-text search.

Authentication service for basic credentials

Valid from Pega Version 8.2

A new type of authentication service is available for authenticating operators by using basic credentials (user ID and password). The default Pega Platform™ login is now an instance of this type of authentication service. All basic credentials authentication services include mobile authentication with the OAuth 2.0 protocol and Proof Key for Code Exchange (PKCE). You no longer have to create a custom authentication service to support mobile applications.

For more information, see Configuring a basic authentication service.

Unauthenticated sessions transition seamlessly to authenticated

Valid from Pega Version 8.2

A new authentication service type allows a guest user to use an application without logging in, and to be prompted to authenticate later in the session. This enhancement supports scenarios such as online shopping portals where a user can browse for items and load a shopping cart as a guest but be prompted for credentials at checkout.

For more information, see Configuring an anonymous authentication service.

Create single sign-on authentication services from App Studio

Valid from Pega Version 8.2

You can create and enable single sign-on (SSO) authentication services from a new landing page in App Studio. From this new landing page you can also configure new SAML and OpenID Connect authentication services to provision users. For more information, see Creating a SAML SSO authentication service and Creating an OIDC SSO authentication service.

Protect against insecure deserialization

Valid from Pega Version 8.2

Deserialization is the process of rebuilding a data stream into a Java object. The Open Web Application Security Project (OWASP) has identified insecure deserialization as one of the top 10 security vulnerabilities for web applications. Pega Platform™ protects against this vulnerability by using filters that prevent deserialization of suspect data streams. You can configure these filters from the Deserialization Blacklist landing page.

For more information, see Configuring the deserialization filter.

Changes to the Attach Content control in Pega Client for Windows

Valid from Pega Version 8.2

Users who access offline-enabled Pega Platform™ applications from Pega Client for Windows can now use the Attach Content control within a case view to attach files with a native file picker control or take screenshots with a device camera. Images are immediately attached to the case, and image file names are based on a time stamp. If a device has no camera, the client skips the source selection step and the native file picker control opens.

For more information, see Harness and Sections forms – Adding an Attach Content control.

Support for Firebase Cloud Messaging (FCM) push notifications in Android custom mobile apps

Valid from Pega Version 8.2

You can now create Android custom mobile apps that use push notifications with the Firebase Cloud Messaging (FCM) services. The push notifications for Android custom mobile apps based on legacy Google Cloud Messaging (GCM) are deprecated, as GCM services will be officially removed from use on April 11, 2019. To continue to use push notifications, you must migrate your custom mobile apps to FCM services. Before building your custom mobile app, you must register your Android app for push notifications in the Firebase console, obtain the FCM server key and Google Services JSON file, and use the key and file in the Android certificate set to build the custom mobile app.

For more information, see Migrating Android custom mobile apps that use push notifications to Firebase Cloud Messaging, Push notifications in Android mobile app, and Android certificate set.

Manage test ID access with an access group role

Valid from Pega Version 8.2

Test IDs for user interface components are available only to users who have the PegaRULES:TestID role added to their access group. This requirement allows administrators to limit access to test IDs to users who create or run tests. At run time, applications do not include the test ID data for users without the PegaRULES:TestID role, which reduces the amount of code that is downloaded to the client.

For more information see Managing Test ID access with an access group role

PEGA0107 alert enables performance monitoring of offline-enabled apps

Valid from Pega Version 8.2

You can now monitor the performance of offline-enabled apps by analyzing PEGA0107 alerts from Pega Predictive Diagnostic Cloud™. PEGA0107 alerts are equivalent to PEGA0069 alerts in the context of offline-enabled applications, but PEGA0069 alerts are not generated for offline-enabled applications.

For more information, see PEGA0107 alert: Client page load time for offline-enabled applications and Pega Predictive Diagnostic Cloud Improvement Plan overview.

Text file rules support the Google Closure Compiler

Valid from Pega Version 8.2

Text file rules support Google Closure Compiler as the default option for minification of JavaScript code. Minification reduces the size of JavaScript in text file rules for faster download. Access the Closure Compiler by selecting it in the Minification menu in a text file rule. For more information, see Text File rules - Completing the Main tab.

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