SR-A15864 · Issue 231716
Post action RTE spellcheck works in Microsoft Internet Explorer
Resolved in Pega Version 7.2.1
After opening a modal dialog window in Microsoft Internet Explorer that has a Rich Text Editor that has been configured to spellcheck on change, submitting a wrongly spelled word blocked reopening the modal dialog. This was traced to Microsoft Internet Explorer throwing Permission Denied for premature load events, and has been solved by wrapping the code which accesses iframe element and throws Permission Denied exception.
SR-A15903 · Issue 240872
Enhancement added to support non-standard HTML in Ruleforms
Resolved in Pega Version 7.2.1
After manually writing non-standard HTML code in Source mode, switching back to Design mode showed corrupted code. This was caused by the RTE used in the Ruleforms auto-correcting the HTML. A "source only mode" check box option has now been added to the on paragraph, correspondence, and corr fragment Ruleforms that will provide a text area in place of RTE when selected.
SR-A15999 · Issue 232081
Modal window retains size after row delete
Resolved in Pega Version 7.2.1
If a repeat grid inside a modal window was using Expand-pane edit mode, adding a row and deleting it then pressing next caused the modal window to be completely squeezed and unable to be re-expanded. This was caused by a null pointer exception in the flow actions for the modal window, and has been fixed.
SR-A16012 · Issue 233486
Localization added for locking messages
Resolved in Pega Version 7.2.1
Localization has been added for locking-related messages in LockInfoAdvanced to facilitate translating messages such as "This case is locked by your operator in another PRPC session. Choosing the End other session to release lock option will log out your other PRPC session in order to release the lock. This option may not be effective immediately."
SR-A16026 · Issue 233285
Resolved validation error for saving section rule
Resolved in Pega Version 7.2.1
A Participant.FullName validation error occurred when trying to save a section rule when the Dynamic Layout with the .Participant.FullName property was above a repeat grid that has the Finish Assignment action specified for the Enter event. This was caused by a null clipboard page being passed in this configuration, and has been resolved.
SR-A16398 · Issue 232765
UI-Kit updated to use Open Work by Handle in pyFavorites
Resolved in Pega Version 7.2.1
In the Manager portal, clicking on a parent case in the "Following" section opened the subcase instead of the parent case that was being followed. The issue occurred when utilizing the pyFavorites section in a UI-Kit that was configured with the Open Work Item action. To correct this, the UI-Kit for this release has been changed to use the Open Work by Handle option.
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-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.