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.

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-173596 · Issue 673089

Apache Commons HttpClient dependency removed

Resolved in Pega Version 8.7.3

As part of moving from the Apache Commons HttpClient project (which is at end of life and no longer being developed) to the Apache HttpComponents project, openws dependencies on the commons-httpclient jar have been removed.

INC-228169 · Issue 729187

Login error messages updated

Resolved in Pega Version 8.7.3

Exception response messages have been updated in order to improve security around attempts to bypass operator authentication.

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