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.

INC-144591 · Issue 601611

Oauth and beanutils jars upgraded

Resolved in Pega Version 8.4.4

The third party Oauth2 jars and commons-beanutils jar have been updated to the latest versions.

INC-144597 · Issue 598307

Updated handling for MT query of pr_data_admin table

Resolved in Pega Version 8.4.4

When using a multi-tenant environment with Oracle, as the number of users in the environment increased, the number of queries of the pr_data_admin table "WHERE pyEnableAuthService" increased exponentially and causes system slowness. This was traced to missed handling for the @ character in the authentication service cache while requesting, and has been resolved by updating authservicecache.java.

INC-145033 · Issue 599482

ForgotPassword responses made consistent

Resolved in Pega Version 8.4.4

To prevent possible exposure of valid usernames, the ForgotPassword logic has been updated so that it will show the same messages and set of screens to both valid and invalid users if a lost password request is made.

INC-146434 · Issue 602740

Accessibility added to Security Event Configuration headers

Resolved in Pega Version 8.4.4

Labels for the headers in the Security Event Configuration screen have been converted to dynamic layout headers so they will be detected by JAWS screen reader.

INC-146921 · Issue 601638

Cross-site scripting update for Dev Studio

Resolved in Pega Version 8.4.4

Cross Site Scripting (XSS) protections have been added to Developer Studio.

INC-154627 · Issue 619570

Re-enabled users are able to log in

Resolved in Pega Version 8.4.4

When disabled operators were re-enabled through operator management, the forced password change on next login was manually unchecked but the operators were unable to login because the change password screen was displayed without any password entry fields. This was a missed use case for handling the change password flag on a requestor , and has been resolved by having the system skip setting the change password on next login flag for disabled users.

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