Skip to main content
circle-square
Outline Circle
square-square
Little Circle
square-square
Little Circle

Published Release Notes

Find release notes for the selected Pega Version and Capability.

Browse resolved issues for Platform releases.

Gadget configuration by using IAC gateway console is no longer supported

Valid from Pega Version 7.2.1

The Internet Application Composer (IAC) gateway was deprecated in Pega Platform™ 7.2.1 and is no longer supported. The IAC was used to embed a Pega Platform application, such as a gadget, on the pages of a web application that was located on your intranet, extranet, or internet site.

Upgrade impact

After an upgrade to Pega Platform 8.5, the configuration of gadgets through the IAC gateway console is no longer supported.

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

To make subsequent changes to your current web mashup, use Pega Web Mashup. 

For more information, see Tutorial: Creating a mashup with Pega Web Mashup.

Default value of the threadpoolsize agent affects batch indexing

Valid from Pega Version 8.5.2

After you patch Pega Platform to version 8.5.2 or higher, the system changes the default value of the threadpoolsize agent, which controls the number of concurrent activities (threads) in the system, from 5 to 15. Batch indexing in Pega Platform does not require all 15 threads, so you can change the agent value to increase system performance by managing the indexing/distributed/batch/numworkers dynamic system setting.
If your deployment does not support that setting, and batch indexing does not use Queue Processors, the system uses the threadpoolsize value for batch indexing instead.

For more information, see Editing a dynamic system setting.

Data page unit test case setup and cleanup

Valid from Pega Version 7.2.1

You can now use one or more data pages, data transforms, or activities to set up a clipboard page with the appropriate properties before you run a data page unit test case. You can also use activities to create any required test data, such as work or data objects.

After you run a data page unit test case, the data pages that were used to set up the test environment are automatically removed. You can now also apply additional data transforms or activities to clean up the clipboard.

For more information, see Setup and cleanup of data page unit test cases.

New assertions for data page unit test cases

Valid from Pega Version 7.2.1

You can now configure the following assertions for data page unit test cases:

  • Result count assertions for page lists, page groups, value lists, and value groups
  • Unordered list and ordered list assertions for page lists

The Pega 7 Platform now supports these assertions in addition to expected run-time assertions for the data page and property assertions for any property type.

For more information, see Data page unit test case assertions.

End of support for Microsoft Internet Explorer 9 in Pega 7.2.1

Valid from Pega Version 7.2.1

In accordance with Microsoft’s announcement to discontinue support for Internet Explorer 9, Pega 7.2.1 will not support Internet Explorer 9. You should not upgrade to Pega 7.2.1 if you are still using Internet Explorer 9. Otherwise, upgrade to Microsoft Internet Explorer 10 or later, or use Google Chrome, Apple Safari, or Mozilla Firefox, which support certain HTML5 and CSS3 standards not supported in Internet Explorer 9.

For more information about browser support, see the Platform Support Guide or contact Pegasystems Global Customer Support.

 

 

 

New options to manage proposition validity

Valid from Pega Version 7.2.1

Manage your decisioning strategy more effectively with proposition validity settings. You can now set your propositions as always active, inactive, or active only within a defined time period. Setting a validity period for your propositions helps you to plan your strategy and automatically activate or deactivate propositions in the future.

For more information, see Proposition validity.

Ability to import data into a Pega Cloud database

Valid from Pega Version 7.2.1

You can export a custom Pega 7 Platform database table into a CSV file and import it into a Pega Cloud database or other Pega 7 Platform database by using the Data Upload utility. This utility is available only for Postgres databases and tables that do not contain BLOB columns. This utility is useful, for example, for updating a product catalog that is used in a Pega Cloud application.

For more information, see Importing data into a Pega Cloud database.

Ability to schedule schema updates for Pega Cloud

Valid from Pega Version 7.2.1

You can schedule BLOB size and table statistic updates to database schemas to run automatically by using agents. Scheduling schema updates is useful for performance monitoring and tuning in the Pega Cloud. This feature is available only for customers who use a Postgres database.

There is an agent for updating the average and maximum BLOB sizes, and an agent for updating table statistics. Each agent can be configured separately for each schema. You can configure whether to schedule the agent to run daily or weekly. You can deactivate a running schedule on the Schema Tools landing page by clicking Designer Studio > System > Database > Schema Tools. From the Schema Tools landing page, you can configure more complex scheduling on the Edit Agent Schedule landing page. In addition, you can configure these agents by using Dynamic Data System Settings.

For more information, see Scheduling schema updates.

BIX performance improvements for CSV output in the Pega Cloud

Valid from Pega Version 7.2.1

BIX performance has been enhanced to download up to 25 GB of data per hour for extracts from a BLOB-less class table for CSV output. This high-throughput option is available only for Pega Cloud instances that use a Postgres database. This option is used automatically for these types of extracts.

When this option is used, the –x and –c command-line options for BIX are not supported, and the checkSum field in the manifest summary is not populated. If you need these options, you can revert to the previous implementation by using a setting in the prconfig.xml file.

For more information, see BIX high-throughput data downloads in the Pega Cloud.

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.

All Pega product release notes can be found on their product pages.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us