Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-A88892 · Issue 266454

Restored nested sections show repeating grid header

Resolved in Pega Version 7.2.2

In a section that has repeating grids configured, rule check-out and check-in caused the repeat grid headers and cells to disappear in Designer Studio. Analysis showed that when a rule was deleted from a section with nested layouts, only the properties which had values were committed to the database. On restoring the rule, only committed properties were re-created on the section XML, leaving the XML incomplete and generating an error and layout rendering failure. To fix this, the pzpega_ud_gridlayout_structure JS has been updated to handle the non-existence of empty nodes and initialize them.

SR-A99412 · Issue 270055

Spacebar 'Select a Form Field' shortcut fixed for JAWS

Resolved in Pega Version 7.2.2

In an application that uses JAWS to navigate the form fields, the instruction from JAWS was "to activate tab page press spacebar", but engaging the spacebar key did not activate the field/tab as expected. This was traced to a missing condition for the spacebar to handle the event firing when spacebar (keycode 32) is pressed to generate a click on the selected tab from the "select a form field" dialog of JAWS. This condition has been added.

SR-A100432 · Issue 268484

Dirty form handling improved for Mobile harness

Resolved in Pega Version 7.2.2

In certain configurations, the Mobile app was entering an infinite loop due to an error in the harness handling for a dirty form. This has been fixed.

SR-A92086 · Issue 264769

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-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.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us