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.

Personalize survey questions by reusing properties

Valid from Pega Version 8.2

Now you can create more dynamic and personalized surveys by incorporating answers to previous questions in subsequent questions. For example, you can ask users to provide their place of residence, and then reuse this data in the questions that follow. By using this feature, you create personalized surveys that are more engaging and more specific to users’ needs.

For more information, see Reusing answers in a question.

Improvements to the Email channel configuration and content analysis

Valid from Pega Version 8.2

To make the Intelligent Virtual Assistant™ (IVA) for Email more useful and easier to manage, you can track all the Email channel configuration changes that you or other operators make. The system now also detects defined entities and topics, not only in the contents of the email messages and its attached files, but also in the email subject field which improves the responsiveness of IVA to emails. You can map same text that appears in an email triage case to different entities. In previous versions of Pega Platform, only the email body was analyzed but with subject analysis, now the entire email is analyzed for topics and entities, including its salutation and signature.

For more information, see Tracking configuration changes in the Email channel and Enabling the analysis of subject field content during email triage.

Discuss documents more effectively by using collaboration feedback

Valid from Pega Version 8.2

Create meaningful documentation for a case by collaborating with other users of your portal, such as the Case Manager or Worker portal. The collaboration feedback features in Pega Platform™ provide options for you to add Pulse comments to a document by responding to a notification email, share documents as URLs, and download documents as PDF files for offline viewing and editing. Collaboration feedback is a convenient and fast way to add valuable content for your case.

For more information, see Adding content to a space (for App Studio), Adding content to a space (for Dev Studio).

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 large binary data item storage in Pega Client for Windows

Valid from Pega Version 8.2

Pega Client for Windows can now store and synchronize large binary data items and their corresponding actions from the action queue. As a result, offline-enabled application users can view, attach, and delete data files from within a case view, whether the Windows-based device is online or offline. To use this feature, enable offline case attachment support, which allows offline-enabled applications to synchronize case attachments between Pega Platform™ and the device.

For more information, see Attach content support in offline mode and Enabling offline case attachments support.

Merged test-coverage report improves overview of application quality

Valid from Pega Version 8.2

You can now merge multiple application-level test coverage reports from built-on apps into a single report. This single test-coverage report provides an overview of your application's quality, and eliminates the need to manually collate data from multiple reports.

For more information, see Generating a merged coverage report.

Manage access to the content in your spaces and cases

Valid from Pega Version 8.2

To more efficiently manage your content, you can grant access to documents only to specific space or case members in a portal that you use. Use this option to provide users with content that is tailored to their specific needs. Provide contextual and consistent documents for your users for more effective communication and case management.

Add content to cases and spaces from external repositories

Valid from Pega Version 8.2

Provide meaningful content for your cases and spaces faster by attaching files from third-party repositories. Pega Platform™ now supports sourcing documents from external repositories that you configure in your application. You do not need to download documents first, and then upload them to your case or space.

For more information, see Adding content to a space (for App Studio), Adding content to a space (for Dev Studio).

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.

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