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.

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.

INC-125398 · Issue 564979

Updated handling for checkboxes configured in the header

Resolved in Pega Version 8.2.8

After configuring multiple checkboxes where each checkbox had a different property and different DT as action set and then using them as a single column header in the table, the on-change of any one checkbox caused all of the checkboxes to be checked or unchecked in the column header. This was caused by the pega.ui.grid.prototype.checkAllIfInHeader, which selects or unselects all checkboxes present in table (header +. body) based on checkbox status in header. However, the header row should not be part of the iterator during this function, and the necessary update has been made.

INC-126255 · Issue 580907

Resolved "maximum limit for pending changes" error

Resolved in Pega Version 8.2.8

When attempting to create a work object in a custom way using doCreateNewCase from the Smart investigate layer by using the RMButtonWithoughtWorkCaseNGP section, a popup showed the error “You have reached maximum limit for pending changes. Please commit/cancel one or more changes to continue.” The error did not occur when creating the case using the out-of-the-box Create New Work action. This was traced to the custom configuration creating work object threads that were not destroyed after the work item is closed. To resolve this, handling has been updated for passing dynamiccontainerID and contentID parameters for OpenWorkByURL case. Note that the pzUpdateActionInfo activity must be called in any custom activity before the actual activity is invoked.

INC-128970 · Issue 583291

Post value in grid works after clicking on modal submit

Resolved in Pega Version 8.2.8

The row submit on the grid of the modal dialogue worked when the value was updated and there was a click outside the grid. However, when the value was auto-populated, after clicking on the submit and going back to edit the value in the grid, the row submit did not work. Investigation showed that when a modal was submitted with some server errors, the system replaced the DOM and a new grid is initialized: since some of the listeners related to grid are attached to body, on submit of modal with server errors, these old listeners were getting fired. To resolve this, a safe check has been added for modalDetailsDiv before accessing it in event listeners.

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