SR-D25012 · Issue 499854
Column filtering updated to better handle merged columns
Resolved in Pega Version 8.4
When filters were applied to a grid containing merged columns, the columns next to the merged columns did not have the filter class applied. This was traced to a calculation of the index in getFilteredColumnIndex function which did not consider the merge columns use case, and the uigrid js file has been updated to correct this issue.
SR-D25177 · Issue 500615
Filter popover positioning consistent for iPad
Resolved in Pega Version 8.4
Filter popover positioning was not consistent on iPad when "Enable support for responsive breakpoints" was disabled for the grid format. To resolve this, scrolled has been set to 'true' in the scroll event, and if client.left is 0 the system will use flippedX for left*/. Please note that making this appearance consistent may cause some repaint slowness in the iPad Safari browser due to a known CSS transition events issue with the browser.
SR-D25251 · Issue 493800
Added support for non-auto DisplayYesNo control
Resolved in Pega Version 8.4
A Change event on post value and refresh was not firing as expected in a section configured with a TrueFalse type property associated with a DisplayYesNo control. The same configuration worked correctly when used with a pxRadioButtons control. This was traced to non-auto control action JSON not generating on the second radio button(No) , and support has been added for this.
SR-D26101 · Issue 495208
Improved DX API page reference handling
Resolved in Pega Version 8.4
When using a property that was being referred through a secondary page that could be referred directly by the case (such as .AccountClosureDetails.ClosingAccountApplicant), the page was not initialized and the local list values were not returned by the DX API. This has been resolved by improving the handling for embedded page references via section include where the property reference is a full path.
SR-D26244 · Issue 501193
Label control XSS protection added
Resolved in Pega Version 8.4
XSS protection has been added to label control.
SR-D26784 · Issue 507136
Check added to ensure client side validation checkbox is honored in Case Worker portal
Resolved in Pega Version 8.4
When the "Enable client side validation" checkbox on the Perform harness was unchecked, the validation was still firing when using a tab out on the Case Worker portal. The validation did not fire on tab out in the Case Manager portal, and both portals worked as expected on Submit. This was traced to the validation being fired without checking the value of the bClientValidation property. To resolve this, a check has been added to ensure the validation is fired only when it is set to true.
SR-D27338 · Issue 496638
Calendar edit properly disabled when set to no text entry
Resolved in Pega Version 8.4
Clicking the input box of a date control used as Date+calendar popped up the calendar even when the calendar control was disabled and "Allow text entry" was set to No. If "Allow text entry" was set to yes, the entire calendar was disabled. To resolve this, the system has been updated to disable calendar control when 'Allow text entry' is selected to No in the presentation tab.
SR-D27776 · Issue 497007
Added support for Thai solar calendar
Resolved in Pega Version 8.4
Support for the Thai solar calendar has been added to the DateTime control.
SR-D28060 · Issue 505638
XSS protection added to Pega App Studio Spaces
Resolved in Pega Version 8.4
Ajax Request's callback success method has a mechanism to process the response object's HTML responseText, initiate and modify the changeTracker changes, and eventually call renderUI to render the DOM. However, the response object sometimes may return a different type (JSON) that may expose XSS vulnerabilities. To improve security for the Pega App Studio, the system will process the Ajax request's response text only if the response date type is not JSON by accepting a flag in the callback object passed by the caller.
SR-D28469 · Issue 499090
Corrected exceptions report appearing on user screen
Resolved in Pega Version 8.4
When "Break on all exceptions" was enabled, the exceptions report was visible on the end user screen when using Microsoft Internet Explorer 11. This has been resolved with updates to the 'pzpega_ui_dynamiccontainer' and 'pzpega_ui_doc_tabsupport.js' files.