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.

INC-135523 · Issue 590437

Tab panel read meaningfully by screen readers

Resolved in Pega Version 8.3.5

When the tabPanel received focus with accessibility, the entire tab content was read instead of the W3 standard of only reading "Edit ". This has been resolved by ensuring the Tabpanel has the proper aria-labelledby.

INC-139023 · Issue 591165

Tab will exit portal side menu

Resolved in Pega Version 8.3.5

It is expected that the Tab key will take users out of the portal menu and to the next focusable element, but on the side navigation menu both tab and arrow keys moved to the next menu item. This caused users to have to navigate the entire menu. The correct behavior was seen for the Navigation rule when called from an Action (for example on the button). This was traced to the system using tabindex as "0" for every element in the menu, and the tabs code has been updated to exit out of the menu bar when pressed.

INC-138354 · Issue 594356

Third party cookies reminder added for Mashup in incognito browsers

Resolved in Pega Version 8.3.5

When working in incognito/private browser windows, attempting to use Mashup displayed a message indicating login credentials were not recognized ("Unknown password and/or username"). This was due to recent changes originating with the browsers regarding blocking third-party cookies which are necessary for Mashup to run. For informational purposes, a new API has been added which will check for the PegaRules cookie; if the cookie is not present, the message "Third party cookies must be enabled for Mashup to function." will be displayed. This message may be customized by configuring the setting "pega.web.config.xCookiesDisabled" with the required message.

INC-133951 · Issue 584148

Try catch added for templated refresh when

Resolved in Pega Version 8.3.5

After configuring a refresh when condition on a dynamic layout triggered by changes on D_worklist.pxResults, a component stack mismatch error was generated if client side UI template is enabled. Without templatization it worked as expected. This has been resolved by adding a try catch block to DynamicLayoutGenerator.java.

SR-D33359 · Issue 505773

SelectAll properly applied to only the page selected

Resolved in Pega Version 8.2.4

In repeating grid, applying SelectAll on one page resulted in it being applied to the next page as well even though all records in the other page were not selected. Investigation showed that on change, the 'when' condition added to refresh the list was always false. To resolve this, the condition in section pzBulkProcessingCheckbox which refreshes the list once the checkbox is changed has been removed.

SR-D37444 · Issue 507038

WorkBasketGadget control updated for improved backwards compatibility

Resolved in Pega Version 8.2.4

After upgrade, the WorkBasketGadget Control was not retrieving the work queues. This was traced to a backwards compatibility issue introduced when greater security was put in place. The control WorkBasketGadget contains a call to pzEncryptURLActionString that was introduced in 8.x versions of the platform to encrypt URLs to avoid hijacking. The content of the URL relies on the pxRequestor.pxWorkGroup property, which is resolved using pega:reference tags. This approach was working in versions below 8.x, but these tags were not resolved at runtime. To correct this, requestorWorkGroup will be resolved as string and passed as a parameter instead of using pega:reference tags.

SR-D26785 · Issue 495892

Corrected error when persisting temporary work object

Resolved in Pega Version 8.2.4

When persisting a temporary work object using the Persist case shape, the internal assignment handle was not updated to include the work object's ID. Subsequent attempts to access the internal assignment (such as the "Edit" button on the Review Harness) resulted in errors. Investigation showed that when a temporary case was persisted, pyInternalAssignmentHandle was not getting recalculated after pzInsKey was updated. To resolve this, the configuration on the edit button has been modified to use .pxFlow(pzInternalCaseFlow).pxAssignmentKey which is what pyInternalAssignmentHandle declare expression was also returning.

SR-D32525 · Issue 505467

Dirty check added to offer save/discard changes when closing tab

Resolved in Pega Version 8.2.4

With the OOTB section enabled, performing a change in the form (changing a text value, selecting a option in a dropdown, etc.) and closing the case generated an unexpected alert indicating that the case was changed and the modifications were lost. This differs from the previous behavior of showing the section pyDirtyCheckConfirm which offered the opportunity to save the work. This was a missed use case and has been resolved by updating the system to perform a check for the dirty state when closing the interaction and show a modal dialog asking the user to choose either save/discard if dirty.

SR-D29832 · Issue 503225

Corrected image alignment for email case creation

Resolved in Pega Version 8.2.4

An issue with missing image styling when an email was sent to create a case was traced to the Owasp library stripping align attributes from the img tag. This has been fixed.

SR-D33966 · Issue 504607

Corrected accessibility error after resize

Resolved in Pega Version 8.2.4

From within a Case and on a screen displaying the Information and Audit tabs in a Layout group, it was possible to use a series of sequences that included resizing the browser and opening Audit to cause the information tab to no longer be accessible. This has been resolved by setting the transform value to 0 after completing the resize.

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