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-D47685 · Issue 514646

Cookie logging restored

Resolved in Pega Version 8.2.5

As part of security updates, Cookies were restricted from being logged. However, this caused some business use cases such as a custom function call to obtain the list of cookies that are present in the application to stop working. To resolve this, the cookie logging restriction has been reverted.

SR-D51554 · Issue 514061

Local UUID cache will be updated when merge event is detected

Resolved in Pega Version 8.2.5

Cluster-related issues were seen in multiple production clusters. For some nodes in the cluster the Cluster Management screen showed all expected nodes with valid Node IDs displayed, and on other nodes the Cluster Management screen showed the node ID of itself, SERVER@localhost:5701. On an impacted node displaying the wrong ID, the Node Information landing page did not work and displayed the error "Unable to execute job on ." Multiple advanced agents running on nodes in the affected clusters, both with correct and incorrect IDs, also failed with a similar error "Unable to execute job on <node's job id>". This was traced to a merge performed after a split brain. To resolve this, the code has been updated to handle merge events: when the node UUID is changed as part of a split brain recovery, the local UUID cache will be updated when the merge event is detected.

SR-D52969 · Issue 514703

Column population honors thread count of 1

Resolved in Pega Version 8.2.5

The thread count parameter in the column population activity was not being honored, causing repeated deadlocks when trying to populate columns. Investigation showed that the ExposeCols process did not honor the thread count when it was 1 (the default is 4), and this has been fixed by adding the necessary code so that if the thread count is 1, it will not run in multhreaded mode.

SR-D53408 · Issue 516735

Expired Oauth Refresh Token will persist for obtaining new token

Resolved in Pega Version 8.2.5

OAuth2.0 was providing the refresh token only once in the first time response of the token endpoint. Once the token expired for first time, it was possible to get a new access token using the refresh token. However, if the access token expired for the second time, it was not possible to generate the new access token automatically because the expired token was set as null. To resolve this, the system has been updated to persist the previous refresh token in order to get a new access token.

SR-D29918 · Issue 503066

Resooved duplicated aria-level attribute in layout headings

Resolved in Pega Version 8.2.5

Headings on layouts automatically applied the aria-level attribute. This meant if the markup was an H tag with an aria-level attribute, the screen reader read it out twice. This has been corrected.

SR-D32528 · Issue 502217

Reduced triggering for checkbox click calling resize

Resolved in Pega Version 8.2.5

When using Microsoft Internet Explorer, checkboxes were slow to respond. For example, when clicking two checkboxes in succession, the second checkbox did not change. This was traced to the Layout Resize function getting called numerous times by the _toDisableSlideOnTabsClick and _resizeActions functions during onload refresh. This has been resolved by updating the system so that an LG header cell item checkbox click will not trigger the resize.

SR-D32655 · Issue 510344

Enhancement added to hold Change Tracker values until UI is loaded

Resolved in Pega Version 8.2.5

Sporadically, an agent attempting to answer a queued call within 10 seconds received a loading screen. By the time the load completed, the next agent had already taken the call. This is a scenario where based on a change, the agent was trying to refresh something on the UI (a section or harness) which was not yet loaded/present on the UI. To address this use case, an enhancement has been added to hold the change tracked values and handle them once the UI is loaded. The new function pega.ui.ChangeTracker.prototype.handlePendingCTChanges in pzpega_ui_changetracker.js is used to handle the pending CT changes. A hook has been added in the pzpega_ui_doc_lifecycle js file to invoke the above function once the UI is loaded.

SR-D34214 · Issue 511812

API available to skip defer loading in Single Page Applications

Resolved in Pega Version 8.2.5

The wait message "Loading ..." was displayed on check on defer load in Single Page Applications. The browser refresh worked as expected if 'defer load' was unchecked. This was traced to SPA not containing the handling necessary to publish the forced replace to other modules: in SPA cases, the dashboard is forcibly replaced with workobject harness, causing defer loads in dashboard to be processed in the wrong thread. To resolve this, there is now an exposed API pega.ui.DCUtil.skipDeferredLoadFrom() to skip defer loading when true in SPA.

SR-D37348 · Issue 514839

Added handling for placeholder in Multi-Select List Control

Resolved in Pega Version 8.2.5

After adding a placeholder in Multi-Select dropdown properties to hold the default value as 'please specify' by way of a refresh section on the action tab of multi-select property, the multi-select drop was showing the 'please specify' placeholder after refreshing the section even though there was value in it. This has been resolved by adding handling to make the placeholder empty when there are values.

SR-D39369 · Issue 513096

Handling added for images in true/false checkboxes causing security policy issues

Resolved in Pega Version 8.2.5

The out-of-the-box Pega security policy AllowPegaCollaborationServices, which is included functions such as Pega Customer Services for Healthcare and required by Pega Cloud Collaboration Services, was blocking Pega images from webwb. As an example, using a checkbox "*truefalse" configured with two images for true and false values when this Security Policy was set (which has Image-Source self set), a console error was generated. This was caused by the images URL being a base-64 string instead of a page URL. This meant that when the checkbox was configured with an image, the image was being converted to bytes as if for offline. To resolve this, separate handling has been added for online cases.

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