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-B37351 · Issue 288347

FTP connection test loads authentication profile

Resolved in Pega Version 7.3

The FTP Server Test connectivity button was not working if the server did not allow anonymous connections. This was due to tests not loading the Authentication Profile, and the system has been updated to load the profile during the connection build process.

SR-B37427 · Issue 293709

Security upgrade for Struts2

Resolved in Pega Version 7.3

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

SR-B37598 · Issue 293711

Security upgrade for Struts2

Resolved in Pega Version 7.3

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

SR-B37780 · Issue 293894

Security upgrade for Struts2

Resolved in Pega Version 7.3

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

SR-B37780 · Issue 293899

Security upgrade for Struts2

Resolved in Pega Version 7.3

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

SR-B37780 · Issue 294148

Security upgrade for Struts2

Resolved in Pega Version 7.3

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

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-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-B38317 · Issue 295056

Password expiry logic updated to use start of day

Resolved in Pega Version 7.3

Previously, the password expiry logic was based on a tight format of number of days+ timeStamp. This caused scenarios such as not prompting for a password reset when user logs in, but rather at the exact time stamp of the previous change even if that comes in the middle of work and throws the user out of the session. To avoid this behavior, the password expiry logic is now based on number of days logic with timeStamp defaulted to start of day (00.00) taking care of locale and getting difference in number of days.

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