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.

Operator presence record tracks disconnected status of operators

Valid from Pega Version 7.3

The state attribute in the operator presence record now tracks the operator connection status of DISCONNECTED, in addition to tracking the operator connection status of ACTIVE, AWAY, or OFFLINE. Operators are disconnected if their browser crashes, if they close a browser session without logging out of the system, or if the network connection is down. The DISCONNECTED status helps prevent work from being routed to operators who are not online or not available.

When the operator restores the browser session or the network connection is restored, the Pega® Platform updates the operator connection status to ACTIVE.

For more information, see Tracking the online presence of operators.

Chart drilldown capabilities extended to dashboard widgets

Valid from Pega Version 7.3

When the chart for a report is displayed in a dashboard widget, you now can click any part of the chart to drill down and view the subset of data for that part. This enhancement provides you with an accurate view of the data that determines the report results. Previously, this capability was provided only in the Report Viewer.

Designer Studio keyboard navigation

Valid from Pega Version 7.3

Keyboard navigation adds speed and convenience to Designer Studio. To open the command palette and search within or select from a list of Designer Studio menu options, press Ctrl+Shift+P (Command+Shift+P on a Mac). For more information, see Navigate Designer Studio menus with the keyboard.

Enhanced autocomplete control with combo box functionality

Valid from Pega Version 7.3

You can now add combo box functionality to an autocomplete control. You enable this functionality on the Presentation tab of the control. In the combo box, search results that match the search criteria are displayed in a list that you can scroll through by clicking the down arrow.

For more information about how to configure an autocomplete control as a combo box, see Autocomplete Properties — Presentation tab.

Enhancements to exporting report results to Excel

Valid from Pega Version 7.3

When you export report results to Excel, the .xlsx file that the export process generates is smaller, opens faster, and no longer displays a security warning when you open it. Excel handles more of the formatting, and DateTime, Date, TimeOfDay, and Numeric properties are exported in a format that Excel recognizes. In addition, columns have sorting and filtering enabled by default.

These enhancements are enabled by default and provide improvements to performance and memory usage, especially with large data sets. You can disable this new default behavior by modifying the pyEnableExportToAdvancedExcelFormat when rule. For more information, see Disabling the default functionality for exporting reports to Excel.

Logging service now uses Apache Log4j 2

Valid from Pega Version 7.3

The Pega® Platform now uses the Apache Log4j 2 logging service. Apache Log4j 2 improves performance and provides support for all log file appender types. As a result of this upgrade, the prlogging.xml file has been renamed to prlog4j2.xml and the format of the file has changed considerably.

For details about the new file format see Pega Platform logging with the Log4j 2 logging service.

For new installations or for upgrades to systems that were using the default logging configuration, no changes are needed. For information about updating custom log files after upgrading, see Customizations to the prlogging.xml file must be manually ported after upgrade. For information about updating your socket server if you use remote logging, see Socket server has changed for remote logging. For information about updated the web.xml file after upgrading, see Log file description in web.xml incorrect after upgrade to Apache Log4j2.

Customizations to the prlogging.xml file must be manually ported after upgrade

Valid from Pega Version 7.3

As a result of the upgrade from the Apache Log4j 1 logging service to the Apache Log4j 2 logging service, the name of the logging configuration file has changed from prlogging.xml to prlog4j2.xml and the format of the file has changed considerably. If you customized your prlogging.xml file, port the customizations to the new prlog4j2.xml file. If you do not port the changes, the Pega® Platform uses the default prlog4j2.xml file and disregards your customized prlogging.xml file.

For more information about customizing your log files, see the Apache Log4j 2 documentation.

Socket server has changed for remote logging

Valid from Pega Version 7.3

As a result of the upgrade from the Apache Log4j 1 logging service to the Apache Log4j 2 logging service, the socket server that is used for remote logging has changed from the Log4j remote logging package with the LogFactor5 log analysis tool to TcpSocketServer. If you use remote logging, update your socket server to TcpSocketServer. For more information, see Installing and using remote logging.

Consistent authoring experience for sections

Valid from Pega Version 7.3

Section references inside a dynamic layout have the same configuration options as a top-level section within a section (section include). Section references reduce the need for included sections, reduce the size of the document object model (DOM), and provide a more consistent authoring experience. You can specify a container format, set view and update privileges, and defer content load for sections within or outside of a dynamic layout. For more information see Harness and Section forms - Adding a section.

Refer to mixin settings in override CSS

Valid from Pega Version 7.3

You can refer to mixin settings inside an override CSS, which makes it easier to maintain and restyle your application. Properties for typography, border, background, and combination mixins can be referenced in an override CSS. For more information see Mixins in an override CSS.

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