SR-A20569 · Issue 238382
Mandatory date and amount fields validation performed before reset
Resolved in Pega Version 7.2.1
Date and amount fields changed to incorrect format if any mandatory field was empty and screen was saved. This was traced to a handling error where the reset of read-only formatting happened before the validation check, and has been fixed.
SR-A20790 · Issue 239549
Refresh section works after spellcheck
Resolved in Pega Version 7.2.1
When using a radio button with section refresh and conditional layouts and an additional spell check icon, clicking on the spell check icon and then changing the radio button value did not refresh the section. Instead, the busy indicator symbol appeared and caused the system to hang. This was traced to a permission denied JS error occurring on the refresh section after spellcheck when the getListeners API tried to access an orphaned RTE body. This has been fixed.
SR-A20861 · Issue 240914
Value populating made consistent for cascading dropdowns
Resolved in Pega Version 7.2.1
Cascading drop downs sourced from large data pages were not consistent about populating the values. The issue was caused by variable synching, and has been fixed.
SR-A20974 · Issue 241074
Validation will not set errors for hidden fields
Resolved in Pega Version 7.2.1
Autocomplete was generating a hidden input for a property referred to in the Search results configuration and displaying it first when the validation checked the property entry handle, causing an error. Required validation has now been modified to not set errors on hidden fields.
SR-A21040 · Issue 243518
Filter icon display corrected for Microsoft Internet Explorer11
Resolved in Pega Version 7.2.1
The filter icons were not properly vertically aligned when using Microsoft Internet Explorer 11. This was due to the parent of the filter icon element not having a height attribute read by this browser, and has been fixed.
SR-A21043 · Issue 241137
Refresh list action retains focus on work area
Resolved in Pega Version 7.2.1
When used as used as part of enabling successive rows, the refresh list action was returning focus back to first item rather than holding focus at the working point. This was found to be caused by a ?Select first row on initial load? option when ?Refresh List? is performed, and this code will no longer be called in this scenario.
SR-A21266 · Issue 239797
Ensured default display after grid takes effect in tree grid without explicit erase
Resolved in Pega Version 7.2.1
Old configurations were still visible after choosing ?Default (display after grid)? unless the value of the section name was explicitly erased. This was due to the generated java code that still contained the data displaying the values in fields it did not consider empty, and the handling has been corrected to resolve this.
SR-A21298 · Issue 240041
NPE on mobile list open resolved
Resolved in Pega Version 7.2.1
A null pointer exception was being generated on mobile device when opening list items. A null check has been added to pega_ui_modaldialog to resolve this exception.
SR-A21378 · Issue 245075
Resolved Interaction Portal unexpected close
Resolved in Pega Version 7.2.1
In Google Chrome, launching a secondary portal and encountering a Content Security Policy issue relating to an image caused the secondary portal to automatically close and the developer portal to be refreshed. This was an issue with a mismatch in the pyrequestor token, and has been corrected.
SR-A21526 · Issue 244743
Decimal formatting kept in autocomplete
Resolved in Pega Version 7.2.1
In some installations, clicking on the auto-complete field caused the decimal format to be lost. For ex: an initial value of 21,000.00 becomes 21000.00. To correct this, the function reload of ajaxengine API has been modified to pass an extra parameter in signature of processOnBeforeSubmit function (of ui_doc_submit API ) that checks 'layouts2refresh' in the function "processOnBeforeSubmit".