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-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-B42262 · Issue 303693

Field Values displayed correctly in mobile dynamic layouts

Resolved in Pega Version 7.3

Dynamic layout headers that reference Field Values were not displayed correctly in the mobile application. This was caused by the getLocalizedValueFromList function not passing activeContext to the resolveParams function, and has been fixed.

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-B42581 · Issue 299511

BIX enhancement to handle unaligned external mappings

Resolved in Pega Version 7.3

If a class with external mappings was configured and some of the properties did not match the db column name, a filter for one of those properties would not be applied to the extract query. In order to support business needs that contain the mis-match, an enhancement has been made to the BIX code to handle this non-alignment.

SR-B42586 · Issue 299297

Modified RD filtering rule to support custom validation

Resolved in Pega Version 7.3

Custom validation was not stopping a Report Definition from completing due to validation errors not being applied to the correct page when submitting the form. In order to support this customization, pzValidateCustomFilterSection has been modified to put messages on the step page rather than primary page.

SR-B42586 · Issue 300843

Modified RD filtering rule to support custom validation

Resolved in Pega Version 7.3

Custom validation was not stopping a Report Definition from completing due to validation errors not being applied to the correct page when submitting the form. In order to support this customization, pzValidateCustomFilterSection has been modified to put messages on the step page rather than primary page.

SR-B42911 · Issue 301591

Tomcat config documentation clarification

Resolved in Pega Version 7.3

The documentation for using Tomcat has been updated for clarity. Step 2b of 'Configuring Tomcat by editing the context.xml file' indicates that configuration of the Admin datasource is optional (which it is), but steps 3 and 4, which use this datasource, were not labeled as conditional on 2b. As a result, those opting not to use the admin datasource believed those settings needed to be added. In the new text for steps 3 and 4, the clarification "For dual-user configurations only, insert..." has been added.

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.

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