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-B42249 · Issue 301181

Resolved HashMaps memory leak

Resolved in Pega Version 7.3

A memory leak was found with HashMap "mapHosts" within MultiThreadedHttpConnectionManage. To handle this, updates have been made to prcommons-pr54.jar (MultiThreadedHttpConnectionManager.java) and cross verified with the latest library from Apache.

SR-B42305 · Issue 299199

Parse-XML generation updated for complex XML element

Resolved in Pega Version 7.3

When generating the datamodel using the REST wizard, if the response XML had a page with type attribute then the value was ignored at run time. This has been fixed with updates to the "RuleGeneratorREST.java" for data model generation and "ParseXMLSAXRuleWrapper.java" for run time handling.

SR-B42374 · Issue 299138

Data Import Wizard Flow error corrected

Resolved in Pega Version 7.3

The Data Import Wizard was failing with the error "Unable to perform {1}: assignment does not exist." This was due to the pzDataImport screen flow being in Draft mode, causing any rule that runs it to fail if the system is in Production level 5. This has been corrected by setting the draft mode to off.

SR-B42374 · Issue 299446

Data Import Wizard Flow error corrected

Resolved in Pega Version 7.3

The Data Import Wizard was failing with the error "Unable to perform {1}: assignment does not exist." This was due to the pzDataImport screen flow being in Draft mode, causing any rule that runs it to fail if the system is in Production level 5. This has been corrected by setting the draft mode to off.

SR-B42964 · Issue 302624

History table updates with data table record deletion

Resolved in Pega Version 7.3

The Deletion of the record from a data table was not adding an entry into History table. This behavior has been changed with a "History-Add" step in the pzDeleteRecord activity.

SR-B43331 · Issue 302897

Help file updated for consequences of "Ignore Locale" setting

Resolved in Pega Version 7.3

Issues with date values were encountered in set ups where a localized Language Pack had been installed and developers used the "Operator Ignore locale preference" in Designer Studio in order to have Designer Studio in English. While the user portal was correctly translated and European format dates were accepted, an error stating "date is not a valid date value" would appear when a date time field was updated or a new ruleset was created. In order to ease the use of the setting, the help files have been updated to clarify that the "Ignore Locale" option on the Operator screen causes ALL locale settings to be ignored and the default en_US settings to be used. In addition to the display language, these settings include date, time and number formats.

SR-B43927 · Issue 300881

Net commons SSL JAR updated

Resolved in Pega Version 7.3

The net commons SSL JAR has been updated to the latest version.

SR-B43950 · Issue 300643

SAML SessionInfo cleanup enhanced

Resolved in Pega Version 7.3

The following SAML issues have been corrected: 1) when IDP logout URL was empty, SAMLSingleLogOff activity generated an exception; 2) the SAML Session info record was not deleted during logout process even when given a valid IDP logout URL; 3) the SAML session info record was not deleted for both SP and IDP initiated logouts.

SR-B43950 · Issue 301551

SAML SessionInfo cleanup enhanced

Resolved in Pega Version 7.3

The following SAML issues have been corrected: 1) when IDP logout URL was empty, SAMLSingleLogOff activity generated an exception; 2) the SAML Session info record was not deleted during logout process even when given a valid IDP logout URL; 3) the SAML session info record was not deleted for both SP and IDP initiated logouts.

SR-B44280 · Issue 302124

Fixed REST call to JVM property http.non.ProxyHosts

Resolved in Pega Version 7.3

If JVM system properties are used to configure an HTTP proxy, it is applied unconditionally by all REST connectors. The JVM property http.non.ProxyHosts is normally used to exclude connections selected hosts from using the proxy, but due to an error this property was not being consulted by the REST connector. This has been corrected.

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