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-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.

SR-B46173 · Issue 302359

Improved HTTP thread handling

Resolved in Pega Version 7.3

During the execution of a performance test (SOAP service, RBS application), several exceptions were generated relating to the attempt to use a 'recycled thread'. In order to resolve this, the HTTP thread locking and ownership have been improved.

SR-B46173 · Issue 296360

Improved HTTP thread handling

Resolved in Pega Version 7.3

During the execution of a performance test (SOAP service, RBS application), several exceptions were generated relating to the attempt to use a 'recycled thread'. In order to resolve this, the HTTP thread locking and ownership have been improved.

SR-B462 · Issue 271962

Event Late triggers expanded

Resolved in Pega Version 7.3

If "Limit passed deadline events" was not set to any value and the enqueue item was still in defer-save and not committed to DB, 'Event Late' was not triggered. Code has been added to properly check and trigger the late notice based on this scenario.

SR-B4620 · Issue 277531

Fixed dirty prompt save UI error

Resolved in Pega Version 7.3

The dirty prompt save action was causing corruption in the UI if there were validation errors present. This was traced to the On save of a work object with errors replacing the harness with section. As a result, styles and scripts in harness were lost and only plain/raw html was shown. This has been fixed by removing the Show-Stream step so Show-Harness takes care of refreshing the screen.

SR-B46365 · Issue 303375

Error check added for ID/label mismatch on field labels

Resolved in Pega Version 7.3

When an UploadFileFlow was created, tabbing through fields with blank values updated most of the field labels with the revised style when an error was present, but Date kept its original style. This was due to an issue setting error styles on a property if the label and identifier of a property were different. To handle this, the code has been modified to such that if the identifier of a control and shown text are different, a check in "findLabelFor()" will fail.

SR-B46599 · Issue 304003

ListenerPage made available to the service API

Resolved in Pega Version 7.3

In order to enable using the service mail activity to fetch information from the Email Listener, "pyListenerPage" has been made available in the API so the service activity can find it.

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