Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-A21756 · Issue 244285

defined-on class error resolved

Resolved in Pega Version 7.2.1

A defined-on class error was being generated when attempting to add strategies to the overlay that referenced a decision rule defined on an SR class with a space in the name. This has been fixed.

SR-A21756 · Issue 243206

defined-on class error resolved

Resolved in Pega Version 7.2.1

A defined-on class error was being generated when attempting to add strategies to the overlay that referenced a decision rule defined on an SR class with a space in the name. This has been fixed.

SR-A21844 · Issue 241153

VBD enhancements

Resolved in Pega Version 7.2.1

The following enhancements have been added to the Visual Business Director feature of PRPC Decisioning: - Support added for changes in field sizes after partitions load - Partitions will be loaded immediately on VBD server startup - Data expiration based on inactivity is disabled to reduce query latency - Timeout added to VBD queries to handle latency when Partitions initially load - Code that processed Actuals query JDBC resultset is optimized

SR-A21931 · Issue 242711

XY chart Dashboard reports updated to handle empty data

Resolved in Pega Version 7.2.1

Dashboard reports were not loading when using RD as the source for XY charts if the data returned was completely empty. RUF: pzControl ? pzRuntimeFusionXYDataJSON has been updated to handle this missing use case.

SR-A21931 · Issue 233188

XY chart Dashboard reports updated to handle empty data

Resolved in Pega Version 7.2.1

Dashboard reports were not loading when using RD as the source for XY charts if the data returned was completely empty. RUF: pzControl ? pzRuntimeFusionXYDataJSON has been updated to handle this missing use case.

SR-A22365 · Issue 243530

Multi-parameter function value handling added to Report Definition chart

Resolved in Pega Version 7.2.1

When a chart control was configured using the property panel in design view, the chart preview did not update appropriately if it used a column defined by a function that with two or more parameters. To handle this, part of com.pega.pegarules.priv.desktop.reporting.chart.AutoChartConfigTranslator.translateDataItem(DataItem, ClipboardPage) has been refactored such that it only splits pyReportColumnKey on the first ',' (comma).

SR-A22841 · Issue 245073

All Data Flow keys considered for filtering

Resolved in Pega Version 7.2.1

When a Data Flow containing a Filter was run , the filter step showed incorrect results in the "Successful records" column even though previewing it from the Data Flow rule it showed the correct result. The algorithm that queries a secondary source shape in the data flow was ignoring all but the first key, and has been updated to properly process all of the keys before displaying any results.

SR-A22993 · Issue 247098

Date format and alignment updated for Export to Excel

Resolved in Pega Version 7.2.1

When using Report Definition for a case search with the out-of-the-box excel export, formatting one of the DateTime type properties to display only the date portion in the exported report was not working as expected in the repeated-grid while it did work properly in report definition export function. The problem existed in the generation for the Report Definition itself due to the control formatting the data to be mm/dd/yyyy without the days even though the data type is a datetime, and the function has been updated to pass "date" as the datatype when a datetime is being formatted as a date.

SR-A23035 · Issue 245109

Enabled bulk delete of ADM models

Resolved in Pega Version 7.2.1

In order to support the deletion of ADM models in bulk, an enhancement has been added to remove the unwanted models from the database provided a list of them is given as input. The activity pxDeleteModelsByCriteria has been created; "Used to delete ADM models in bulk. Models to be deleted are determined by the criteria selected by this Activity's parameters; a model is deleted if it matches all selected criteria." PLEASE NOTE: activity is not constrained by Application, only by the criteria provided as parameters. Therefore in most cases you will probably want to constrain by 'applies to' class in addition to the other criteria. Please see the tooltip / description of each parameter for more info on their usage. Integer output parameter 'NumberDeleted' returns the number of models that were successfully deleted."

SR-A23395 · Issue 245032

Optimized decision data components

Resolved in Pega Version 7.2.1

Decision data component performance has been optimized to better handle the heavy demands of the java generated for every mapping using get property and set values API calls in all scenarios.

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