SR-A94633 · Issue 261954
Mouse clicks work on touchscreen/mouse combo devices
Resolved in Pega Version 7.2.2
When using Google Chrome with a touchscreen and mouse combination, some click events such as Calendar date picker were not working when using the mouse. This was due to MenuSystem not using the generic isTouchable API, and this has been updated.
SR-A92781 · Issue 264233
Fixed date format in en_GB locale
Resolved in Pega Version 7.2.2
When using locale en_GB, the date format of the fields was displaying in the wrong date format. The pyCustDateTime parameter was set for custom datetime format, but this was not getting cleared after getting the formatted value and then being incorrectly used for the next DateTime control. This has been fixed by clearing the pyCustDateTime parameter in the pzGenerateFormat RUF after calling formatter RUF.
SR-A23891 · Issue 252255
Resolved busy indicator attached to incorrect iframe
Resolved in Pega Version 7.2.2
When using Microsoft Internet Explorer , adding a grid row to a flow action form and then clicking a configured 'Finish Assignment' caused the busy indicator to appear and spin indefinitely. This was caused by how the Microsoft Internet Explorer browser handled nested frames: an inner iframe form submit adds the busy indicator to the outer iframe, but the outer frame did not gets hide / refresh on form submit. This has been fixed with the addition of a target element that will attach the busy indicator to the inner iframe instead of the parent frame.
SR-A92015 · Issue 260437
MobileSnapStart portal works with OpenWork
Resolved in Pega Version 7.2.2
When using pyMobileSnapStart and openWorkByHandle, the portal was displaying along with the case. However, any portal action that went through OnDesktopAction failed even though actions within the case were working. This was an issue with Portal actions not working when using openWork, and has been fixed with an added null check for docsRecreateInfo in dynamiccontainer_lite js to handle pyMobileSnapStart cases.
SR-A22230 · Issue 245989
Focus corrected for auto-complete fields in Microsoft Internet Explorer 11
Resolved in Pega Version 7.2.2
When using the Microsoft Internet Explorer 11 browser, selecting the value for an auto-complete field caused the cursor to move to the next field and then return to the first field. This was an issue with the focus and on-change refresh within the dynamic layout, and has been fixed.
SR-A22230 · Issue 244700
Focus corrected for auto-complete fields in Microsoft Internet Explorer 11
Resolved in Pega Version 7.2.2
When using the Microsoft Internet Explorer 11 browser, selecting the value for an auto-complete field caused the cursor to move to the next field and then return to the first field. This was an issue with the focus and on-change refresh within the dynamic layout, and has been fixed.
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.