SR-A16621 · Issue 233386
Changed image tag to prevent auto-submit of calendar when parameters exceeded
Resolved in Pega Version 7.2.1
When user wanted to select the future date, he navigates by clicking the Year navigation link (arrow link). During this process of selecting a future date in the Year Navigation link, moving beyond the configured Number of years caused the page to be automatically submitted. This was caused by the input tag used for image causing a form submit, and tag has been changed to an anchor to fix this.
SR-A16678 · Issue 234858
Scrollbar retains position after focus change and return
Resolved in Pega Version 7.2.1
In the compliance score landing page, clicking on "All Warning" opens a window with a report of all the guardrail compliance warnings. If that window had a scrollbar, clicking on a rule in the guardrail report to view it in Designer Studio and then returning to the popup was resetting the scrollbar location to the top of the window. This has been fixed to retain the scrollbar position.
SR-A16915 · Issue 232937
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-A16960 · Issue 233576
Predictive Analytics rulesets excluded from RSA
Resolved in Pega Version 7.2.1
The Pega-provided Predictive Analytics rulesets were being incorrectly being checked and flagged by the Rule Security Analyzer. The PAD rulesets have now been properly excluded from the RSA check, and further analysis was done to find and fix other RSA flags that should have been excluded.
SR-A17070 · Issue 239464
Accessibility added for field level validation messages in Microsoft Internet Explorer
Resolved in Pega Version 7.2.1
Server-side validation error messages were not read aloud in Microsoft Internet Explorer11 when the accessibility user tabbed to the field with the error. The API has been updated to resolve this.
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.