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.

Legacy landing pages removed

Valid from Pega Version 7.3.1

The following legacy landing pages and their links in the Designer Studio menu have been removed:

  • Designer Studio > Data Model > Clipboard Pages > Data Pages
  • Designer Studio > Data Model > Clipboard Pages > Undefined Pages
  • Designer Studio > Data Model > Classes & Properties > Class Relationships

The streamlined Designer Studio menu facilitates locating and navigating to landing pages.

For information about the replacements for these landing pages, see Deprecated features.

Service REST monitoring

Valid from Pega Version 7.3.1

You can now monitor response and request data for REST services and view the results in Pega® Platform. The ability to monitor REST services is useful for debugging your application during development, for example, when a request fails. It is not recommended that you monitor REST services in production environments because monitoring might affect performance and depending on the number of incoming service requests, there is a chance that over a period of time, the invocation history might get large enough so that you run out of database space. You can configure monitoring globally for all of your REST services by using the service/EnableglobalMonitoring Dynamic System Setting with owning ruleset Pega-IntegrationEngine, or by using the service package and service rule forms.

For more information, see Service REST monitoring.

Project sizing supports real-time feedback

Valid from Pega Version 7.3.1

You can now size a project based on the stories that you create in the Agile Workbench tool. By capturing feedback from your stakeholders in stories, you can improve the accuracy of your estimated timeline and costs in real time.
For more information about project sizing, see Sizing an application development project.

Support for intelligent routing in the Email channel

Valid from Pega Version 7.3.1

When you create an Email channel interface to use as a Pega® Intelligent Virtual Assistant, you can now set up automatic routing of the received email content. You define routing rules so that the Email channel is more responsive and makes an informed decision about how to process the email content. The Pega Intelligent Virtual Assistant can automatically assign it to an operator, add it to a work queue, or create a top-level case. In addition, you can configure multiple email accounts to act as the same Pega Intelligent Virtual Assistant.

For more information, see Configuring routing conditions for automatic email handling.

Continue batch data flow runs that failed and reprocess partitions with the failed records

Valid from Pega Version 7.3.1

You can now continue batch data flow runs that failed and complete them with failures. You can also identify all the records that failed during a batch data flow run that is completed with failures. After you fix all the issues that are related to the failed records, you can reprocess the failures by resubmitting the partitions that contain the failed records. This option saves time when your data flow run processes millions of records and you do not want to start the run from the beginning.

For more information, see Data flow run updates.

Multi-Select list control

Valid from Pega Version 7.3.1

You can add a Multi-Select list control to a user form so that application users can select more than one value for a single field. These lists save time and ensure accuracy by supplying a list of valid values for an input field. You can source a Multi-Select list control from a data page, clipboard page, or report definition.

For more information, see Adding and configuring a Multi-Select list control.

Rules Assembly cache is deprecated

Valid from Pega Version 7.3.1

Rules Assembly (RA) cache and custom settings for its corresponding fua/assemblyCacheModeprconfig.xml file setting are deprecated because they are obsolete. A warning is logged at startup if a custom (non-default) value is specified for fua/assemblyCacheMode in the prconfig.xml file. The functional behavior of the system is not affected.

Improved Clipboard performance

Valid from Pega Version 7.3.1

Clipboard performance has been enhanced to use high-speed, read-only data pages, making processing faster. For some high throughput use cases, performance might be degraded. If performance is degraded, you can use a restricted feature set for a specific read-only data page by selecting Restricted feature set for high throughput on the Load management tab of the data page rule.

For information about unsupported features when using a restricted feature set, see High-speed data page support.

Improved usability for feature management

Valid from Pega Version 7.3.1

You can now manage your features more effectively by implementing the following changes in your application:

  • Move features to different levels to change the structure of your feature hierarchy.
  • Provide descriptions that are longer than 256 characters to improve the readability of features.
  • Quickly remove irrelevant features without having to manage dependencies on built-on applications or previous application versions.
  • Consolidate features into one application layer when you are ready to ship your application.

For more information about feature management, see Managing the features in your application.

Real-time statistics added to application overviews

Valid from Pega Version 7.3.1

You can now use the Application Overview landing page to get information about the number, type, and status of work items that are associated with your features. By referring to the statistics and progress bars that update as your team creates and resolves work items, you can track feature development in real time without interrupting your development team for status updates.

For more information, see Real-time statistics for feature development.

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