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.
SR-D67360 · Issue 527679
Bottom and right custom borders appear as expected
Resolved in Pega Version 8.4
After enabling editing of the default table format and then giving a format for the bottom and right borders, the borders did not appear. This was caused by code that was overriding the new configuration, and has been resolved.
SR-D71105 · Issue 532191
Corrected error when using CharCounter in non-template mode
Resolved in Pega Version 8.4
An error message was generated when trying to save a section with the TextArea's Display CharCounter set to True. This was traced to an error in the remaining character count span generation for non template mode and has been corrected.
SR-D71402 · Issue 532333
Localization added for Pega Call Login screen
Resolved in Pega Version 8.4
Localization has been added to the label "Value can not be blank" on the Pega Call Login screen.
SR-D71756 · Issue 533551
Thread Cleanup error resolved
Resolved in Pega Version 8.4
After upgrade, intermittent exception errors were being generated by the FreeClipboard activity when switching between applications. This was traced to specific use-case issues with Thread Cleanup, and has been resolved.