SR-D41984 · Issue 510013
Added handling to correct '&' displayed as '&' in custom tab name
Resolved in Pega Version 8.4
When using a data transform and custom properties to set the tab title, clicking on a link containing "&" in the label opened a tab name which included "&" instead of "&". This has been resolved by modifying the handleGadgetLoad method in the pzpega_ui_dynamiccontainer file to handle the Cross Scripting FIlter and display the character.
SR-D42583 · Issue 514487
Label of a field is correctly rendered when a section is re-used with a visiblity condition
Resolved in Pega Version 8.4
The label of a field was not being rendered/visible when a section with a 'visible when' condition was re-used in different Page Contexts. The label was displayed correctly if 'Run visibility condition on client' was checked. As part of performance improvements made in a previous version, label generation was moved under the dlcellvisibility flag. Because of this, if a section was re-used at multiple places with different contexts and one place had visibility false and another had visibility true, the labels were not getting generated for the visible section. To resolve this, Label Generation has been moved out of dlcellVisibility to ensure label metadata will always be generated. Updated performance improvements have been made instead by way of a DSS setting (generateCellMetadata) so that when generateCellMetadata is true, the label generation will honor dlcellvisibility to generate the label metadata.
SR-D42701 · Issue 510923
XSS security added for Case Manager
Resolved in Pega Version 8.4
XSS security has been added to the Document features in the Case Manager portal.
SR-D43141 · Issue 512435
Support added for iFrame Mashup resize when using SPA
Resolved in Pega Version 8.4
After upgrade, issues were seen with an iFrame holding a Mashup not resizing as expected. This was traced to the use of an SPA portal inside mashup, and has been resolved by explicitly invoking the doharnessResize API to set proper height on iframe when using SPA.
SR-D43468 · Issue 511644
Includes() function changed for Microsoft Internet Explorer compatiblity
Resolved in Pega Version 8.4
The complete screen was not loading due to "includes()" not being supported in Microsoft Internet Explorer, resulting in a console error and the flow breaking. To resolve this, ".includes()" has been changed to indeOf.
SR-D43551 · Issue 511241
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-D43740 · Issue 512183
Added support for Helper Text Question Mark with visibility condition
Resolved in Pega Version 8.4
The Helper Text Question Mark was not displaying if the control was configured with "Help icon with overlay on hover" combined with a visibility condition. This was a missed use case, and the expression visibility support for controls.changes have now been added in the pzpega_ui_DLCellTemplate.js file.
SR-D44546 · Issue 512600
Corrected opening collapsible rows with modal action inside a nested pane grid
Resolved in Pega Version 8.4
After expanding the second level of a collapsible row in a table and then collapsing the row back down again, trying to expand other rows in the table did not work and the error "Unable to get property 'target' of undefined or null reference" appeared on the console. This was an issue with a modal action configured inside a nested pane grid that was attempting to call a target key on an undefined object, and has been resolved by explicitly checking for the existence of the 'event' object before calling the 'target' key on it.
SR-D44943 · Issue 527921
Handling added for mousdown triggers in Firefox dropdown and sutocomplete controls
Resolved in Pega Version 8.4
After recording a test case that includes entering data into an autocomplete, the data was not actually entered into the autocomplete when the test was executed but the test step was marked as successfully executed. Other tests for other similar autocompletes appeared to execute as expected. This was due to a mismatch between the sequences of events that are fired in the Google Chrome and Firefox browsers: the system is listening for a mousedown event to record a new step, but the browser-specific behavior is different. Google Chrome: mousedown focus click change Firefox: mousedown focus mousedown change As this difference in events order is browser behavior, code has been added that will handle the specific Firefox case where mousedown triggers on invalid target elements related to dropdown and autocomplete controls.
SR-D45101 · Issue 512529
Added support for Helper Text Question Mark with visibility condition
Resolved in Pega Version 8.4
The Helper Text Question Mark was not displaying if the control was configured with "Help icon with overlay on hover" combined with a visibility condition. This was a missed use case, and the expression visibility support for controls.changes have now been added in the pzpega_ui_DLCellTemplate.js file.