SR-A22933 · Issue 246958
Check added to resolve Google Chrome-based value localization error
Resolved in Pega Version 7.2.1
A Google Chrome browser check has been added to the Polish and French localization packages to resolve an error generated when a comma is used in a monetary value.
SR-A23012 · Issue 243963
pega.u.d.onViewUpdatecorrectly triggered from Master-Detail
Resolved in Pega Version 7.2.1
The "pega.u.d.onViewUpdate" function invocation was not being triggered as expected when the details screen was opened from a master list while offline. To fix this, the "actionInfo" pzInskey has been updated to obtain the Page Context on which the RDL is configured.
SR-A23208 · Issue 246610
Microsoft Internet Explorer menu highlighting tuned
Resolved in Pega Version 7.2.1
The system has been updated to resolve an Inconsistency with menu highlighting in Microsoft Internet Explorer.
SR-A23445 · Issue 247673
Localization picks up existing translations in child applications
Resolved in Pega Version 7.2.1
If an operator is a member of multiple access group and has access to multiple applications, the localization wizard was not picking up existing translations when the operator switched to another, non-default, application. The UseCurrentAccessGroupForChild has been updated to provide the missing localization.
SR-A23473 · Issue 246023
WordTextArea function tuned for Microsoft Internet Explorer 11
Resolved in Pega Version 7.2.1
The WordTextArea was displaying base64 encoded text in the IE11 browser. This was a compatibility problem, and the WordInclude.js ' after edit' functionality has been tuned.
SR-A23940 · Issue 247101
RGB value accepts direct custom entry
Resolved in Pega Version 7.2.1
The RGB value was not updating in Custom tab of "ColorPicker " Control when directly changing the spinner value by entering value. This has been fixed.
SR-A24110 · Issue 246955
Fixed new tab opened on manual refresh (F5) of the Case Manager portal
Resolved in Pega Version 7.2.1
Doing a manual refresh (F5) of the Case Manager portal caused a new tab to be created with the harness displayed in it This was caused by the pyKey being incorrectly updated for static tabs, and has been fixed.
SR-A9107 · Issue 218864
Fixed required field entry validation flicker in autocomplete
Resolved in Pega Version 7.2.1
For autocomplete (chosen as required), when the down arrow is used and an option is selected, the error "field cannot be blank" is shown for a fraction of second. This has been fixed by moving the validationtype attribute firing from the time of selecting a value from grid to after the value is selected.
SR-A9481 · Issue 244466
Cleared validation error for fields not present on submit
Resolved in Pega Version 7.2.1
Validation errors were being thrown by fields that were no longer present or no longer relevant when a a modal window was launched and then canceled without filling in the fields, and the the main form was submitted. This was due to the popover/overlay close not clearing the DOM element, and has been fixed.
SR-A9651 · Issue 235540
Added null check for empty section rule properties in Design Time section containers
Resolved in Pega Version 7.2.1
In some cases, attempting to reopen a section container resulted in corrupted files. This was a Design time issue only, and was traced to empty property values. On doing a check-in , the clipboard page is put into the DB, but only properties with values were committed. Any properties whose values are empty were not committed. During retrieval, an exception was thrown because the properties did not exist in the XML. This has been resolved by updating the loadPropertyHtmlCache API of pzpega_ud_dvmanager to add null checks for pyFormat and pyValue properties which are being accessed.