SR-A81527 · Issue 254654
Unlocked rulesets for UI-Kit-7 and Pega-Desktop
Resolved in Pega Version 7.2.2
When using UI tollgate, the message 'Sentence case is not followed' would sometimes appear due to no unlocked rulesets being available in UI-Kit-7 and Pega-Desktop. In order to facilitate the UI issues pass, the rulesets have been made available.
SR-A69128 · Issue 252454
SmartInfo updated to properly retain or advance focus on mouse position
Resolved in Pega Version 7.2.2
Whenever the mouse pointer hovered out of a text field with 'ReadWriteSmartInfo' option configured, the focus in the text field was not visible and it was not possible to make edits. This was an unintended consequence of SmartInfo applying focus to the next focusable element for the purpose of accessibility reading out the contents. In order to better handle this scenario, pzpega_ui_smartinfo.js has been updated so that Smart Info configured on hover will retain focus on the same element while Smart Info configured on focus will move toward the next element in order to avoid a cycle.
SR-A100724 · Issue 268499
Resolved cascading error messages in case work user portal
Resolved in Pega Version 7.2.2
Whenever there were error messages seen on the UI of the case work user portal, taking any action on that screen (e.g. delete /save/submit) caused the number of error messages to increase every time. This was caused by a harness issue relating to isAncestor, and has been fixed.
SR-A76831 · Issue 255486
Grid headers show "Required" when PegaWAI enabled
Resolved in Pega Version 7.2.2
With PegaWAI enabled, grid headers marked as required were displaying the noncompliant '*' label instead of the accessibility-enabled 'required' label. This was due to missing styles for table headers and has been corrected.
SR-B6425 · Issue 270890
Scrum Board chicklet error resolved
Resolved in Pega Version 7.2.2
After collapsing and expanding a user story chicklet in the Scrum Board, adding a new note to the user story would cause the user story chicklet to disappear. This was a rendering issue due to an error in the type property syncing with the level property, and has been fixed.