SR-A20148 · Issue 239782
Repeat grid wrap column header center aligned upon resize
Resolved in Pega Version 7.2.1
The repeat grid wrap column header was not properly center aligned upon resize due to the text padding. This has been fixed.
SR-A20183 · Issue 238612
Localization handling updated for High Level Overview documents generated in Word
Resolved in Pega Version 7.2.1
In a localized environment, High Level Overview documents generated in Word included some garbled characters if there were images or attachments in between the content of sections. The localization code has been updated to properly handle this format.
SR-A20219 · Issue 239018
Page-Set-Messages error properly displayed in harness
Resolved in Pega Version 7.2.1
Error messages were not displayed after setting the page- set messages in an activity and calling on post processing of the flow action. This was due to the improper clearing of messages during the ReloadSection, and the API has been updated to resolve this.
SR-A20346 · Issue 242973
Cell height/width rounded in "," decimal locales
Resolved in Pega Version 7.2.1
Localization for areas that use "," as the decimal separator led to errors indicating the height/width of a merged cell of Free Form layout was a non-integer value. To avoid this, the design time JS will round the measurement for cellWidth and cellHeight.
SR-A20352 · Issue 242962
Scroll handling updated for autocomplete results popover
Resolved in Pega Version 7.2.1
Issues were found with the scrolling handling of an autocomplete popover opened inside a modal window. The pzpega_ui_popover.js has been modified to attach a scroll handler for modal dialog scroll, and code has been added in the clickaway handler to reposition the popover during scroll.
SR-A20391 · Issue 240293
Set enter key use for Google Chrome pagination
Resolved in Pega Version 7.2.1
In Google Chrome, the enter key was not working on the pagination gadget if the report was opened in a new window, but tab would fire the page change. Functionality has been added to the GridActivePage control to create the expected behavior.
SR-A20444 · Issue 238240
BusyIndicator masking fixed for Microsoft Internet Explorer and Firefox
Resolved in Pega Version 7.2.1
BusyIndicator masking was not working properly in Microsoft Internet Explorer and Firefox due to using the scrollTop property which does not work for body elements in these browsers. This has been fixed by adding a browser check and calculating scrollTop from documentElement.
SR-A20470 · Issue 240001
Twitter harvesting enhanced
Resolved in Pega Version 7.2.1
Data recovery has been improved for Pega Customer Service Social Engagement customers harvesting Twitter streaming data. If a steaming data set fails for any reason, whether due to disconnecting of the API for a short period, server failure, or for any other scenario where Tweets are not ingested in real time, the data recovery capability will fetch missed Tweets within a given set time window of recent Twitter historical data. This is done through an activity to create a Twitter search data set which can then be used to work act as a data source for the data flow. Additionally, logic has been added to identify the appropriate language for short inputs (one or two words).
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.