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-111928 · Issue 183474

Assignment locking smoothed for slow network async requests

Resolved in Pega Version 7.1.8

In situations with slow network async Ajax requests, locking was not being properly released between requests. This caused an issue with sub-flows that had a Spinoff Flow configured to route the assignments in the sub-process and the main process to separate operators. In order to resolve this, the close tab process has been updated to remove the corresponding thread and release the lock.

SR-114819 · Issue 175544

Localization added for currency values using commas vs decimal points

Resolved in Pega Version 7.1.8

Excel within PRPC was not properly localizing for the use of decimal and comma as thousand and decimal separators for decimal/double currency property values, a use that is common in non-English installations. The records editor has been changed to support localization for properties of type double and decimal.

SR-114875 · Issue 171313

Enhanced error handling for WebSphere class conflicts

Resolved in Pega Version 7.1.8

An error caused by a class conflict issue in WebSphere was being generated when exporting Process Flow as XPDL. In order to clarify the limitations in this use, changes have been made to the XSLTRANSLATE Activity to add an extra catch that handles any style sheet errors explicitly and provides an informative error message.

SR-115208 · Issue 178808

Assignment locking smoothed for slow network async requests

Resolved in Pega Version 7.1.8

In situations with slow network async Ajax requests, locking was not being properly released between requests. This caused an issue with sub-flows that had a Spinoff Flow configured to route the assignments in the sub-process and the main process to separate operators. In order to resolve this, the close tab process has been updated to remove the corresponding thread and release the lock.

SR-115208 · Issue 183474

Assignment locking smoothed for slow network async requests

Resolved in Pega Version 7.1.8

In situations with slow network async Ajax requests, locking was not being properly released between requests. This caused an issue with sub-flows that had a Spinoff Flow configured to route the assignments in the sub-process and the main process to separate operators. In order to resolve this, the close tab process has been updated to remove the corresponding thread and release the lock.

SR-115365 · Issue 173851

New 'Break Long Word' sub-setting added to 'Wrap Text'

Resolved in Pega Version 7.1.8

When lengthy text was present inside the cell of a grid configured as a fixed size / fixed header grid, misalignment between column header and row cells was seen. This was an issue with the text display. The word-wrap property earlier was set to break-word to enable wrapping of long words to multiple lines, but this was not working as expected for values that do not have a whitespace/break. To resolve this, when the 'Wrap text option' is clicked, the new configuration option 'Break long word' will be available to allow line breaks between letters.

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