SR-D17568 · Issue 498412
Handling added for interaction portal refresh containing many data parameters
Resolved in Pega Version 8.4
Attempting to refresh the browser when there were interactions opened in the Interaction portal and a huge amount of data on the parameter page caused the screen to blank and the interaction content was not displayed. Investigation showed that as part of the refresh, the displayOnPage GET request was sent with all of the parameters in the parameter page (data-model), resulting in a 400 Bad Request due to the browser URL length limitations. This has been resolved by removing the parameters which are not actually required for the displayOnPage GET call during the refresh case.
SR-D17919 · Issue 491582
Corrected thread switching when moving between interactions tabs
Resolved in Pega Version 8.4
When using Create New for a Phone Call-Consumer in one tab and Create New for an Outbound Phone Call on another tab, the thread was not changing when switching between the tabs of the interactions. Closing the Outbound call interaction resulted in null pages on the clipboard. This has been resolved by updating the pzpega_ui_doc_tabsupport file so it switches to root document context if called from onActivate function using a flag.
SR-D18200 · Issue 492100
Whitelist security added to getDataPage API
Resolved in Pega Version 8.4
In order to secure data pages that may be exposed through using Global Resource Settings with the pega.api.ui.actions.getDataPage API, logic has been added to expose only mentioned data pages from the clipboard through pyPublicDataPageWhiteList.
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.