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-144462 · Issue 601367

Added logoff check for requestors

Resolved in Pega Version 8.1.9

The error "java.lang.InterruptedException. Requester has been destroyed" was appearing in the logs. Investigation showed this was related to unregister requests being submitted after logoff, and has been resolved by updating the system to check for logout before sending unregister requests.

INC-144527 · Issue 599396

Scenario test cases working with radiobutton in grids

Resolved in Pega Version 8.1.9

Running scenario test cases was not working correctly if the table layout had rows with radiobuttons. When the radio button control is included with a property type of boolean in a grid, radioTable class is not present in DOM. Because the scenario testing tool relies on this class of highlighted element to get the target element, the system was not able to get the proper target element in this case. This has been resolved by updating pzpega_ui_automation_radiogroup to get the proper target element when boolean type radio buttons are included in a grid.

SR-D68328 · Issue 557751

Unload handler added for use with custom popups

Resolved in Pega Version 8.1.9

A memory leak seen in Microsoft Internet Explorer was traced to a custom script to close windows which bypassed window unload and continued to hold some objects in memory. This has been resolved by introducing a new file which will load only for popup harnesses and which registers the unload handler to remove the popup window references.

SR-D80696 · Issue 548824

Autocomplete context fetched for dropdown in nested case

Resolved in Pega Version 8.1.9

The autocomplete dropdown was empty when using SmartTip and the down arrow was clicked while opening an autocomplete case within an Interaction case. Opening the service case directly in a new tab populated the dropdown values as expected. This has been corrected by registering context changes just before the content is fetched for the overlay.

SR-D86200 · Issue 549032

Resolved tab appearance issues related to resolution support

Resolved in Pega Version 8.1.9

When trying to add multiple tabs on larger screens, once the first row was filled with tabs then new tabs began appearing at the bottom of the layout group. The layout group worked as expected with the tab overflow having the right and left arrows with the dropdown on smaller screens. In addition, @1440px the overflow arrow on the right side was not working correctly, showing as grayed out even though focus was not on the last tab. These issues were traced to taboverflow with add icon not working correctly at certain resolutions. To resolve this, the todisableslide function has been updated to consider add icon width and layoutgroup has been updated to consider parent width.

SR-D87546 · Issue 553356

Harness context will be stored to handle on click executed outside of the Ajax Container

Resolved in Pega Version 8.1.9

An exception was generated in the interaction portal on execution of a post-value action for the on-change event on a text-box in the service case: "Failed to find instance Work-Interaction-Research.EmailBodyRTE of type Rule-HTML-Section". This was traced to a condition where clicking outside of the Ajax Container context to trigger the change caused the Events code to execute the event in the active context when the active context had already been changed by clicking outside of the AC. To avoid this, the system will store the harness context in the event object using pega.ctxmgr.getContextByTarget(target) API. Additional changes were also made to handle the context switching in case of post value when the blur triggers a change in context.

SR-D91344 · Issue 560627

Resolved PageCannotBeSerializedForPassivationException in logs

Resolved in Pega Version 8.1.9

The exception "One or more properties could not be serialized during passivation and have therefore been lost. They will not be available on activation. Please ensure that all property data is Serializable" was observed in the logs. Investigation showed there was an HTML fragment in 'pzGridOpenAction' that was adding non-serializable properties to the clip board. This did not cause a functional issue, but has been resolved by modifying the way the system obtains and reuses the class definition.

SR-D91964 · Issue 551093

Negative values in optimized table filters show markup

Resolved in Pega Version 8.1.9

HTML markup was shown in the filter popup when Number control was used in a Table cell and there were negative values in the cells at runtime. This was traced to work done on template grid filtering, and has been corrected.

SR-D92571 · Issue 553116

Corrected ReportBrowser refresh section

Resolved in Pega Version 8.1.9

After bringing up the popup menu on a report shortcut in the report viewer and then dismissing it, the gear icon on the shortcuts in the upper section of the report browser stopped responding. This has been resolved by updating the system to refresh the pyReportBrowserInner section instead of pyReportBrowserAll.

SR-D99100 · Issue 564381

Character counter updates correctly with RDL refresh section

Resolved in Pega Version 8.1.9

When using a repeating dynamic layer with a refresh section, the text area character counter was not accurate. This was traced to the system sourcing server-side metadata for the remaining character count and refresh section updating the same remaining count to all textareas. This has been corrected by recalculating the count for each template rendering of textarea so that it works correctly inside templatized repeating structures.

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