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

SR-B4703 · Issue 276811

Browse Messages accepts custom properties for authentication

Resolved in Pega Version 7.3

Browse Messages was throwing a username null error due to custom properties provided in the JNDI server rule form not being read. Support has now been added to read custom properties for browse messages.

SR-B4749 · Issue 285795

Fixed Guardrail warnings not clearing on Justification

Resolved in Pega Version 7.3

Guardrail warnings that appeared on the Map Structured rule Justification Dropdown were not clearing until the mapping was deleted and readded with proper justification. This was an error related to the value default for property pyJustification not being defined in the prompt list, and has been fixed by adding blank as a valid value for pyJustification property with prompt label "Default", and setting the pyJustification in pyDefault model for the row to be empty string instead of "Default".

SR-B47650 · Issue 301985

Dynamically populated values localized

Resolved in Pega Version 7.3

Dynamically populated values were not getting translated in Data Migration Wizard. In order to improve localization, Property Value has bene modified to use a Localized property value for pyLabel in general settings.

SR-B47650 · Issue 303884

Dynamically populated values localized

Resolved in Pega Version 7.3

Dynamically populated values were not getting translated in Data Migration Wizard. In order to improve localization, Property Value has bene modified to use a Localized property value for pyLabel in general settings.

SR-B4772 · Issue 285014

GetXML read-only conflict resolved

Resolved in Pega Version 7.3

When executing the "run" button on the rule form to test a read-only data page sourced by a Rule-Parse-XML, a read-only violation in getXML() resulted when attempting to expand the XML of the page for presentation to the user. This was traced to an unnecessary override IF block in prGetObject() related to overriding context class, and it has been removed.

SR-B5172 · Issue 275097

SOAP handling for BOM bites fixed

Resolved in Pega Version 7.3

After upgrade, an exception was generated when hitting the PRSOAPServlet. This was due to an error in encoding BOM bytes, 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