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-B37915 · Issue 294722

Security upgrade for Struts2

Resolved in Pega Version 7.3

To improve security, Apache Struts2 has been upgraded to version 2.3.32 .

SR-B37923 · Issue 295190

null-pointer exception fixed for ForceCaseClose

Resolved in Pega Version 7.3

An exception was generated when running pxForceCaseClose due to an explicit call to the function before the Step Page was passed. This has been corrected.

SR-B37957 · Issue 303574

XSS security added for date property error message

Resolved in Pega Version 7.3

A cross site scripting filter has been added for pyErrorMessage in order to improve security.

SR-B37957 · Issue 278510

XSS security added for date property error message

Resolved in Pega Version 7.3

A cross site scripting filter has been added for pyErrorMessage in order to improve security.

SR-B37958 · Issue 296563

Radio button error highlight fixed for grids

Resolved in Pega Version 7.3

When a radio-button was configured as mandatory in a grid column, submitting the page without filling in the mandatory field did not correctly highlight the error. This was caused by the system not being able to find the correct label for the associated elements, and code has been added to find the correct label when the radio button is inside a grid.

SR-B37988 · Issue 298759

Fixed Addressing checkbox error in Connect-SOAP

Resolved in Pega Version 7.3

The addressing checkbox on the SOAP connector rule form was not being honored. This was a defect in the third party library 'praxis2-1.6.2-1.jar', and code has been added to disable the processing of WebSphere addressing headers when WebSphere addressing is false.

SR-B38034 · Issue 297014

Improved error handling for Usage Daemon

Resolved in Pega Version 7.3

The Usage daemon was exiting due to DB error and did not recover, leading to PALSnapshotImpl multiplying and causing an OOM. This was traced to missing error handling, and UsageDaemon has now been updated to handle a DB error without exiting.

SR-B38072 · Issue 297065

null-pointer exception fixed for REST XML samples

Resolved in Pega Version 7.3

The rule generation implementation for XML samples in REST wizard was faulty and throwing a NullPointerException if a resource name was the same as any of the complex node names in the sample XML. This has been fixed.

SR-B38101 · Issue 299647

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-B38157 · Issue 301486

Added post-upgrade compatibility for agent tracing

Resolved in Pega Version 7.3

After upgrade, tracing agents was not working due to a change between versions in the method of tracing rules in rulesets of a remote requestor. Previously, rules were traced in the rulesets of the current requestor who initiated the trace; in newer versions, rulesets are fetched for batch requestors so all rules in rulesets accessible to browser requestor are not traced. In order to resolve this, a traceAllRulesets flag has been added for agent tracing so that all rulesets are traced and a note has been added to the settings window stating that in case of agents, all rulesets are traced.

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