INC-137818 · Issue 594023
Corrected sorting icon accessibility when grid size is not fixed
Resolved in Pega Version 8.5.2
After configuring a table and checking the boxes for Filtering and Sorting and unchecking the fixed (pixel) size grid box, tabbing in to the grid/table using the keyboard did not bring the focus to the sorting icon /header, but instead the focus went to the filter icon. If filter was unchecked and sorting was checked, the focus went to the first row of the table. This was traced to the column headers missing the tabindex attribute when the column headers were not fixed. When the column headers were fixed, tabindex =0 was present for the column header and the sort icon was accessible. This was traced to the Freeze Header value not being updated according to Fixed Size value because it was not a fixed size grid. To resolve this, an extra condition has been added in GenerateCellContent Rule-Utility-Function to be used while checking the Freeze Header.
INC-137966 · Issue 597740
Embed-ReportFilter supports pyDateproperties
Resolved in Pega Version 8.5.2
After creating a report definition with Date time filter values where the 'from' date and 'to' date are input and propagated as “pyStartDateTime” and “pyEndDateTime” in the clipboard, opening the pyDate properties from clipboard resulted in a 'rule not found' exception. No properties of other data types generated the error. This has been resolved by creating the pyStartDateTime,pyEndDateTime and pyDisplayTimeperiod properties in Embed-ReportFilter to support this use.
INC-138309 · Issue 591148
Added busy state reset to reenable buttons after custom frame cancel
Resolved in Pega Version 8.5.2
When using a custom iFrame in a section that called a third-party URL, clicking on cancel for the popup "Do you want to stay on this page or leave it?" caused the screen to freeze. This was traced to the cancellation of the dirty page setting a busy state which disabled all the buttons and did not have a path to recovery. This has been resolved by updating the busy state so it will reset when the user chooses to cancel the changes and reenable all the buttons.
INC-138354 · Issue 594353
Third party cookies reminder added for Mashup in incognito browsers
Resolved in Pega Version 8.5.2
When working in incognito/private browser windows, attempting to use Mashup displayed a message indicating login credentials were not recognized ("Unknown password and/or username"). This was due to recent changes originating with the browsers regarding blocking third-party cookies which are necessary for Mashup to run. For informational purposes, a new API has been added which will check for the PegaRules cookie; if the cookie is not present, the message "Third party cookies must be enabled for Mashup to function." will be displayed. This message may be customized by configuring the setting "pega.web.config.xCookiesDisabled" with the required message.
INC-138672 · Issue 593279
Corrected size of Session Timer modal window
Resolved in Pega Version 8.5.2
The session timer modal dialog window did not have the correct height. This has been resolved by increasing the height of the logoff timer modal dialog from 210 to 236 in the desktop_showTimeoutLogoffDialog method of the pega_desktop_appcontrollerlite.js file.
INC-138701 · Issue 596613
Multi Select populates values for Page group
Resolved in Pega Version 8.5.2
The Multi Select control was not populating values when Page group was chosen as a source. This has been resolved by updating control_multiselect and pzgetACdata to support page group source.
INC-138803 · Issue 591924
Mouse event Cross-site scripting updates
Resolved in Pega Version 8.5.2
Cross-site scripting protections have been added to mouse event attributes.
INC-138877 · Issue 589533
Filter range decimals persist for German locale
Resolved in Pega Version 8.5.2
When using German localization, filtering values in Dashboard caused the entered decimal value range (13.00 - 50.55) to lose the separator and become a whole number (1300 - 5055). This has been corrected.
INC-138968 · Issue 594167
ARIA landmarks added to put dynamic layout in tab order
Resolved in Pega Version 8.5.2
As part of W3 accessibility specifications, ARIA landmarks have been added to dynamic layouts to direct tabbing focus. If the role type is "landmark" or "document", tabindex=-1 will be added, and for component widgets tabindex=0 will be added unless it is a non-focusable element like Alert, log etc.
INC-139023 · Issue 591163
Tab will exit portal side menu
Resolved in Pega Version 8.5.2
It is expected that the Tab key will take users out of the portal menu and to the next focusable element, but on the side navigation menu both tab and arrow keys moved to the next menu item. This caused users to have to navigate the entire menu. The correct behavior was seen for the Navigation rule when called from an Action (for example on the button). This was traced to the system using tabindex as "0" for every element in the menu, and the tabs code has been updated to exit out of the menu bar when pressed.