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-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.

SR-D13886 · Issue 490616

CORS error logging improved

Resolved in Pega Version 8.4

In order to facilitate error resolution, logging has been enhanced for CORS denial errors.

SR-D14159 · Issue 493083

Toggle added for displaying exception stack trace

Resolved in Pega Version 8.4

When text like "%25" was added to the login URL, the full exception stack was displayed on the screen. To resolve this, when the prconfig 'initialization/displayexceptiontraceback' is set to false (default value), the system will render the status.jsp instead of error.jsp and will not populate any sensitive data in the request object. If its set to true, the system will fall back to the old approach which renders error.jsp and emits the stacktrace.

SR-D14601 · Issue 490632

Unique ID generation added for simultaneous multiple text area boxes

Resolved in Pega Version 8.4

In the Interaction portal, adding a task for a interaction using a form with a character-count enabled text area worked as expected when the interaction first opened a task with the character counter text area. However, if a second version of the same task was opened before the first task was completed, the second text area was not responsive or working as expected. This was traced to the system generating the same ID attribute for both instances of the text area character counter span, and has been resolved.

SR-D15910 · Issue 495124

AM/PM time setting corrected for Riyadh timezone

Resolved in Pega Version 8.4

When logged into the Pega mobile application with operator locale as ar_AR and timezone as Asia/Riyadh, selecting time as PM resulted in it being set to AM with Native control. If the native control was unchecked, a blank screen resulted. This has been corrected.

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