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-135874 · Issue 583414

Added handling for password containing a colon on Pega Client for Windows

Resolved in Pega Version 8.2.8

If a password included a colon (:), it was possible to log in on the desktop but not Pega Client for Windows. This was due to authentication files specific to the Windows mobility client, and handling has been added to resolve the issue.

INC-137516 · Issue 592455

Invalid redirect URI logging changed from error to warn

Resolved in Pega Version 8.2.8

The Pega Mobile client was reporting an Invalid redirect URI error triggered by the OOTB AuthorizationService. This warning is not an error, and the log method has been changed form error to warn.

INC-137709 · Issue 584289

New security role added to restrict access to development-specific classes

Resolved in Pega Version 8.2.8

A new security role and related RAROs have been implemented to allow better security for end users on non-BAC systems. This restricts access to Rules and execution of activities on classes that are development-specific.

INC-144597 · Issue 598306

Updated handling for MT query of pr_data_admin table

Resolved in Pega Version 8.2.8

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-145694 · Issue 601295

Property check handling updated for Ajax requestor

Resolved in Pega Version 8.2.8

SECU0001 alerts were seen when submitting a case in the interaction portal. Logging indicated the errors were related to the 'pxRequestor.pyLatitude' and 'pxRequestor.pyLongitude' properties which are included in an Ajax request when they exist in the DOM and the 'pyGeolocationTrackingIsEnabled' when rule is true. The error was traced to a condition where a new thread request results in an unexpected property check that encounters a clipboard which doesn't have any pages created for that thread. To resolve this, the 'pxRequestor.pyLatitude' and 'pxRequestor.pyLongitude' properties have been added to an allow list to handle the unexpected properties check.

INC-142648 · Issue 594805

PRTraceServlet security check added

Resolved in Pega Version 8.2.8

Modifying the Pega application URL with PRTraceServlet displayed multiple user credentials and session information. This has been corrected with the addition of a privilege check in GetConnectionListCommand before allowing the connections list to be fetched.

INC-130304 · Issue 567925

Retry logic added for downloading upgraded rules

Resolved in Pega Version 8.2.8

A Rules upgrade failed while downloading applications from the maintenance server due to an SFTP server connection failure. This has been resolved by adding logic to retry if the first connection attempt fails.

INC-132218 · Issue 573358

Resolved buffer overflow for Migration loadDatabase

Resolved in Pega Version 8.2.8

A Rules upgrade failed in the Migration step at loadDatabase stage, involving the move of all the table records from old schema to new schema. This was traced to the inability of Migration to load blob of sizes more than 100 MB, and has been resolved by updating Migration to use byte[] to read the blob content with the help of metadata that contains blob length.

INC-133202 · Issue 574700

TableRenameUtil hashing improved

Resolved in Pega Version 8.2.8

During index name generation, the algorithm that was responsible for index name uniqueness was sometimes insufficient and cerated a loop condition. This has been resolved by using a stronger hash algorithm and refactoring the code that could result in a loop.

SR-D37487 · Issue 507206

Helper classes showing in the Helper Class Picker

Resolved in Pega Version 8.2.8

When opening the skin rule -> Actions -> Launch -> Skin Preview -> Helper class, the helper classes were not displayed in the picker. The helper classes were visible if they were manually entered in the Cell read-write classes or Cell read-only classes. Investigation showed that the CSSCommentParser.java was throwing a StackOverFlow exception while finding comments in the text file. To resolve this, the regex has been rewritten to not use alternation.

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