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-A21098 · Issue 246780

Updated row delete authorization failure error message

Resolved in Pega Version 7.2.1

The delete button at the top of the ListViewEditor was correctly configured to delete or not based on permissions, but the proper error message did not appear when the edit attempt failed. The function will now show the message "You are not authorized to delete row." in cases where there was no permission to delete the instance.

SR-A21514 · Issue 242070

DateTime calendar displays time in report filter view

Resolved in Pega Version 7.2.1

The DateTime calendar was not displaying time in the pre-report filter screen while the same calendar displayed both date and time in the report viewer screen. This has been corrected.

SR-A21573 · Issue 241299

Security update for Web Service Policy RampartConfig signaturePassword

Resolved in Pega Version 7.2.1

Appropriate changes have been made to support password obfuscation in signaturePassword and userPassword elements of RampartConfig elements configured in Ws-Policy rule form.

SR-A21597 · Issue 241378

Request Only' I/O timeouts updated for Connect HTTP

Resolved in Pega Version 7.2.1

The Request Only checkbox option on Connect HTTP rules is intended to optimize IO latency for fire-and-forget use cases. The code that implements the connector was performing a full request/response HTTP call, even when the Request Only option had been selected. This sometimes caused long IO delays in the connectors. This update leverages the ability of the HTTP client to set a socket read timeout value on the response coming back from the server, which has now been set to 1 millisecond (zero milliseconds is not an option) in the cases when the Request Only feature has been enabled on the connector rule. The HTTP socket connection will time out immediately after the request message has been sent and eliminate any overhead of consuming the HTTP response data. Any connection failures will still be reported as exceptions.

SR-A21629 · Issue 243799

Enhanced column supports in 'Export to Excel'

Resolved in Pega Version 7.2.1

Reports using functions in columns were not working with 'Export to Excel'. This has been fixed. Support has also been added to display all the report column localized values in pzListViewExcelData while doing Export to Excel: Simple Column, Joins, Declare Index,Associations,Sub Report,Functions and Embedded Properties.

SR-A21792 · Issue 242548

Saver.addBatch updated to log exception details

Resolved in Pega Version 7.2.1

To improve diagnostics, an SQL exception in the Saver class will log the actual exception instead of a null pointer.

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-A21935 · Issue 247142

Corrected data page Lookup logic

Resolved in Pega Version 7.2.1

While trying to source a Datapage with Lookup, a "No records found" error was generated by the fetch using the pyClassName from parameter and considering that as primary page class instead of the data page page class. This has been corrected by using the pxObjClass from the parameter page, which is an actual data page class.

SR-A22152 · Issue 247716

Report Def Filter using .pxObjClass returns all results

Resolved in Pega Version 7.2.1

Using .pxObjClass as a filter in Report Definitions resulted in different and/or incomplete Class arrays being built depending on how the Value field was populated. This was traced to an incorrect "if" check in objClassOptimizer causing class names to be missed, and has been fixed.

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