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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-B45093 · Issue 301258

Fixed invalid reference for auto-populate

Resolved in Pega Version 7.3

An invalid reference exception was generated while trying to do Property-Ref on two properties inside Auto populate. This was caused by a coding error in a check used to avoid doing a getSourceProperty in case of a reference to a top level page, and has been fixed by modifying the setAsReference API in ClipboardProperty to gracefully handle Autopopulate scenarios.

SR-B45435 · Issue 301778

GenerateGridHTML updated for JAWS version compatibility

Resolved in Pega Version 7.3

An update to the JAWS program caused it to no longer recognize some Pega grids as tables due to the use of role=presentation, and the table name was not associated with the layout header title leading to the tables not being labeled accordingly. To correct this, the GenerateGridHTML now has an added summary attribute in the ".gridTable".

SR-B4548 · Issue 275463

Class Data-Admin-Connect-MQServer now cached

Resolved in Pega Version 7.3

The rule instance cache has been updated to include the type Data-Admin-Connect-MQServer.

SR-B4548 · Issue 275330

Class Data-Admin-Connect-MQServer now cached

Resolved in Pega Version 7.3

The rule instance cache has been updated to include the type Data-Admin-Connect-MQServer.

SR-B45613 · Issue 302956

Fixed query for RD using dependent classes

Resolved in Pega Version 7.3

A runtime exception was generated when running a summary report due to an incorrect query being built for RD when dependent classes was checked. This was caused by pyGetDistinctRecords being set to true even for summary reports, and has been corrected by ensuring pyGetDistinctRecords is set to false for summary reports.

SR-B45640 · Issue 302810

Resolved ConcurrentModification exception in getclass name

Resolved in Pega Version 7.3

Attempting to getclass name while iterating over values of mPageProperties in expandAllToProperties (in the putPropertyOntoClipboard call) was causing a ConcurrentModificationException that resulted in queues being blocked and loss of synch to the server. In order to more cleanly set the pxObjClass for the classless page-properties, pxObjClass has been added to the lookupDictionaryDefinition.

SR-B45640 · Issue 303222

Resolved ConcurrentModification exception in getclass name

Resolved in Pega Version 7.3

Attempting to getclass name while iterating over values of mPageProperties in expandAllToProperties (in the putPropertyOntoClipboard call) was causing a ConcurrentModificationException that resulted in queues being blocked and loss of synch to the server. In order to more cleanly set the pxObjClass for the classless page-properties, pxObjClass has been added to the lookupDictionaryDefinition.

SR-B45744 · Issue 302814

Debug logs Response XML

Resolved in Pega Version 7.3

The InvokeAxis2 activity was logging the Request XML to the debug log, but was not logging the Response XML. Code has been added to the InvokeAxis2 Activity to print the SOAP Response in the log file when debug is enabled.

SR-B45917 · Issue 302415

DisplayReport date made consistent between report and exported PDF

Resolved in Pega Version 7.3

When exporting a report to PDF, the "Generated on" date did not match the format on the report. This was caused by the system using different controls for date in pzDisplayReportSectionForPDF and displayReportSection, and has been resolved by changing the date format specified in pzDisplayReportSectionForPDF to match that in displayReportSection.

SR-B46050 · Issue 302190

Corrected DateTime corruption

Resolved in Pega Version 7.3

If "Display value using read-only formatting" was selected for a Date field, entering an invalid value caused the resulting HTML DOM to be displayed incorrectly when the page was refreshed. This was traced to missing handling for the exception resulting from the invalid data, 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