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.

Show multiple views of data in your application

Valid from Pega Version 7.2.2

You can now show multiple views of data in your application by adding the record editor (pxRecordsEditor) section to a layout, another section, or a cell in a layout. You can configure the section to customize the display and enable the search, import, and export capabilities of the record editor.

For more information, see Multiple views of data in the record editor section.

Support for additional rule types for PegaUnit test cases

Valid from Pega Version 7.2.2

To compare the expected results with the results that are returned by running a rule, you can now create PegaUnit test cases for the following rule types:

  • Activities
  • Data transforms
  • Strategies
  • Decision trees
  • Decision tables

After you unit test these rules, you can convert them to test cases and configure assertions on the test cases. You can also set up the clipboard with data before tests are run, and clean up the clipboard after tests are run.

For more information, see PegaUnit testing.

Page assertions are supported for PegaUnit test cases

Valid from Pega Version 7.2.2

You can now create page assertions for PegaUnit test cases. Because data transforms and activities can create or remove pages, you can configure page assertions to determine whether a page exists after you run PegaUnit test cases.

For more information, see Configuring page assertions.

Authenticate REST data sources by using OAuth 2.0

Valid from Pega Version 7.2.2

You can now authenticate the data sources that are created from your REST integration by configuring OAuth 2.0 authentication in the New REST Integration wizard. You can specify or create an OAuth 2.0 authentication profile in the wizard by using the client credentials or authorization code grant type.

For more information, see OAuth 2.0 in REST integration.

More efficient load management strategies for large data pages

Valid from Pega Version 7.2.2

The processing of large data pages on the Pega 7 Platform server during the packaging of offline apps is now faster and much more memory-efficient, especially in environments with many concurrent users. Server communication with the data source is now also optimized by reducing the number of data transfers to only what is needed. In addition, all types of refresh strategies are supported for large data pages.

For more information, see Tutorial: How to use large data pages to store large reference data in offline mobile apps.

Customized data imports

Valid from Pega Version 7.2.2

You can now further customize the data import process in Data Designer by:

  • Setting a default import purpose and preventing the selection of an import purpose to speed up frequent imports of the same kind
  • Removing the import purposes that you do not need for your data type
  • Defining a default field mapping between the fields in the .csv file and the fields in your data type that act as a unique identifier (key), to save time during the import process
  • Skipping the import progress screen and showing progress contextually within your application
  • Including the link for data import anywhere in your application or calling it in the background from a service or agent

For more information, see Data import customization.

New Mobile Apps form for defining and building mobile apps

Valid from Pega Version 7.2.2

You now create and build mobile apps from the Mobile Apps form instead of from the Mobile tab of the Application rule form. The new console is a control center for mobile apps where you can gather applications, services, components, and settings in one place to fully customize your apps in the Pega 7 Platform. You can create and build one instance of a custom mobile app and define multiple native mobile apps that can use the Pega Mobile SDK. To push notifications to an Android or to an iOS device, you must define an SDK mobile app in the Pega 7 Platform with a certificate set that has push notifications enabled.

For more information, see Configuring a custom mobile app and Configuring push notifications for an SDK app.

Caching of common rules in offline mobile apps

Valid from Pega Version 7.2.2

To help start offline-enabled mobile apps more quickly from the time when the server was started, you can now cache common Pega 7 Platform rules, including node scope data pages. Optionally, you can also either cache all node scope data pages, with the exception of the selected ones, or cache only the node scope data pages that are explicitly specified. You set up the offline caching options for your custom mobile app in the Advanced tab of the Access Group rule form.

For more information, see the Offline Configuration section in Access Group form - Completing the Advanced tab.

Enhanced data imports

Valid from Pega Version 7.2.2

The data import process in Data Designer has been enhanced to give you more options. You can now import case types, save and use templates for field mapping, add data without updating existing data, specify date and time formats, and reprocess erroneous records by downloading a .csv file that lists the errors in your data import. You can also adjust the data import wizard to the context where it is included.

For more information, see Data import enhancements

Testing push notifications service connection and configuration

Valid from Pega Version 7.2.2

From the Push Notifications console, you can now quickly test the configuration of and connection to the push notifications services for both the Android and iOS platforms. Testing push notifications helps to eliminate issues that might occur when you are using a firewall or a secure connection (SSL) between the Pega 7 Platform and your mobile app. If any configuration, connection, or service test errors are generated, you can download and examine the contents of a log file to determine the cause of the error.

For more information, see Testing push notifications.

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