SR-A99155 · Issue 265977
Mobile dirty page handling corrected
Resolved in Pega Version 7.2.2
When the "X" (Close) icon was clicked in the Mobile Create Opportunity/Lead/Contact form and then the cancel button in the prompt popup was clicked, the same page returned and the app went into infinite loading mode. This was caused by a missed use case; when the document is found to be dirty and user decides to stay on the page, the code just returned. This has been fixed.
SR-B1043 · Issue 270870
Resolved RTE with Microsoft Internet Explorer textarea update
Resolved in Pega Version 7.2.2
If spellcheck was invoked on an RTE text area when using Microsoft Internet Explorer , the next time text was entered and saved the new text was not preserved in the text area. This has been resolved with an added null check.
SR-B426 · Issue 271503
Error label highlighting corrected for inside grid
Resolved in Pega Version 7.2.2
The correct label associated with the UI element in which the client side error was thrown was not highlighted when inside a grid. To fix this, the function findLabelFor has been updated to handle the case specific to the grid, as the error elements ID and the label's 'for' attribute were never equal due to the 'for' attribute changing value when used on repeating elements within a grid.
SR-A92731 · Issue 264546
Localization wizard correctly narrows to only rulesets
Resolved in Pega Version 7.2.2
Despite narrowing the localization wizard to select only rulesets, platform rules and messages ere also picked. This has been corrected by modifying the logic in the pzGetCLassLabels activity to only get populated rulesets when this filter is used.
SR-A87242 · Issue 255987
Removed secondary encoding in GetLocalizedValue checkbox
Resolved in Pega Version 7.2.2
When using a field value that referenced the GetLocalizedValue control to populate the caption of a checkbox, special characters were encoded on the UI. This behavior did not occur for simple labels. This was due to a second encoding step which has now been corrected.
SR-A81527 · Issue 254655
Unlocked rulesets for UI-Kit-7 and Pega-Desktop
Resolved in Pega Version 7.2.2
When using UI tollgate, the message 'Sentence case is not followed' would sometimes appear due to no unlocked rulesets being available in UI-Kit-7 and Pega-Desktop. In order to facilitate the UI issues pass, the rulesets have been made available.
SR-A88333 · Issue 256129
Corrected Interaction Header unexpected refresh
Resolved in Pega Version 7.2.2
Every time a new intent task was launched or closed in Interaction Portal, the Interaction header refreshed without any explicit configuration to refresh the header. This was due to the process used when evaluating the cross thread change tracker and has been fixed.
SR-A81527 · Issue 254654
Unlocked rulesets for UI-Kit-7 and Pega-Desktop
Resolved in Pega Version 7.2.2
When using UI tollgate, the message 'Sentence case is not followed' would sometimes appear due to no unlocked rulesets being available in UI-Kit-7 and Pega-Desktop. In order to facilitate the UI issues pass, the rulesets have been made available.
SR-A92755 · Issue 261497
Fixed links display with privilege option in repeating grids
Resolved in Pega Version 7.2.2
When making use of the privilege option in the link control configuration as a condition to enable/disable the links in the repeat grid, the links were disabled/hidden even when the operator had the correct privilege. Analysis showed this happened in cases where the primary page was different from the page context on which the current part of the section was rendering (for example, when a grid or repeating dynamic layout is present), and it has been fixed by passing the current step page to the pega_rules_default.ValidatePrivileges function instead of passing the primary page.
SR-A22230 · Issue 245989
Focus corrected for auto-complete fields in Microsoft Internet Explorer 11
Resolved in Pega Version 7.2.2
When using the Microsoft Internet Explorer 11 browser, selecting the value for an auto-complete field caused the cursor to move to the next field and then return to the first field. This was an issue with the focus and on-change refresh within the dynamic layout, and has been fixed.