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-D79777 · Issue 542046

Corrected top navigation rendering for Robot Manager harness with parameters

Resolved in Pega Version 8.3.2

When using "Robot Manager", a Single Doc, top navigation enabled portal, with pre DTs or Activities provided to launch a new harness on click of links from multiple places, an invalid data error appeared when a new Harness was rendered as part of some button or link click. If the the tab was closed and the Robot Manager portal was initiated from Dev studio, invalid data was loaded. This was traced to a missing use case for loading the portal center-panel harness when it was configured with preactivity and preDT with parameters. To resolve this, the showdesktop activity has been updated to handle preDT and preactivity parameters of the launch harness action.

SR-D80223 · Issue 542921

Cross-site scripting filtering for ActionStringID

Resolved in Pega Version 8.3.2

Cross-site scripting filter logic has been added to the ActionStringID function.

SR-D81779 · Issue 543855

Logic added to prevent refresh on enter when no action is configured

Resolved in Pega Version 8.3.2

After configuring a text input followed by an icon with display SmartInfo for click action, switching focus to the text input again after displaying the SmartInfo and hitting enter invoked the refresh harness even though no action was configured for the text input. This has been resolved by updating 'pzpega_ui_events.js' -> keyDownHandler() with logic to call preventDefault() based on certain conditions.

SR-D81900 · Issue 544327

Thread Cleanup error resolved

Resolved in Pega Version 8.3.2

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.

INC-227878 · Issue 727855

UPDATE IMPACT FOR PEGA CALL

Resolved in Pega Version 8.7.3

Log4j-1.2.14.jar and Log4j-1.2.17.jar have been removed to address the security concerns with these versions, and logger jars have been upgraded to 12.7.2 version (from 12.7.1 version) to make Pega Call compatible. This change will impact Pega Call customer environments due to Avaya or Genesys, which are part of Pega Call, having an internal dependency on Log4j1.x version jars. As a result, the SDK logging for Avaya or Genesys will not be available in the 8.7.3 release unless the Log4j-1.x jar files are reimported locally.

INC-203040 · Issue 721056

Null value handling added for CBU

Resolved in Pega Version 8.7.3

After update, changes made to the Operator record were not reflected and the Actions menu in Operator record did not show all available actions after the Operator was saved. This has been resolved by adding handling for null values passed as String for arguments from cbu.xml for the PegaCBU utility.

INC-214451 · Issue 721971

Rest connector passes RequestAttachmentPage to child requestor

Resolved in Pega Version 8.7.3

While invoking the Rest Connect from a data page, the error "InboundMappingException: Exception occurred while mapping incoming response" was generated. Requests with "Content-type:multipart/form-data" require "pyRequestAttachmentPage" or "pyResponseAttachmentPage" to be populated with correct values. When Rest-Connector was executed in parallel, those pages were not copied to the child requestor and the rest call executed from the child requestor did not have correct header and body. To resolve this, MethodConnect.java has been updated to correctly pass pyRequestAttachmentPage to the child requestor.

INC-224268 · Issue 724022

Cleaned up outdated prprivcommon class references

Resolved in Pega Version 8.7.3

After update, an exception was generated related to FirstUseAssembler. This was a missed use case for the WriteEFormToFile activity from previous work which restricted loading classes from prprivcommon.jar, and has been resolved by removing references to the following classes which were made inaccessible by the changes to prprivcommon: com.pega.pegarules.storage.FileStorageManager com.pega.pegarules.storage.fs.resadaptor.RAFile com.pega.pegarules.storage.fs.resadaptor.OutputStreamWrapper

INC-226830 · Issue 727153

Case Archival hierarchy updated for multiple occurrences of a child case

Resolved in Pega Version 8.7.3

Case Archival did not correctly discover hierarchy when child case appeared multiple times in the hierarchy. This was due to the CaseAssociationsProvider class having a check to skip performing the discovery when the case type had already been processed, and has been resolved by updating the handling for this scenario.

INC-202111 · Issue 710106

Logging extended for PRPCPropertyInfoProvider

Resolved in Pega Version 8.7.3

In order to assist with diagnosing issues with Kafka and JSON, additional logging has been added for PRPCPropertyInfoProvider.

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