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-D90687 · Issue 560427

IOException handling improved to resolve broken pipe errors

Resolved in Pega Version 8.2.7

Frequent "connection reset by peers" exceptions were being generated and broken-pipe exceptions were seen in the logs. Investigation traced the issue to unhanded IOExceptions on the server side that were a result of the client application not always closing the TCP connection gracefully. To resolve this, error handling for IOExceptions has been improved.

INC-118907 · Issue 561071

ClearHighlight called after test steps complete

Resolved in Pega Version 8.2.7

When using a custom delay as part of a scenario test, an orange highlight square was unexpectedly persisting on the portal. To resolve this, an update has been made to explicitly call "_clearHightlight()" after every test case step execution completes.

INC-121444 · Issue 561807

Added handling to force text area maxlength in Edge

Resolved in Pega Version 8.2.7

When using the Edge browser, it was possible to continue entering characters in excess of the value set for the 'max characters' property. Investigation showed that the Edge browser does not honor the maxlength attribute on text area, to resolve this, logic has been added to restrict the user from entering extra characters above the max limit.

INC-125105 · Issue 563382

Null checks added for incomplete autocomplete fields

Resolved in Pega Version 8.2.7

When using a page which has an AutoComplete text input and a button configured for search, tabbing out of the autocomplete field before the autocomplete list has appeared and then filling out the rest of the fields and clicking submit was sporadically resulting in the page becoming unresponsive. This has been resolved by adding null checks and improving the error handling.

INC-126432 · Issue 564623

Support added for resuming scenario test recording

Resolved in Pega Version 8.2.7

When running an automation recording, a refresh of the harness was hiding the recording panel. When it was reopened, the panel was not responsive but the recording process was still running. This was traced to a scenario where the portal harness had a second harness running on it (such as a normal case worker would have) and the "Render As Single Page" was not checked: clicking a button with an action like "create new work" caused the whole harness (top) to be refreshed, resulting in the panel issues. To resolve this an enhancement has been added which will maintain the Scenario test recording when browser refresh happens, and recording can be restarted by clicking the toolbar option.

INC-127201 · Issue 562820

Thread Cleanup error resolved

Resolved in Pega Version 8.2.7

After update, intermittent exception errors were being generated by the FreeClipboard activity when switching between applications. This was traced to specific use-case issues with Thread Cleanup, and has been resolved.

SR-D53568 · Issue 521145

Improved post-update compatibility for custom tabbed screen flows

Resolved in Pega Version 8.2.7

After update, a screen flow with a customized harness saved-as from a TabbedScreenFlow harness and configured with client side validation disabled was displaying a blank white screen if validations failed when moving from one tab to another tab. When a tabbed screen flow has errors the necessary script bundles should be added, but this configuration was created prior to the introduction of templated controls and non-templated controls don't need script files. Because the ‘doesStreamMatchInputProperties’ method sets ‘researchmode’ to true, the ‘doOnlyOnce’ method evaluated to false and script files related to templating controls were not getting appended. For greater backwards compatibility, 'mResearchMode’ will be set to ‘true’ to make stream processing light weight. In addition, the researchmode check will be removed when adding scripts.

SR-D61560 · Issue 539473

Support added for multiselect control with SmartTip for iPad

Resolved in Pega Version 8.2.7

When using a multiselect list control to a lproperty with Smart Tip configured, choosing one item on an iPad and then trying to tap or drag down the vertical scrollbar caused all listed items to disappear. To resolve this, the multiselect control has been updated to handle the popover exit on smart popover hover along with arrow key navigation support for tablets.

SR-D65174 · Issue 560600

SetInterval will increase when AQD delay is defined

Resolved in Pega Version 8.2.7

With a 5000ms delay in place, executing scenario test cases resulted in errors such as values sporadically not being entered in their respective fields when the test was run, test runs that failed even though the data was entered as expected, or the submission of a test case assignment (Next button) executing the next step before the new screen was loaded. Investigation showed this issue was occurring when the system encountered a slower machine and a delay in loading pages, and was traced to the executor not waiting long enough due to the implicit setInterval of 8 seconds. It was possible to add a local delay in AQD settings for slow pages, but the system-set setInterval interfered with this delay. To resolve this, changes have been made to the executor module where setInterval is invoked that will increase the setInterval time when AQD delay is defined, so that setInterval will not interfere with a locally-set AQD delay.

SR-D67012 · Issue 537308

Invalid dropdown time will retain entered time

Resolved in Pega Version 8.2.7

If a datetime control using dropdown mode and a timeofday property had a validation error, on refresh the current time was being set in the dropdown. This occurred when selecting only one part of the time property (only minutes or only hours), and included an error indicating that the provided time was not a valid time of day value. To resolve this, an update has been made so that if this combination has a validation error, on refresh setting the user-entered time will be given in the dropdown instead of the current time.

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