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

SR-B46718 · Issue 304110

pyFLowSLA property added to support pxObjClass change

Resolved in Pega Version 7.3

Validation errors occurred when using a data transform which changes the pxObjClass of primaryPage. Pega Platform tries to validate internally for all the properties during the page change class; in order to support the DT, the new property pyFlowSLA has been introduced. The previous pxFlowSLA property has been deprecated.

SR-B46735 · Issue 302808

Debug logging added to better track missing required parameters in declarative pages

Resolved in Pega Version 7.3

A debug logger named "com.pega.pegarules.exec.internal.declare.infengine.pages.DeclarativePageUtilsImpl.MissingParameters" has been added in the DeclarativePageUtilsImpl class to print more info when required parameter is unavailable.

SR-B46802 · Issue 304072

Null check added for missing propInfo in WSDL

Resolved in Pega Version 7.3

A null-pointer exception was occurring in cases where the propInfo generated from SOAP WSDL was null. This has been fixed with the addition of a null check.

SR-B46832 · Issue 302938

Logic added to convert UTC Date for REST clipboard mapping

Resolved in Pega Version 7.3

An error was generated while mapping UTC format Date fields to the clipboard in REST. This was traced to the DateTime properties in the JSON response not being converted to Pega-supported datetime format, and the necessary parsing logic has been added.

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