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-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-A76837 · Issue 257171

Resolved blank property screen lock when WAI enabled

Resolved in Pega Version 7.2.2

When PegaWAI was enabled and a property-set-message method, run by clicking a button, set an error message to a blank property on the user portal (not in a flow), the screen became disabled. After entering a value in the field, the screen was still disabled and the error was not cleared and appeared in a fixed position on the page. This has been fixed by adding a null check to the displayError method in the harness_accessibility.js to handle conditions when there are no forms present.

SR-A99423 · Issue 265463

Report Definition parameter passing improved for grids

Resolved in Pega Version 7.2.2

When run report was configured on a grid, the Data-Click attribute for a Report definition action with the parameter of type Pagename.Prop inside the grid did not generate properly. The parameter passing has been improved to address this issue.

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-A77177 · Issue 258649

Attachment gadget updated for Firefox

Resolved in Pega Version 7.2.2

When the Attachment gadget pops up using Firefox, it was not being correctly read with JAWS. This was an issue with the enter key press triggering a click event which did not have the expected code for Firefox. Changes have been made so the browser will consider the event object correctly.

SR-A95614 · Issue 263958

Modified logic for displaying default accordion tab with visibility when

Resolved in Pega Version 7.2.2

When the default tab selected in an Accordion was hidden by a visibility condition, the whole default tab calculation was incorrect and did not display properly. This has been fixed by modifying the defaultTab calculation logic when visible when conditions are present.

SR-A95614 · Issue 263995

Modified logic for displaying default accordion tab with visibility when

Resolved in Pega Version 7.2.2

When the default tab selected in an Accordion was hidden by a visibility condition, the whole default tab calculation was incorrect and did not display properly. This has been fixed by modifying the defaultTab calculation logic when visible when conditions are present.

SR-A24901 · Issue 266257

Restored nested sections visible in Designer Studio

Resolved in Pega Version 7.2.2

When trying to restore a earlier check-in version inside a nested layout, the restored section was corrupted i.e., the elements inside the dynamic layout (repeating grid) were not visible in the Designer Studio even though they did display as expected at runtime. 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-A90755 · Issue 263310

Restored nested sections visible in Designer Studio

Resolved in Pega Version 7.2.2

When trying to restore a earlier check-in version inside a nested layout, the restored section was corrupted i.e., the elements inside the dynamic layout (repeating grid) were not visible in the Designer Studio even though they did display as expected at runtime. 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-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.

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