SR-D18960 · Issue 499912
Logic updated to resolve busy indicator delay
Resolved in Pega Version 8.4
On click of submit in the main interaction flow, the busy indicator was not getting displayed or was displayed after a delay whenever there were a series of Ajax requests being made. The logic has been updated to resolve this issue.
SR-D19083 · Issue 508092
Autocomplete list resets to top of scroll if selected data is deleted from the control
Resolved in Pega Version 8.4
If an autocomplete on Screen did not initially have any input, pressing the down arrow showed the popover data with the scrollbar on the top. Scrolling down and selecting an item from the autocomplete suggestions and then tabbing out closed the popover. If the data was then deleted from the control and the down arrow was pressed again, the popover suggestion showed the data in the last scrolled position instead of restarting from the top as expected. Investigation showed that when autocomplete used a list configuration, the popover div was not being updated if the data was deleted from the control. This has been corrected.
SR-D19177 · Issue 492341
Mashup refined to not trigger resize from popup
Resolved in Pega Version 8.4
The parent window was being refreshed when an action was performed on the child window or the child window was resized from the mashup script. This has been resolved by altering the logic to avoid triggering resize from popups in a mashup scenario.
SR-D19801 · Issue 495841
Corrected embedded section inside dynamic layout group becoming readonly
Resolved in Pega Version 8.4
When using a nested sections structure in a Dynamic Layout Group (tab), the fields inside the layout group were becoming readonly. This has been resolved by ensuring the controls present in second-level nesting onwards obey section read-only value in a dynamic layout group, and resolving the 'when' rule that governs the disabledwhen of link for all sections in a section include.
SR-D21332 · Issue 494519
Handling added for exceptions related to Microsoft Internet Explorer 11 grid cleanup
Resolved in Pega Version 8.4
Numerous exceptions generated from Microsoft Internet Explorer 11 related to pzPega_ui_grid were traced to a browser difference in timing logic related to grid cleanup. This has been resolved by adding a check to determine whether the grid is inside a defer-loaded section.
SR-D22219 · Issue 491446
Dropdown UI CSS corrected
Resolved in Pega Version 8.4
An issue with incorrect generation of the Dropdown UI CSS has been resolved by directing the Preflight Crawler to the field holding the CSS Format.
SR-D22225 · Issue 504357
Added handling for iPad special characters in any key event
Resolved in Pega Version 8.4
When using an iPAD, there were 5 characters that were not caught when typed by the anykey event on a text control that was supposed to take only numeric data. The control worked as expected on iPhone. Investigation showed that the Keycode is 0 in the event object for some special characters with the iPad, and this has been resolved by using key instead of depending on keycode for those special characters.
SR-D2272 · Issue 486163
RDL updated to ensure unique ID generation
Resolved in Pega Version 8.4
An Android hybrid mobile app was showing data on the UI which did not match with the data available in pyWorkPage. This was traced to the use of timestamps for ID generation, and has been resolved by updating RepeatingDynamicLayoutAssembly Java to ensure unique ID generation.
SR-D23036 · Issue 500574
XSS protection added to paragraph rules
Resolved in Pega Version 8.4
XSS filtering has been added for property references in paragraph rules.
SR-D23174 · Issue 499570
Check logic added for change in datetime
Resolved in Pega Version 8.4
After selecting a valid date in the calendar UI, clicking outside of the DateTime control caused the date to disappear when using the Microsoft Internet Explorer browser. Investigation showed that the order of events execution is different in Microsoft Internet Explorer and Google Chrome, so that by the time the getReadOnlyFormatting method was called, the data-changed attribute had already been updated to 'false'. This caused the read-only formatting to not be applied so the data-display-value was considered to be empty. To resolve this, a check has been added to better detect the change so that read-only formatting gets applied.