SR-D93564 · Issue 557262
Corrected screenflow CSS precedence
Resolved in Pega Version 8.4.2
After upgrade, the screen flow navigation chevrons were not displaying correctly due to the screenflows CSS styling not taking the correct precedence in the markups. This has been resolved.
SR-D96061 · Issue 562601
Localization added for "Preview"
Resolved in Pega Version 8.4.2
Support has been added for localizing the text "Preview".
SR-D98614 · Issue 559863
Parent and child case links resolved for Cosmos
Resolved in Pega Version 8.4.2
After upgrade to v8.4, a behavior change was seen in creating a child case (Add Work) from a Parent case when using an application built on the Cosmos theme. Items such as pyWorkCover Page and CoveredInsKeys were missing, Data Propagation from the parent case to the child case was not working, the Child case max Instance configuration was not being applied, and when the child case was created from Add work, the child case appeared in an unexpected popup. This was traced to work done to implement a feature of creating subcases in a dialog (using a tertiary AJAX container) which was missing handling for a target parameter used for the child case clipboard, and has been resolved.
SR-D65174 · Issue 560603
SetInterval will increase when AQD delay is defined
Resolved in Pega Version 8.4.2
With a 5000ms delay in place, executing scenario test cases resulted in errors such as values sporadically not being entered in their respective fields when the test was run, test runs that failed even though the data was entered as expected, or the submission of a test case assignment (Next button) executing the next step before the new screen was loaded. Investigation showed this issue was occurring when the system encountered a slower machine and a delay in loading pages, and was traced to the executor not waiting long enough due to the implicit setInterval of 8 seconds. It was possible to add a local delay in AQD settings for slow pages, but the system-set setInterval interfered with this delay. To resolve this, changes have been made to the executor module where setInterval is invoked that will increase the setInterval time when AQD delay is defined, so that setInterval will not interfere with a locally-set AQD delay.
SR-D68328 · Issue 557752
Unload handler added for use with custom popups
Resolved in Pega Version 8.4.2
A memory leak seen in Microsoft Internet Explorer was traced to a custom script to close windows which bypassed window unload and continued to hold some objects in memory. This has been resolved by introducing a new file which will load only for popup harnesses and which registers the unload handler to remove the popup window references.
SR-D75421 · Issue 552438
Parameters added to protect font size in HTML to PDF conversion
Resolved in Pega Version 8.4.2
Pega uses the pd4ml external library for HTML to PDF conversion. As part of this, the adjustHTMLWidth API was called to avoid truncation issues, but this resulted in font-sizes not being preserved in the exported document but rather changed as necessary to fit in the PDF. In order to support preserving the font size during export, the pyPDFSettings datatransform will call the protectPhysicalDimensions API along with setHTMLWidth, and avoid calling adjustHTMLWidth. With this change in place, any content width should not be set explicitly to some value as it may lead to truncation if the space is not sufficient. If there is no width set, text will wrap automatically. In case of tables with large number of columns, truncation issues may be seen: to avoid such issues, pass a larger htmlWidth value so that table will be reduced in size and in the rest of the page, font-sizes are preserved.
SR-D78557 · Issue 551842
Check added before generating aria-label
Resolved in Pega Version 8.4.2
To improve accessibility, logic has been added to dynamic layout generation that will check whether the text value is empty, and if so an aria-label will not be generated.
SR-D80572 · Issue 558413
Refresh-Other section correctly shifts focus on tab out
Resolved in Pega Version 8.4.2
After upgrade, a difference was seen in the behavior of the Refresh-Other section action functions. Previously, focus was shifted to the next field when tabbing out, which is the desired behavior. Investigation showed that this was a result of modifications made to resolve other focus issues, and the previous behavior has been returned by updating the conditions used to call the "focusNextElement" method to include a check whether the reloadElement is stale, and to get the focusElement from DOM based on name (pega.util.Dom.getElementsByName(focusElemName)) if needed.
SR-D83476 · Issue 550787
Layout Group (Tab) keyboard navigation behavior made consistent
Resolved in Pega Version 8.4.2
When using keyboard navigation for Layout Groups (tab), arrow keys (up/down/left/right) are used to navigate the tabs once focus is set on the first tab, and the tab contents of each tab is opened automatically. It was noted that pressing tab a few more times caused the second tab to gain focus, but the contents of the tab did not open automatically or when enter was pressed, which was unexpected behavior. For accessibility best practices, tab focus should not be allowed on tab groups. To resolve this issue, this has been removed and the system will continue to follow auto activation of tabs on arrow keys.
SR-D84126 · Issue 545039
Resolved delegated data type exception for new line character
Resolved in Pega Version 8.4.2
After delegating two data types to certain access groups, the data type appear with the specified detail in the case manager portal under the configurations tab but the exception "Class not defined in dictionary" appeared when the edit button was clicked. This was related to the handling for parseJSON, and has been resolved by adding handling for escaping new line characters in the catch block of correctActionArgs method inside the ui_events file.