INC-145263 · Issue 600036
Query logic modified for Anypicker
Resolved in Pega Version 8.5.2
A search for results in the Anypicker control for the first time showed the results, but if the results were deleted and the search run again without focusing out from that field, no results were found for the second search. This has been resolved by using slice than splice in the query to avoid mutating the original array source.
INC-145535 · Issue 600785
Corrected layout group overlapping content
Resolved in Pega Version 8.5.2
When an editable Table with Master Detail Edit has a section that contains a Layout group (Tab) inside the Master Detail Flow Action, if there are more layout group headings than that can be contained in the screen, a left and right arrow are displayed to toggle between headings in the layout group heading bar. However, timing issues sometimes caused the contents of the layout group to overlap on top of the content below the layout group and the screen was freezing with a loading icon. This was traced to console errors, and has been resolved by adding an 'undefined' check to prevent those errors.
INC-146237 · Issue 608744
Corrected popover scroll for AnyPicker
Resolved in Pega Version 8.5.2
Using the AnyPicker control caused display problems. In the initial display of the selection list, the line of choices and the search field overlapped and they were displayed from the second line of choices which forced the user to scroll up to see the first line. After displaying the selection list, clicking outside the selection list without selecting anything to close the list and then displaying the selection again caused the options to be displayed from the 4th line, requiring a scroll up to see lines 1 to 3. This has been resolved to ensure the Scroll on Popover goes to the first element.
INC-146262 · Issue 603689
Handling added for new doc.write with Google Chrome 85
Resolved in Pega Version 8.5.2
Document.write was not working as expected on Google Chrome 85 due to the DOM elements not being updated. This has been resolved by updating the code to do doc.write by checking the if the document body has no child nodes in a time out.
INC-146429 · Issue 602290
Disabled control status made accessible to JAWS
Resolved in Pega Version 8.5.2
When using the Security Event Configuration page (tab) within Pega Dev Studio, the link elements used for 'Select All', 'Clear', 'ON' and 'OFF' were not providing the current State of the element to JAWS. In template rendering of Link control with a 'disable when' condition (server-side evaluation), when the control is disabled it was still accessible and screen readers were not reading the link as disabled. This has been resolved by adding tabindex="-1" and aria-disabled="true" for disabled Link control.
INC-146572 · Issue 603294
iniGadgets updated to support jQuery with Mashup
Resolved in Pega Version 8.5.2
Mashup gadgets were not loaded during browser refresh when the host page had a jQuery in it. This issue occurred while trying to find the gadget divs. There is an 'if' condition to check if $ is available in initGadgets method. In this scenario, this 'if' block was getting executed and mashup gadget divs were returned as empty. As a result. mashup was not getting loaded. This has been resolved by updating the iniGadgets method to check for jQuery instead of $.
INC-148115 · Issue 605421
Autocomplete results list position scrolls inside a table
Resolved in Pega Version 8.5.2
Given a row editable table with a fixed height and freeze grid header, when autocomplete was included in a row of a table and the down-arrow was pressed to get the list of options in dropdown, this drop-down popup was not moving along with the row during scrolling. This was due to scroll handler not being triggered for popover when inside a hierarchical table, and has been resolved.
INC-148237 · Issue 605846
Autocomplete markup handles control format style names with spaces
Resolved in Pega Version 8.5.2
After creating the format 'Standard Gray Background' in the skin rule to change the back-ground color for an auto_complete field and using it in a presentation tab for Control-format input, the field was not updated with the background color as expected. This was due to the Autocomplete control only replacing the first space in the control format name with underscore ( _ ), causing the formatting to not be accepted. While there was a workaround of providing a name without spaces or using a name with only a single space, this has now been resolved by modifying the autocomplete markup generation so all the spaces in a control format style name are replaced instead of only the first space.
INC-148303 · Issue 606795
doRDLAction activity registered for BAC validity
Resolved in Pega Version 8.5.2
Users were unable to see more than the 10 most recent pulse posts because of a security alert (SECU0019) being thrown when the 'Show More' link was clicked. Investigation showed the error was coming from the PegaGadget-Feed.pyRDLPaginator section: "pzdoRDLAction" is part of non-template rendering, and pagination will use "pzdoRDLAction" activity whenever paginator is used in a non-template section. Because of this, it must be registered for BAC security to accept it and pass through, and this has now been done to resolve this issue.
INC-148375 · Issue 607796
"Today" will set date-time in the respective operator timezone
Resolved in Pega Version 8.5.2
When a Date was entered using the "Today" option in Datetime control, the Date set used the system date and Time was taken from Timezone specified for the operator. This created issues for a scenario such as operator being set to America/New_York/ EST while the application was accessed in another country such as India or Japan. This was a missed use case and has been resolved by adding code to get the date-time in the respective operator timezone and setting it on click of date-time controls.