SR-A17159 · Issue 235008
Year range calculation updated
Resolved in Pega Version 7.2.1
If a datetime control was configured as a dropdown list for a Date field in a screenflow, selecting a date and clicking "Next", then traversing back to the Date screen changed the year, ex. at run time, Year range is from 2006 to 2026, but became 1996 to 2016 when the focus returned. The current logic of year calculation was based on the year already set, and changes have been made to pzGenerateDatePicker to consider the current year when populating the year dropdown.
SR-A17183 · Issue 241734
Swimlane flow connectors visible after upgrade
Resolved in Pega Version 7.2.1
After upgrade, some of connectors between the flow shapes were not appearing as expected when opening flow rules forms designed with Swimlane even though the flows ran as expected. Attempting to amend the flow rules by reconnecting the shapes caused the ruleform save to fail. This issue stems from problems opening the Decision Tree rule Data-MO-Connector-Transition.pyBuildLabel on a Pega 7.1.8 system. This has been fixed.
SR-A17193 · Issue 236190
Custom height settings retained for progress bars
Resolved in Pega Version 7.2.1
After upgrade, the settings contained in the final rule pzjquery_ui_progressbar_dotluv CSS were overriding custom height settings for progress bars. The code has been updated to ensure custom settings are retained.
SR-A17223 · Issue 238044
Fixed JS error for Date Calendar changes
Resolved in Pega Version 7.2.1
Using Microsoft Internet Explorer, the Date Calendar was intermittently throwing a JavaScript error when trying to select another date from the date picker. This was caused by the rapid changing of dates overwhelming the onChange refresh section configured on the date input and leaving a stale input element, and has been fixed.
SR-A17403 · Issue 236170
Microsoft Internet Explorer browser check added to screenshot tool
Resolved in Pega Version 7.2.1
When closing an Microsoft Internet Explorer browser tab with an interaction open, an error is generated relating to the create snapshot tool. This screenshot functionality is only supported in Microsoft Internet Explorer8 and Microsoft Internet Explorer9, and a browser check has been added.
SR-A17411 · Issue 234053
Alignment resolved for repeating grid headers
Resolved in Pega Version 7.2.1
Headers were mis-aligned in the UI Gallery for a repeating grid when the freeze header option was chosen along with pagination and width of the content. This was an issue with the initScrollbars function, and has been corrected.
SR-A17476 · Issue 234924
Autocomplete working on node level data pages
Resolved in Pega Version 7.2.1
The auto complete feature was not working if the Categorize search results option was checked on node level data pages. The SortClipboardData now has support for node level data pages categorization.
SR-A17672 · Issue 236191
Tab layout groups updated to retain status when switching
Resolved in Pega Version 7.2.1
Switching between tabs caused the harness to refresh. The tab layout groups have been updated to ensure expected behavior.
SR-A17683 · Issue 235082
Autocomplete JSON error resolved
Resolved in Pega Version 7.2.1
A JSON parse error was causing issues with autocomplete controls after updating. This was caused by a syntax error, and has been corrected.
SR-A17881 · Issue 233850
Browser check added to TextArea for consistent rendering
Resolved in Pega Version 7.2.1
When using the Google Chrome browser, an Enter key press / newline was calculated as two characters during rendering but as a single character in the character counter. This would cause the Text Area to behave differently depending on the browser. To avoid rendering issues, a check has been added to compensate for this difference.