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.

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.

More visibility of your production level

Valid from Pega Version 8.2

You can now see the production level of your environment in a new gadget that is available in all Pega Platform™ workspaces. To ensure that you immediately recognize your current environment, you can give it a unique name that is displayed when you click the gadget. In addition to specifying your production level and environment name on the System form in Dev Studio, you can now specify those values on the System & nodes page in Admin Studio.

For more information on Admin Studio, see Modifying your environment name and production level.

For more information on Dev Studio, see Specifying the production level.

Facebook and Web Chatbot configuration in the preview console

Valid from Pega Version 8.2

When you develop a Pega Intelligent Virtual Assistant™ (IVA) for Facebook or Web Chatbot, you can now teach interactive bot conversations by chatting with the bot in the preview console and guiding the artificial intelligence algorithm to the right responses. This ability greatly accelerates conversation development and simplifies configuration, while providing the developer with more transparency in the mechanisms that produce specific responses.

For more information, see Simulating a conversation and building a chatbot runtime and Testing and building a chatbot from the preview console.

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

Visualize application layers for case processes and sections

Valid from Pega Version 8.2

In App Studio, you can now easily visualize the application layers for case processes and sections, including work areas and views. When you click the Discover gadget for a case process or section, you are shown a visual representation of the application layers. You can open a layer in Dev Studio to see the rulesets and other attributes of an application.

For more information, see Discover gadget.

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.

Improved clipboard performance for editable data pages

Valid from Pega Version 8.2

Improve clipboard performance for editable data page processing by using the new high-throughput mode option. This mode does not support all clipboard features.

For a list of supported and unsupported features, see Data page rules - Using the Definition tab.

More display options for charts

Valid from Pega Version 8.2

Display properties have been expanded for charts that you add to a report harness or section. In addition to setting general display properties, you can set visibility and color options, control hover highlight behavior for data points and legends, and define more presentation options for grids and tooltips. The additional presentation options enhance your chart design and provide a way for you to effectively highlight important data.

For more information about configuring charts, see Harness and section forms - Adding a chart.

Better navigation between pages

Valid from Pega Version 8.2

The navigation between landing pages and configuration pages in App Studio has changed so that only one tab at a time is displayed in the work area. This change eliminates the maximum tab limit message. Navigate to previous pages by clicking the back arrow at the top of the work area or click the Back to preview button in the workspace header to open a page in the selected device preview.

Reuse when conditions when designing cases in App Studio

Valid from Pega Version 8.2

Reuse existing conditions to save time when you design a case in App Studio. Now you can use an existing when condition when you create a condition for a stage in your workflow. You can also define custom when conditions and save them for future use.

For more information, see Defining conditions with a condition builder.

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