INC-151401 · Issue 615716
Context set for progressive scroll load of dynamic layout
Resolved in Pega Version 8.4.4
When setting pagination as 'Progressively load on scroll' for a repeating dynamic layout in a section with pagelist as the source, scrolling resulted in a null pointer exception and no further scrolling was possible. The issue was not seen when 'Progressively scroll on user action' was used. Investigation showed the activity Reload Section was failing because of the failure in the pre-processing activity, and this has been resolved by setting the correct context before making the pagination call.
INC-151418 · Issue 610229
Authentication updated for legacy activities
Resolved in Pega Version 8.4.4
Authentication updates have been made for several legacy activities invoked via URL by custom HTML.
INC-150188 · Issue 608937
Added API to ensure correct desktop window is found for test cases
Resolved in Pega Version 8.4.4
In Dev Studio scenario-based testing, Test Suite and Test Case were not able to execute the "Complete Task" button on review screen and the "Submit" button on Case screen. This was traced to the desktop window not being correctly found due to recent changes in the way the App studio and Dev studio are rendered in the iframe, and has been resolved by adding the API 'getSTPortalWindow' in pega_desktop_support to identify the correct window.
INC-151716 · Issue 618440
Resolved Screenflow overflow
Resolved in Pega Version 8.4.4
Screenflow bread crumbs were overflowing out of the action area when more than 10 assignments were configured. An error in the console indicated the navigation.navigate function was not defined. This behavior was observed in general when a screenflow was called from another screenflow and 'enable navigation links' was set on all assignments in the screenflows, and the issue has been resolved by updating the implementation.
INC-151858 · Issue 610351
Updated currency decimal precision
Resolved in Pega Version 8.4.4
Hungarian and Taiwanese currencies were previously hardcoded to use zero decimal precision. In order to be compliant with the current ISO-4217 standards, these currencies have been updated to be precise to two decimal places.
INC-151952 · Issue 609339
Expand Pane icon responds to enter key when using JAWS
Resolved in Pega Version 8.4.4
In an Operator ID rule in Dev Studio, pressing the Enter key when focused on an Access Group expand icon caused the focus on the page to move to the top of the Contact Information frame (top left corner of the Frame). The only way to use the enter key to expand the pane without the refocus was to tab to the arrow icon and then tab a second time before pressing enter. This was traced to the expand caret icon being focussed twice due to the tabIndex for both the TD and SPAN elements holding the caret icon: TD had a focus element for accessibility of the grid, and SPAN had it for the expand pane accessibility. This has been resolved by adding a check condition before adding tabIndex to the first cell in the Grid.
INC-152084 · Issue 620951
Handling added for cross-origin DOM exceptions
Resolved in Pega Version 8.4.4
When an openURLWindow action was used to open any other domain, DOM exceptions were generated related to cross-origin iFrames communication and the UI became unresponsive. This has been resolved.
INC-152171 · Issue 610974
Unused query parameter cleaned up from harness
Resolved in Pega Version 8.4.4
Recent testing showed a legacy 'encodedPassword=true' query parameter lingering after changes were made to convert harness actions. Although there was no security implication as no sensitive information was being sent, this unused query has been removed.
INC-152340 · Issue 610910
Scrollbar consistent on switching between grids in tabs
Resolved in Pega Version 8.4.4
On switching between two grid tabs configured in a layout group of tabs, the scrollbars intermittently disappeared or doubled. This was traced to the initscrollbars function being called multiple times and adding hScrolldiv and vScrolldiv each time. To resolve this, the logic has been updated to recalculate the position style.
INC-153025 · Issue 614693
Updated table field Minimum Character validation
Resolved in Pega Version 8.4.4
The Minimum Character validation for the Table field was not working due to minchars and validationtype attributes not being populated in the markup. This has been corrected.