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-A17544 · Issue 236778
Removed pagination size restriction on listview if page size is set
Resolved in Pega Version 7.2.1
When an application had more that 50 data-types, not all data-types were shown in the application packaging wizard due to the page size being set to 50 while the list view function was set to return a maximum of 50 results if pagination was enabled. The pagination size limit on listview has been disabled in cases where page size is set in order to remove this conflict and display the results as expected.
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.
SR-A17941 · Issue 235161
Compatibility mode modal resize resolved
Resolved in Pega Version 7.2.1
When using compatibility mode, launching a modal containing an RTE caused the old deprecated modal dialog to launch as opposed to the supported standards based modal. Clicking the "Maximize" icon caused the work area to go blank; since the modal was no longer displayed, it could not be re-sized or dismissed. The contents of the work area behind the modal also went blank. This was due to known resize issues with the deprecated modal dialog caused by the editor's maximize logic conflicting with the old modal dialog resize logic. To prevent this, the Ckeditor will not fire resizeHarness when the old modal is in use. This stops the resize of the deprecated modal dialog and avoids the conflict between RTE maximize and old modal resize.
SR-A18078 · Issue 234051
Hybrid Client errors will display in modal window
Resolved in Pega Version 7.2.1
When an error occurs on the hybrid client of a server, a new window should open with the error. This was not working as expected due to the client passing an invalid URL of "" to Window.open. To better handle this scenario, errors will be displayed in a modal window instead of performing a Window.open if a hybrid client container is in use.