SR-D29517 · Issue 513174
OpenURLWindow works after click on MailTo
Resolved in Pega Version 8.4
After configuring an openURLWindow action for a link in a modal dialog, clicking on any email ID link and then clicking the openURLwindow action did not launch the URL as expected. This has been corrected by stopping the unload event in dom when clicking on a MailTo.
SR-D29809 · Issue 505257
Extra <p> tag removed when not needed in RTE generation
Resolved in Pega Version 8.4
The RTE was generating an extra <p> tag in the Review harness or when the RTE was non-editable, causing alignment issues in the UI when RTE was displayed using inline dynamic layout with a textarea. This has been corrected.
SR-D29918 · Issue 503067
Resooved duplicated aria-level attribute in layout headings
Resolved in Pega Version 8.4
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-D29926 · Issue 501408
FormatType reset added to ensure accurate DateTimes
Resolved in Pega Version 8.4
Read-only Date Time fields in the Case Information screen were displaying just the Date in Review Harness mode but displaying Date and Time properly in perform mode of the case. This was traced to a scenario where if any section which had only a date property was rendered in non-template, then 'pyFormatType' was being set as 'date' in tools and not reset afterwards. That meant any datetime type property rendered after this date property was rendered without a timestamp. This has been corrected.
SR-D30215 · Issue 503684
XSS protection added to ClientDynamicData
Resolved in Pega Version 8.4
Cross-site scripting protection has been added to the "DesignViewIframe" & "pzHarnessID" parameters in the pzClientDynamicData HTML rule.
SR-D31336 · Issue 501287
Dropdowncontrol shows correct value in read-only mode
Resolved in Pega Version 8.4
The dropdown control was not showing the correct value in read-only mode when the standard value of one option was the same as the prompt value of another. Investigation showed that in read-only mode, the loop to fetch the selected value from the datapage results was not stopping when it found an exact match. This has been resolved with the addition of a break statement.
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.