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.

Select values gadget optimization enhancements

Valid from Pega Version 7.3.1

The Select values gadget includes several enhancements that help reduce performance issues when a data set is very large. Administrators and developers can now add and remove optimizations for fields directly in Designer Studio. Additionally, Select values gadgets were added to the proposition import shape and history shape in the Strategy rule form.

For more information about Select value gadgets and field optimization, see Optimizing properties in Select values gadget.

Use of PegaRULES_Extract_Marker.txt to delete cache is deprecated

Valid from Pega Version 7.3.1

The PegaRULES_Extract_Marker.txt file is deprecated. The system uses the presence or absence of the PegaRULES_Extract_Market.txt file to determine at startup whether to delete the static content, service export, and lookup list file system-based caches. In the rare situation that you need to delete these caches manually, use the System Management Application (SMA) ETier Static Content Management page. Using SMA does not require restarting the node.

Custom scaling on x-axis for bubble charts

Valid from Pega Version 7.3.1

Bubble charts now support custom scaling for the x-axis as well as the y-axis. For example, you can now configure a fixed range for the x-axis.

For information about including a chart in a report, see Adding or editing charts from the Report Definition rule form.

Enable users to save charts as .png files

Valid from Pega Version 7.3.1

You can now enable users to save a report chart as a .png file. On the Chart tab of the Report Definition rule form, click General settings and select the Export chart to image check box. When you select this option, users are provided with the Save as image option, which they can use to save an image of the chart to include in a Word document or email.

For information about including a chart in a report, see Adding or editing charts from the Report Definition rule form.

Enhancements to exporting reports to Excel

Valid from Pega Version 7.3.1

When you export report results to Microsoft Excel, the process now creates a Data sheet and an Info sheet in the Excel file. By default, the Info sheet contains the report title, filters used to generate the report, the date when the report was generated, and the number of results returned.

If you want the report title and filters to display in the first sheet instead of the Info sheet, you can disable the default functionality. For more information, see Disabling the creation of an Info sheet in Excel output.

New alert for distinct values query

Valid from Pega Version 7.3.1

The PEGA0093 alert identifies performance issues when a distinct values query from virtual reports or the getDistinctValuesForProperty API take longer than the threshold. For more information, see PEGA0093: Distinct values query took more than the threshold.

Behavior changes when reporting on descendant classes

Valid from Pega Version 7.3.1

Report Definitions that use the Report on descendant class instances option with the Include all descendant classes option apply only to the Applies to Class. Join classes are not included as they were in previous Pega® Platform versions. The following example shows what happens for each possible scenario for Report on descendant class instances when the report is defined on ClassA with a class join with Work-.

  • If Report on descendant class instances is disabled, the report runs against ClassA and the join happens with Work-. The behavior is the same in Pega 7.3.1 as it is in previous Pega Platform versions.
  • If Report on descendant class instances is enabled, and Include single implementation class is selected, the report runs against ClassA and the join happens with the MySampleClass implementation class. The behavior is the same in Pega 7.3.1 as it is in previous Pega Platform versions.
  • If Report on descendant class instances is enabled, and Include all descendant classes is selected, the report runs against ClassA and its descendants and the join happens with Work-. In previous Pega Platform versions, the join happened with the MySampleClass implementation class.

Automatically update dependent applications to use the latest versions of built-on applications

Valid from Pega Version 8.5

You can now automatically update dependent applications to use the latest versions of built-on applications. When you import an archive that you created from a product rule, you can update all dependent applications to be built on the latest application versions in the archive.

For more information, see Updating dependent applications with the latest versions of built-on applications.

 

Alerts for long-running queue processor and job scheduler activities

Valid from Pega Version 8.5

Pega Platform™ now saves an alert in the performance alert log when a queue processor activity or a scheduled job runs longer than the configured threshold value. Use the alerts to identify potential performance issues with long-running processes.

The alerts are enabled by default. You can change the alerts for dedicated queue processors and job schedulers at the rules level. For standard queue processors, you can also set the threshold value for the Queue-For-Processing command in an activity. You disable the alerts in dynamic system settings.

For more information, see:

Introduction of Search and Reporting Service

Valid from Pega Version 8.5

Pega Platform™ now uses Search and Reporting Service, which is an independent microservice. The new enhancement provides a convenient way to manage your application data, and is easier to maintain. For example, because of the cloud-based architecture of Search and Reporting Service, any bug fixes and performance improvements occur seamlessly, and have no impact on your overall experience in Pega Platform.

For more information, see Search and Reporting overview.

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