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.

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.

Low-code authoring of case pages

Valid from Pega Version 8.6

Mobile authoring for Cosmos React applications now supports the configuration of native mobile pages that include case details. Your mobile channel automatically generates these pages for each case type in your application. This enhancement improves the user experience in your app by providing users with native pages that you can adjust to best suit your business process. For example, you can highlight specific views on a page by modifying which tabs appear on the page, or add a floating action button to help your users edit the case.

For more information, see Authoring mobile case pages for Cosmos React applications.

In Pega Platform™ version 8.6, mobile features in Cosmos React applications are available only as a preview, with limited support for various interface elements and features, such as offline mode. The recommended production design system for Pega Mobile in Pega Platform 8.6 is Theme Cosmos.

For more information about the Cosmos React design system, see Cosmos React and UI architecture comparison.

No support for Android versions earlier than 4.4 on mobile devices

Valid from Pega Version 7.3

Pega® Platform dynamic layouts by default now use Flexbox-based rendering. As a result, mobile devices running on Android versions earlier than 4.4 are not supported in Pega Platform. Such devices cannot render correctly with Flexbox because the Pega Mobile Client includes the default stock browser on the Android operating system.

Debugging data synchronization issues with offline-enabled applications

Valid from Pega Version 7.2.1

If an offline-enabled mobile application that originates from the Pega 7 Platform fails to synchronize data after reconnecting to the server, the Pega 7 Platform generates a PEGA0066 alert. The alert includes detailed information about the failure, such as the activity that preceded the event, entries collected from the native application, and entries from the JavaScript part of the Pega 7 Platform application. The administrator can use the alert and device logs to facilitate error analysis and debugging without having to access the failing device.

For more information, see Understanding the PEGA0066 alert - Mobile App Data-Sync Failure.

New ClientStore JavaScript API for offline-enabled applications

Valid from Pega Version 8.3

For offline-enabled applications built using Pega Infinity Mobile Client™, you can now take advantage of a new window.pms.plugins.clientstore JavaScript API. The improved API is based on promises and events instead of callbacks and listeners, and replaces the previously available window.launchbox.PRPC.ClientStore JavaScript API which is now deprecated.

The worklist appears to be empty when you go back from an opened case in an offline-enabled mobile application

Valid from Pega Version 7.4

In a Pega® Platform offline-enabled application, when you go back to the worklist from an opened case, the worklist appears to be empty even though it contains cases. This issue will be fixed in the next release of Pega Platform. Only portals that use the key principles and design of the pyCaseWorker portal are supported in offline-enabled applications.

For more information, see Offline mobility guidelines.

Touch response supported on mobile devices

Valid from Pega Version 7.4

When displayed on a mobile device, all active elements of the Pega® Platform user interface now respond to touch by changing their appearance. No additional configuration is available or necessary.

Searching for Pulse messages available in spaces

Valid from Pega Version 8.5

Pega Platform™ now supports searching for Pulse messages within a space. For greater accuracy of the results, you can search by applying different filters, such as keywords, message authors, and a time range for posting of the messages. The results return private and public posts, comments, and attachments that match the search filters. When the result is a comment, Pulse displays the whole message thread for full context.

For more information, see Search for Pulse messages in spaces (8.5), Searching for Pulse messages in spaces.

Push notification delivery to multiple devices

Valid from Pega Version 7.2.1

Push notifications sent from the Pega 7 Platform are now delivered to all devices on which a user is logged in to your custom mobile app, regardless of the device platform. You can either send push notifications from the Push Console to all users who have your application installed on their devices, or configure your application to send push notifications to indicate that an action might be required, a status update is available, or a case was approved.

Consistent search experience in App Studio

Valid from Pega Version 8.5

Pega Platform™ now supports a unified search mechanism in App Studio. Instead of manually locating a single item, such as a case type, a channel, or a data object, you can simply use the Search option in the navigation pane. You can also use Search in case types and personas landing pages, to conveniently access the information that you need, for example channels and case types associated with a persona.  

For more information, see Plan your Microjourneys more conveniently in an improved Case Designer (8.5)Creating a Microjourney for customer success.

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