SR-A90790 · Issue 262061
Layout group tab focus issue fixed
Resolved in Pega Version 7.2.2
he user is having a tabbed layout group, by imposing If visibility when conditions were imposed on a tabbed layout group such that only one tab was visible in Section pyCaseContent, the default Information tab did not receive focus upon completion of the assignment and all of the information was not rendered after a manual focus click. This was an error in the expand indication parameter value handling for the tab layout group, and has been fixed.
SR-A101626 · Issue 272644
Height properly set for opening report in Portal
Resolved in Pega Version 7.2.2
Height was not being properly set when opening a report in the harness due to the resize function incorrectly handling expanded items. This has been fixed.
SR-A90621 · Issue 259615
Navigation highlighting fixed for items on horizontal menu
Resolved in Pega Version 7.2.2
Highlighting was not working correctly on a horizontal menu. On clicking on the first menu, the correct window opened and was highlighted, but when opening the subsequent menus, highlighting appeared for a fraction of a second and then disappeared. This was an issue with focus not returning back and not highlighting items which were not first or last in the menu bar, and has been fixed.
SR-A98409 · Issue 270972
Smart Tip focus modified to check for Accessibility
Resolved in Pega Version 7.2.2
If a text area was set with Smart Tip and used a hover event and required validation, actually hovering over the area displayed the OOB error for required and any click moved the focus to the text area. This was an error in Smart Tip which always set the focus to the target element, and has been resolved with added code to set focus and set blur on the target element only when accessibility is enabled.
SR-A98409 · Issue 270057
Smart Tip focus modified to check for Accessibility
Resolved in Pega Version 7.2.2
If a text area was set with Smart Tip and used a hover event and required validation, actually hovering over the area displayed the OOB error for required and any click moved the focus to the text area. This was an error in Smart Tip which always set the focus to the target element, and has been resolved with added code to set focus and set blur on the target element only when accessibility is enabled.
SR-A76729 · Issue 252834
Page Messages not cleared by Tree grid
Resolved in Pega Version 7.2.2
If a Tree grid was configured to run a local action on click of a node and error messages were set by page-Set-Messages/property-set-messages is set, it was observed that these messages were reset or cleared on click on any node in the tree. This was due to the local action being executed which in turn called ProcessAction, and the Messages were reset in step 2. To prevent this unexpected behavior, the pzpega_ui_grid JS file has been updated.
SR-A94024 · Issue 264561
Resolved RTE spellcheck freeze with Microsoft Internet Explorer
Resolved in Pega Version 7.2.2
If spellcheck was invoked on an RTE file in a modal dialog while using Microsoft Internet Explorer , the reload harness was not being correctly triggered and the UI would freeze. This was due to the body event listeners not working in Microsoft Internet Explorer , and code has been added to remove the listener from the document body if the browser is Microsoft Internet Explorer .
SR-B1043 · Issue 270870
Resolved RTE with Microsoft Internet Explorer textarea update
Resolved in Pega Version 7.2.2
If spellcheck was invoked on an RTE text area when using Microsoft Internet Explorer , the next time text was entered and saved the new text was not preserved in the text area. This has been resolved with an added null check.
SR-A17941 · Issue 246609
Resolved maximized RTE tab blanking
Resolved in Pega Version 7.2.2
If the Rich Text Editor was opened and maximized in a modal window tab using a dynamic container, navigating away and returning to the tab resulted in the RTE tab being blank. This was an issue with the resize function relating to Quirks mode, and a check has been added to resolve the problem.
SR-A88892 · Issue 266454
Restored nested sections show repeating grid header
Resolved in Pega Version 7.2.2
In a section that has repeating grids configured, rule check-out and check-in caused the repeat grid headers and cells to disappear in Designer Studio. Analysis showed that when a rule was deleted from a section with nested layouts, only the properties which had values were committed to the database. On restoring the rule, only committed properties were re-created on the section XML, leaving the XML incomplete and generating an error and layout rendering failure. To fix this, the pzpega_ud_gridlayout_structure JS has been updated to handle the non-existence of empty nodes and initialize them.