SR-D23417 · Issue 493544
Image Attachment File Type error localized
Resolved in Pega Version 8.4
Localization has been added to the error message generated when an unsupported image is uploaded while in live-chat.
SR-D24083 · Issue 498489
Guardrail warning removed for setting filter by format on RD sourced grid
Resolved in Pega Version 8.4
After upgrade, use of the 'filter by format' (Configuration on table layout column) for grids sourced with report definition caused confusion in that the option now exists to either to see the value or the formatted value in the filter panel. Previously, a grid layout would show a date format in both the column of a grid and the filter of that column, but the filter changes produced a date format on the column within the grid but the date time format applied on filter of the column. This behavior change will be reflected in updated documentation. In addition, there is a workaround to recreate the old behavior by changing the column 'Date assigned' from a filter by value to format, but a moderate guardrail warning was created when filter by format was set on any column of a grid sourced to a report definition. This has been removed: when filter by format is selected, no guardrail warning will be displayed in design time.
SR-D24318 · Issue 494060
Dom API updated to resolve Microsoft Internet Explorer 11 not loading async data with refresh when calling an activity
Resolved in Pega Version 8.4
The browser was continuously showing "loading" if Microsoft Internet Explorer 11 was used for a section which was sourced from a data page and configured to load the data asynchronously from a external service while calling an activity and using a 'refresh when' rule to refresh the section if a property changed. Investigation showed that the initial data load was successful and the section with the data was visible, but if the property changed and the section loaded once again due to the 'refresh when' condition, the browser was unable to render the defer loaded section case because the dom returned had the wrong value. To resolve this, the API used to check for the dom element has been updated.
SR-D24682 · Issue 501080
Added check for undefined targetTD in repeating tab layout
Resolved in Pega Version 8.4
Given a repeating tab layout and a validation on the flow action which used edit validate, clicking on the next button set an error on the page. Putting in the correct data and clicking the next/submit button a second time resulted in a console error indicating the targetTD was undefined for the markSectionTabErrors function in pzpega_ui_doc_tabsupport. This has been resolved by adding a check for the undefined targetTD.
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.