SR-D56836 · Issue 518011
Includes() function changed for Microsoft Internet Explorer compatiblity
Resolved in Pega Version 8.4
The complete screen was not loading due to "includes()" not being supported in Microsoft Internet Explorer, resulting in a console error and the flow breaking. To resolve this, ".includes()" has been changed to indeOf.
SR-D57278 · Issue 519461
Padding added to keep sort icon always visible in Google Chrome
Resolved in Pega Version 8.4
When sorting a grid column on Google Chrome, the sort icon was missing if the header label was large. This was traced to the Sort icon being handled as a background image of 12px in width inside 'display:table-cell' which was forced to shrink by the resize. To resolve this, 'padding: 0 6px;' has been added to each side to keep the space intact for the sort icon to always be visible.
SR-D57629 · Issue 532493
Navigation sub menu shows all options
Resolved in Pega Version 8.4
The switch app menu was running off the bottom of the screen, and using arrow keys to navigate it caused the whole portal to jump up. This was traced to the sub-menu style attribute 'top' being changed to '0' if it was given a negative value. To resolve this, a condition was added to check whether the rendering sub-menu height is greater than viewport, and adjust the top attribute value accordingly.
SR-D61860 · Issue 523584
Preflight Optimization styling now handlies right-to-left language packs
Resolved in Pega Version 8.4
When using Preflight Optimization on a generated app with the AR (Arabic) locale, Pages rendered in Right-to-Left (RTL) mode did not have the proper styling or placement for the radio button target and text. The same app rendered correctly when using an empty (default to EN - English) locale. Investigation showed that Preflight Optimization of CSS was failing when using Right-to-Left (RTL) languagebecause the use of preflight bypassed all other CSS processing. To resolve this, the handling of Preflight's CSS Optimization has been updated to handle cases using a Right-to-Left language (ex: Arabic).
SR-D62361 · Issue 534811
Read-Only harness takes precedence over editable section with when condition
Resolved in Pega Version 8.4
Given a harness which was marked as Read Only and contained sections which were configured as editable based on some conditions, when the condition became true, the section became editable and ignored the read only conditions applied on the harness. Investigation showed that when a read-only 'when' rule evaluated to false, it rendered the layout in Edit mode instead of falling back to the read-only status of parent. This has been corrected by ensuring that when read-only evaluates to false, the system will fall back to the parent read-only status.
SR-D63416 · Issue 526523
Multi-select list control properly sets error message for server-side validation
Resolved in Pega Version 8.4
When using the Multi-select list control, client-side validation was working as expected but server-side validation was creating the Property-Set-Message error at Form level rather than Field level. This has been corrected.
SR-D64694 · Issue 533963
Check added for Turkish locale in Firefox
Resolved in Pega Version 8.4
When using Firefox in the Turkish locale, attempting to open worklist subsets or edit tables in a modal dialogue caused the browser to hang. This was traced to the character conversion process in the browser and has been resolved with the addition of a check.
SR-D65086 · Issue 526597
Harness context will be stored to handle on click executed outside of the Ajax Container
Resolved in Pega Version 8.4
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-D65917 · Issue 528109
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-D66387 · Issue 530843
ReloadSectionsCache handling improved
Resolved in Pega Version 8.4
Change Tracker was reporting changes properly and ExpressionEvaluator logic identified the correct DOM element related to layout refresh, but the refresh was not getting triggered due to _isInvalidRefresh logic. This was traced to reloadSectionsCache not being optimally maintained, and has been resolved by updating reloadSetionCache to avoid unnecessary reloads and only update the cache after a reload section is completed.