SR-A90755 · Issue 263310
Restored nested sections visible in Designer Studio
Resolved in Pega Version 7.2.2
When trying to restore a earlier check-in version inside a nested layout, the restored section was corrupted i.e., the elements inside the dynamic layout (repeating grid) were not visible in the Designer Studio even though they did display as expected at runtime. 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.
SR-A87242 · Issue 255987
Removed secondary encoding in GetLocalizedValue checkbox
Resolved in Pega Version 7.2.2
When using a field value that referenced the GetLocalizedValue control to populate the caption of a checkbox, special characters were encoded on the UI. This behavior did not occur for simple labels. This was due to a second encoding step which has now been corrected.
SR-A77023 · Issue 257680
Fixed Firefox Checkbox onclick events triggering when not clicked
Resolved in Pega Version 7.2.2
When using Firefox, clicking in between the label and checkbox captured the target as span. Data-click actions were configured to trigger with this click, but the logic to toggle the checkbox value on click was missing. This has been corrected in ui_events on clickHandler.
SR-A77023 · Issue 255255
Fixed Firefox Checkbox onclick events triggering when not clicked
Resolved in Pega Version 7.2.2
When using Firefox, clicking in between the label and checkbox captured the target as span. Data-click actions were configured to trigger with this click, but the logic to toggle the checkbox value on click was missing. This has been corrected in ui_events on clickHandler.
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.