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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

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-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-A75998 · Issue 253191

Improved SOAP envelope cache for WSA/WSSE use

Resolved in Pega Version 7.2.2

After configuring and successfully using Connect-SOAP to a non-secure Endpoint, enabling WSA and WSSE for the connect-SOAP configuration and then disabling it again generated the error "Caused by: com.pega.apache.axis2.AxisFault: A required header representing a Message Addressing Property is not present". This was due to the way the SOAP envelope was being cached and the code has been updated to correctly reflect the desired header processing.

SR-A20018 · Issue 250581

Drill down fixed for use with "Do not display group headings"

Resolved in Pega Version 7.2.2

When the "Do not display group headings" setting in report viewer tab was checked in a report, drilldown did not work correctly for summarized reports that do not display group headings. This was an issue with attributes not being set for the drilldown to work with aggregate columns, and has been resolved.

SR-A20018 · Issue 250155

Drill down fixed for use with "Do not display group headings"

Resolved in Pega Version 7.2.2

When the "Do not display group headings" setting in report viewer tab was checked in a report, drilldown did not work correctly for summarized reports that do not display group headings. This was an issue with attributes not being set for the drilldown to work with aggregate columns, and has been resolved.

SR-A76586 · Issue 256002

Guardrail updated for Report Definitions using Data Page for filter

Resolved in Pega Version 7.2.2

It is possible to configure a report definition to use a Data Page in the Filter/Criteria field (such as pxObjClass Contains D_ABC.PropValue) and not be prompted to list the Data Page on the Pages & Classes Tab, but when it is not listed on this Tab the query uses a literal value as opposed to a dynamic reference. In order to ensure expected results, a check has been added to fully identify invalid page prefixes and an Informational guardrail for Functionality will appear.

SR-A91682 · Issue 261408

Repeat grid properly refreshed with add icon when no rows to display

Resolved in Pega Version 7.2.2

The repeat grid was not getting refreshed when the add icon was clicked. Analysis showed that when "Do not display grid header when there are no rows to display" was checked in the repeat grid property panel presentation tab, the grid 'no results' div was placed outside of the grid content div. This caused removeGridNoResultsMsg to fail and the toggleGridStylesForNoResultsCase function was never called after loading the new row. To fix this, the pega_ui_grid JS removeGridNoResultsMsg function has been modified to call the toggleGridStylesForNoResultsCase function when bHideGridHdrWhenNoRows is true.

SR-A91682 · Issue 260252

Repeat grid properly refreshed with add icon when no rows to display

Resolved in Pega Version 7.2.2

The repeat grid was not getting refreshed when the add icon was clicked. Analysis showed that when "Do not display grid header when there are no rows to display" was checked in the repeat grid property panel presentation tab, the grid 'no results' div was placed outside of the grid content div. This caused removeGridNoResultsMsg to fail and the toggleGridStylesForNoResultsCase function was never called after loading the new row. To fix this, the pega_ui_grid JS removeGridNoResultsMsg function has been modified to call the toggleGridStylesForNoResultsCase function when bHideGridHdrWhenNoRows is true.

SR-C57557 · Issue 402906

Work Object lock released correctly when modal dialogue is canceled

Resolved in Pega Version 8.1.1

The Work Object lock was not being released when the modal dialogue cancel button was clicked. This was due to the primary page not being switched to the pyWorkPage during the cancel, and has been fixed.

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