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-D64694 · Issue 533963

Check added for Turkish locale in Firefox

Resolved in Pega Version 8.4

When using Firefox in the Turkish locale, attempting to open worklist subsets or edit tables in a modal dialogue caused the browser to hang. This was traced to the character conversion process in the browser and has been resolved with the addition of a check.

SR-D65086 · Issue 526597

Harness context will be stored to handle on click executed outside of the Ajax Container

Resolved in Pega Version 8.4

An exception was generated in the interaction portal on execution of a post-value action for the on-change event on a text-box in the service case: "Failed to find instance Work-Interaction-Research.EmailBodyRTE of type Rule-HTML-Section". This was traced to a condition where clicking outside of the Ajax Container context to trigger the change caused the Events code to execute the event in the active context when the active context had already been changed by clicking outside of the AC. To avoid this, the system will store the harness context in the event object using pega.ctxmgr.getContextByTarget(target) API. Additional changes were also made to handle the context switching in case of post value when the blur triggers a change in context.

SR-D65917 · Issue 528109

XSS protection added to ClientDynamicData

Resolved in Pega Version 8.4

Cross-site scripting protection has been added to the "DesignViewIframe" & "pzHarnessID" parameters in the pzClientDynamicData HTML rule.

SR-D66387 · Issue 530843

ReloadSectionsCache handling improved

Resolved in Pega Version 8.4

Change Tracker was reporting changes properly and ExpressionEvaluator logic identified the correct DOM element related to layout refresh, but the refresh was not getting triggered due to _isInvalidRefresh logic. This was traced to reloadSectionsCache not being optimally maintained, and has been resolved by updating reloadSetionCache to avoid unnecessary reloads and only update the cache after a reload section is completed.

SR-D67360 · Issue 527679

Bottom and right custom borders appear as expected

Resolved in Pega Version 8.4

After enabling editing of the default table format and then giving a format for the bottom and right borders, the borders did not appear. This was caused by code that was overriding the new configuration, and has been resolved.

SR-D71105 · Issue 532191

Corrected error when using CharCounter in non-template mode

Resolved in Pega Version 8.4

An error message was generated when trying to save a section with the TextArea's Display CharCounter set to True. This was traced to an error in the remaining character count span generation for non template mode and has been corrected.

SR-D71402 · Issue 532333

Localization added for Pega Call Login screen

Resolved in Pega Version 8.4

Localization has been added to the label "Value can not be blank" on the Pega Call Login screen.

SR-D71756 · Issue 533551

Thread Cleanup error resolved

Resolved in Pega Version 8.4

After upgrade, 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-D10855 · Issue 485681

Improved security for DSM Scorecard

Resolved in Pega Version 8.4

Security against remote code execution has been added for the rule Scorecard in DSM.

SR-D11655 · Issue 511426

JMS Listener modified to ensure connections are closed after encountering an exception

Resolved in Pega Version 8.4

JMS listener logs were detailing exceptConnection leaks with the message " J000100: Closing a connection for you. Please close them yourself". Investigation showed that when the JMSListener is configured for JBOSS, it goes via EngineImpl. However, connections opened during engineimpl.ivokeEngine were prevented from closing if they encountered an exception. To resolve this, the execution of the connection close command has been moved to the finally block.

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