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.

SR-D31344 · Issue 503070

Stale div classes are removed on refresh of section

Resolved in Pega Version 8.4

When a section had a navigation rule and a button configured in the same section with 'Refresh - Section' in its action set, each click of the button (i.e on each refresh of the section) added an additional row of <div class="menu-panel-wrapper">. This was traced to the sub-menus div not getting removed on every refresh, and has been resolved by explicitly removing the stale div.

SR-D31599 · Issue 503199

Table layout filter by format works for empty value

Resolved in Pega Version 8.4

If a DateTime property with empty values in a table layout grid was filtered by format, no result was returned even though the grid had the Records for empty DateTime property. This was traced to null value filtering being done with empty values instead of a formatted null value, a difference that could produce different results depending on the control. To resolve this, the activity has been updated to support null values filtering.

SR-D31702 · Issue 505057

Added constraints to RTE resize

Resolved in Pega Version 8.4

When using Microsoft Internet Explorer 11 with a column layout with main (using RTE) and a side bar (with a text input), dragging the RTE box towards the right side from the bottom right hand corner caused it to expand and overwrite the contents of the side bar. This occurred irrespective of whether the column layout was placed in a dynamic layout or standalone. Investigation found that this was caused by there not being any restriction on the resize of RTE, which allowed it to expand beyond limit. This has been corrected.

SR-D32086 · Issue 500895

Memory leak repaired

Resolved in Pega Version 8.4

A server side memory leak was traced to heap utilization increasing due to a Stream control assembly problem where the CleanForReuse() function was not cleaning up pzAuto. The cleanForReuse method in generated HTML properties is used to either initialize local fields, in which case aContext will be non-null, or to clear the object for pooling, in which case aContext will be null. Because the pzAuto variable was not being properly nullified, pooled controls were retaining stale references to StreamTools, LayoutRuntime, PRThread, and others. This has been resolved by adding code to ensure the pzAuto variable is correctly nullified, and additional work has been done to improve memory management.

SR-D32507 · Issue 507846

GenerateCellContent updated to properly set active context

Resolved in Pega Version 8.4

An issue with adding and deleting items in existing rows in a repeating grid layout was traced to the Base_ref being wrongly stamped on a section included cell. This was caused by a grid in previous cell causing the active context to be updated to the cell's grid source context, and has been resolved by updating the generatecellcontent Rule-Utility-Function to set the active context properly in generation.

SR-D32525 · Issue 505468

Dirty check added to offer save/discard changes when closing tab

Resolved in Pega Version 8.4

With the out-of-the-box section enabled, performing a change in the form (changing a text value, selecting a option in a dropdown, etc.) and closing the case generated an unexpected alert indicating that the case was changed and the modifications were lost. This differs from the previous behavior of showing the section pyDirtyCheckConfirm which offered the opportunity to save the work. This was a missed use case and has been resolved by updating the system to perform a check for the dirty state when closing the interaction and show a modal dialog asking the user to choose either save/discard if dirty.

SR-D32528 · Issue 502218

Reduced triggering for checkbox click calling resize

Resolved in Pega Version 8.4

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-D32637 · Issue 504120

Added minification for out-of-the-box javascript files

Resolved in Pega Version 8.4

Several out-of-the-box javascript files were not being compacted/minified as expected. This has been resolved.

SR-D33008 · Issue 505865

Added handling for 'Safari version is not a number' error on mobile

Resolved in Pega Version 8.4

When using a browser on mobile, the error "Safari version is not a number" appeared intermittently in the logs. This was traced to the code "Mozilla/5.0 (iPhone; CPU iPhone OS 12_3_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.1.1 Mobile/15E148 Safari/604.1" returning the wrong value for the above user agent string because "Mobile/" was present in between Version/ and Safari/. This has been resolved by updating the BrowserUtilsRuntime.java file to handle these cases.

SR-D33096 · Issue 502742

pzGetURLHashes returns proper content-type

Resolved in Pega Version 8.4

When using an environment set with X-Content-Type-Options:nosniff, the response from pzGetURLHashes was returned with text/html response type and the mashup would not load due to browser exception "MIME Type ('text/html')is not excutable, and strict MIME type checking is enabled." In order to support CORB mitigation in the browser, the javascript content type will be set in the response header for pzGetURLHashes call.

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