SR-D19083 · Issue 490402
Autocomplete list resets to top of scroll if selected data is deleted from the control
Resolved in Pega Version 8.3.1
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-D15844 · Issue 496775
Flag set for using defer load context switching with Microsoft Internet Explorer
Resolved in Pega Version 8.3.1
Defer load section was not working as expected due to Microsoft Internet Explorer 11 not maintaining the context of the section during busyIndicator hide. To avoid this, a flag 'pega.ctxmgr.skipContextSwitching' will be set during the hide of busy indicator if Microsoft Internet Explorer is used, and the harness switching context will then be decided based on this flag.
SR-D17568 · Issue 498409
Handling added for interaction portal refresh containing many data parameters
Resolved in Pega Version 8.3.1
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-D18960 · Issue 499909
Logic updated to resolve busy indicator delay
Resolved in Pega Version 8.3.1
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-D19177 · Issue 492338
Mashup refined to not trigger resize from popup
Resolved in Pega Version 8.3.1
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 495838
Corrected embedded section inside dynamic layout group becoming read-only
Resolved in Pega Version 8.3.1
When using a nested sections structure in a Dynamic Layout Group (tab), the fields inside the layout group were becoming read-only. 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 494515
Handling added for exceptions related to IE11 grid cleanup
Resolved in Pega Version 8.3.1
Numerous exceptions generated from IE11 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-D23174 · Issue 499567
Check logic added for change in datetime
Resolved in Pega Version 8.3.1
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.
SR-D23340 · Issue 497605
Calendar begins with Saturday in the Arabic locale
Resolved in Pega Version 8.3.1
When using the Arabic locale, the week was not starting on Saturday as expected, but was showing Thursday as the first day. This has been corrected.
SR-D24083 · Issue 498486
Guardrail warning removed for setting filter by format on RD sourced grid
Resolved in Pega Version 8.3.1
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.