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.

Child case queries can be slow after upgrade

Valid from Pega Version 7.2.1

After upgrading, performance might be slow when you run queries on child cases for work tables that existed prior to the upgrade. This issue is often indicated by PEGA0005 (query time exceeded limit) alerts that can be correlated to these queries in the logs. To resolve the issue, add a database index to each of your work tables by using a multicolumn index on the pxCoverInsKey, pxObjClass, and pyStatusWork columns.

For more information, see Performance improvements for child case queries.

Immediate drain available for the quiesce process when using high availability

Valid from Pega Version 7.2.1

The quiesce process, which is used to take a server out of service for maintenance in a highly available system, can now be modified to use the immediate drain method. When using the default slow drain method for quiesce, users are placed in a passivation queue. When using the immediate drain method, users can continue to access the node being quiesced until it is removed from the load balancer.

Organizations should determine which quiesce method to use based on the overall needs of their users. However, for applications that have implemented long poll requests, it is recommended to use the slow drain method.

For more information, see the Pega 7.2.1 High Availability Administration Guide.

Improved mobile user experience with spaces

Valid from Pega Version 8.3

Spaces in mobile apps have been enhanced to provide a wider screen area for navigation between content tabs such as Pulse, Boards, Subspaces, and Tasks. Mobile users can now use native selection controls to choose from the same space-specific actions that are available to users of desktop-based applications. The enhancement improves the usability of spaces and promotes collaboration between mobile users.

Spaces on mobile apps do not require any additional configuration.

For more information about spaces, see Collaborating with users by using spaces.

Usability improvements to Admin Studio

Valid from Pega Version 8.3

Admin Studio offers a variety of usability enhancements, including:

  • New access groups to differentiate between full and read-only access to Admin Studio
  • A Java class lookup utility
  • A requestor list for the logged-on operator
  • The ability to display system node type in the logs

Also, if your environment uses Predictive Diagnostic Cloud (PDC), the Admin Studio overview page now includes a link to PDC.

For more information, see Managing requestors.

Improvements for automated scenario testing

Valid from Pega Version 8.3

Test automation authors can group related scenario tests into suites. The scenario test suites can be run manually from the Scenario Testing landing page as part of purpose-specific tests such as smoke tests, regression tests, and outcome-based tests. Additionally, automation authors or release managers who monitor tests for an application can disable or quarantine unstable scenario tests so that they do not run.

For more information about creating and managing test suites for scenario testing, see Creating test suites for scenario testing.

Data migration enhancements

Valid from Pega Version 8.3

Ensure a successful data migration by using a configuration template for setting up your environment before you migrate data into your application. From the new Migration settings landing page, configure dynamic system settings for migration and turn off database indexes and processes that might affect data migration performance. After you have finished migrating data, you can revert your system to its normal working state.

For more information, see Creating a migration configuration template.

Indicate download size in offline-enabled mobile apps for iOS

Valid from Pega Version 8.3

When you publish a client-based mobile app in the Apple App Store that needs to download additional resources before it starts, the app must indicate the size of the download and obtain user consent. To comply with this requirement, you can now build offline-enabled mobile apps that prompt the user before they perform the initial data synchronization. If the user chooses not to download data, the application closes.

For more information about disclosing the data size and how the data size is calculated, see Defining advanced offline configuration for an access group.

Improved management of batch indexing

Valid from Pega Version 8.3

You can now cancel and check the status of a batch index process directly from the Search landing page in Dev Studio. The landing page now refreshes automatically every 10 seconds so that you can easily see the most recent status of the batch index process. Additionally, the reindex operation is now 20% faster than in previous versions. These features provide greater visibility into batch indexing and improve your ability to fix issues with a batch indexing process.

For more information about batch indexing, see Rebuilding search indexes from the user interface.

.

New capabilities of the rich text editor

Valid from Pega Version 8.3

The enhanced rich text editor has a new plug-in that helps the users skip a few configuration screens by uploading image files directly from the file system. When they copy and paste content from a word processor or a spreadsheet, the text retains the original formatting. The developers can now configure all toolbar options, such as bulleting or font formatting, so the users can focus only on the tools that they need and work more efficiently.

For more information, see Selecting the property for a Rich text editor control.

Test coverage support for more rule types

Valid from Pega Version 8.3

Test coverage has been expanded to include the following rule types. Test coverage support for these rule types enables developers to more accurately measure the effectiveness of their tests.

  • Collection
  • Declare trigger
  • Map value
  • Navigation 
  • Report definition
  • Scorecard

For more information about test coverage, see Test coverage.

Upgrade impact

The new rule types may impact the test coverage metrics for your applications. Due to the increased number of supported rules, the reported test coverage percentage will decrease.

What steps are required to update the application to be compatible with this change?

Run your coverage reports after upgrading to see the latest metrics.

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