SR-A92086 · Issue 260095
Mashup Gadget considers DSS for access group redirectGuests
Resolved in Pega Version 7.2.2
In Mashup, the Gadget was unable to redirect to the corresponding access group based on the application name, instead always redirecting to the default access group. In order to address this immediate problem, a change has been made to add the redirectGuests attribute to the mashup html generation based on DSS setting. This will not get the access group hash only in cases when: - operating in the non-tenant environment and - the mashup configuration div claims to have set the DSS for redirectGuests as being set to false. The code itself does not verify whether the run time value of the DSS is properly set or not.
SR-A87054 · Issue 255434
Click delay removed in mobile events
Resolved in Pega Version 7.2.2
In order to improve performance on mobile devices, the click handler has been moved to touchend event to remove the 300ms delay used by browsers to differentiate click/double-click.
SR-A77173 · Issue 254080
IsWindowStealFocusInIEAllowed allows 'when' value
Resolved in Pega Version 7.2.2
In order to run legacy and Pega applications in parallel, a site configured the system to create a case in the Pega application as soon as a case was created in the legacy application. The intent was to have the case created in Pega to be in the background, but performing any DC actions shifted focus to the Pega app window when using Microsoft Internet Explorer . In order to have the configuration work as desired, the pyIsWindowStealFocusInMicrosoft Internet Explorer Allowed when rule must be set to false (default is true). Support for a conditional window focus configuration is now available, based on pyIsWindowStealFocusInMicrosoft Internet Explorer Allowed 'when' rule value.
SR-A91480 · Issue 259296
Datarepeater honors user-set global dirty flag
Resolved in Pega Version 7.2.2
In pzpega_desktop_datarepeater JS and pzpega_ui_template_datarepeater JS, the code for add and delete functions was overriding the global dirty flag, creating unexpected results. The system has been updated to honor the global dirty flag if it is already set and set it only when it has not been set by the user.
SR-A96445 · Issue 265106
Fixed grid rendering for menu item target
Resolved in Pega Version 7.2.2
Incorrect grid rendering for a menu item target was causing a right-click on the link item to display a misaligned result and faulty click responses. The pega_control_actions JS has been modified to ensure that If a section exists inside the grid, the menu will be rendered in that context.
SR-A96445 · Issue 266378
Fixed grid rendering for menu item target
Resolved in Pega Version 7.2.2
Incorrect grid rendering for a menu item target was causing a right-click on the link item to display a misaligned result and faulty click responses. The pega_control_actions JS has been modified to ensure that If a section exists inside the grid, the menu will be rendered in that context.
SR-A100693 · Issue 270076
Checkboxes retain context in Repeating Dynamic Layouts
Resolved in Pega Version 7.2.2
Issues were found with properties in Repeating Dynamic Layouts that lose their context based on user interaction and out-of-the-box configuration, most notably with Checkboxes. On checkboxes the action does not need to trigger a refresh, yet the UI for the checkbox HTML is was refreshed even when it should not be. In order to fix this issue, changes have been made to the initiatePost() method in "pzpega_ui_events" file to ensure the "RepeatDynamicIndex" param is sent to the server and generates the ID on the checkbox as expected. Note: This fix will work only for checkboxes in RDL only and only for "post value" action.
SR-A100725 · Issue 270058
Checkboxes retain context in Repeating Dynamic Layouts
Resolved in Pega Version 7.2.2
Issues were found with properties in Repeating Dynamic Layouts that lose their context based on user interaction and out-of-the-box configuration, most notably with Checkboxes. On checkboxes the action does not need to trigger a refresh, yet the UI for the checkbox HTML is was refreshed even when it should not be. In order to fix this issue, changes have been made to the initiatePost() method in "pzpega_ui_events" file to ensure the "RepeatDynamicIndex" param is sent to the server and generates the ID on the checkbox as expected. Note: This fix will work only for checkboxes in RDL only and only for "post value" action.
SR-A93553 · Issue 263954
Filtering for duplicate rules added to localization wizard
Resolved in Pega Version 7.2.2
It was observed that some duplicate or even triplicate rules were appearing after running the Spanish language localization wizard. In order to prevent this, the localization wizard logic has been updated to filter duplicates based on their pzInsKeys.
SR-A69787 · Issue 253568
DSS added to allow validation to be disabled if Edit-input is configured
Resolved in Pega Version 7.2.2
Japan has a special date format based upon the year of accession of the emperor. An Edit Input rule that converts that format into standard Gregorian format and applied it to a date property worked as expected, but when the initial client validation fired and generated an error on the text field, the Edit input also fired and converted the text as per the required format. At this point the refresh condition occurred, which again resulted in firing the client validation and removing the error. In order to prevent client validation when an Edit Input is likely to alter the contents, a Dynamic System Setting has been added. Based on the value of this DSS, validation can be disabled for all the fields where Edit-input is configured.