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.

Reporting

Valid from Pega Version 7.1.3

This release had a focus on extending key capabilities to improve the functionality and ease of use of reporting features based on early adopter feedback.  A series of cosmetic changes and fixes are also included.

  • Multiple boxes may be checked on List view checkboxes
  • Dashboard Charts slider has been improved.
  • Summary View reports and charts have been enhanced.
  • Column properties can be added to a report in the Report Editor.
  • List view column widths can be set by Smart Info.
  • Listviews will display correctly for updated systems.
  • Improvements to the GuardRail Report.

Use "alternate database" as report source

Valid from Pega Version 7.1.6

You can opt to use the the "alternate database" identified in the Reports Database field of the Data-Admin-DB-Table instance that supports the Applies To class of a report as the source for the report. This reduces the load on the database that serves your application when you run the report.

View status of custom search indexes

Valid from Pega Version 8.1

Custom search indexes are special purpose indexes that are created and managed outside of Pega Platform™. You can view the status of custom search indexes on the Search landing page to see whether they are complete. This information is useful for troubleshooting and can help you determine whether to rebuild the index.

For more information, see Checking search index status.

Support for multiple custom mobile apps for a Pega Platform application

Valid from Pega Version 8.1

To enhance the user experience and provide support for native mobile components, you can create multiple custom mobile apps for a Pega Platform™ application. For each custom mobile app, you must create a different mobile channel interface. In addition, you can configure each custom mobile app to run only in a specific portal for an application. The custom mobile app uses this portal regardless of which default portal is defined for the access group.

For more information, see Selecting a portal for a custom mobile app.

Ability to generate a dedicated search index for a case type

Valid from Pega Version 8.1

You can generate a dedicated search index for a case type. Using a dedicated index makes reporting faster without putting additional requirements on the database. 

For more information, see Including indexed data during case search.

Changes in large data page support in offline-enabled custom mobile apps

Valid from Pega Version 8.1

You can now create offline-enabled custom mobile apps that store reference data in large data pages that are sourced from report definitions, even if these report definitions return no records. Synchronization of these custom mobile apps does not fail. Also, you can now use page type properties as large data page properties.

For more information, see Creating and sourcing large data pages to store large reference data in offline-enabled applications and Custom populator JavaScript functions for large data pages.

Troubleshooting offline-enabled applications in a browser

Valid from Pega Version 8.1

You can now troubleshoot offline-enabled applications by using the Tracer tool and developer tools that are available in a web browser. You can troubleshoot scripts that are running when the application is running, without having to use additional debugging tools.

For more information, see Application debugging using the Tracer tool, Troubleshooting offline-enabled applications with the Tracer tool in a browser, and Offline capability.

Support for native search in custom mobile apps

Valid from Pega Version 8.1

To improve the overall user experience in a custom mobile app, you can configure native search in the user interface of the application. To use the search capability, first configure the pySearchConfiguration rule. This rule allows you to optionally define a set of search categories as a local data source. You then configure the mobile search action for any user interface control, for example, a button in a section. Users can tap the search field to see the most recent search results, including results that are grouped by categories, as they enter search text.

For more information, see Native search capability in custom mobile apps and Configuring search in custom mobile apps.

Enhanced Pulse performance and layout on mobile devices

Valid from Pega Version 8.1

Pulse performance is now faster on mobile devices. The user interface has been enhanced to enable better collaboration among users. The new Pulse mobile layout provides a better user experience for posting messages, adding attachments, bookmarking content, and so on.

For more information about Pulse, see:

Support for when rule in offline-enabled applications

Valid from Pega Version 8.1

You can use when rules in offline-enabled applications without creating custom JavaScript code. Using when rules reduces the offline-enabled application implementation time by further automating case processing in offline mode and deriving the logic directly from the model. No additional configuration is required to use when rules in offline mode.

For more information, see When rule support in offline mode.

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