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-185122 · Issue 670400

Able to create View in Cosmos React

Resolved in Pega Version 8.6.2

After creating a Cosmos react application and adding casetype, it was not possible to configure the view from the step in App Studio or Dev Studio or to create a section from Dev Studio. This was traced to the componentslist not finding some necessary components, and has been corrected.

INC-185847 · Issue 669525

Handling added for disabling weekends when no weekends are available

Resolved in Pega Version 8.6.2

A browser exception was generated while selecting the option “Disable weekends”. This was traced to a malformed array of weekends in a scenario where the Data-Admin-Calendar instance had all business days checked (i.e., no weekends). To resolve this, DatePickerAssembly and pzGenerateDatePicker have been updated to handle the case when there are no weekends available in the Data-Admin-Calendar instance.

INC-186466 · Issue 670291

Style selector workaround added for Internet Explorer 11

Resolved in Pega Version 8.6.2

When using UI-Kit 15.0.1 with Microsoft Internet Explorer 11, the responsive behavior of the left navigator was not working as expected, it was not possible to Customize/Style the File Path control completely, and the AutoComplete control and Date Time Controls had a blue border on hover/focus. This was traced to the styles not being correctly selected because they contained the selector "focus-within" which is not supported in this browser. This has been resolved by adding focus-within separately so Internet Explorer will ignore the selector.

INC-187378 · Issue 670549

Scrolling fixed for moving rows in tables

Resolved in Pega Version 8.6.2

After update from Pega 8.4 to Pega 8.6, attempting to move a row on the top to bottom was not working correctly due to the scroll being limited. Moving an item higher worked as expected. Investigation showed if the container format of the grid was None a condition was setting the scroll to top even if it was being scrolled down, and this has been resolved by getting the gridOffsetTop value from the closest table tag and increasing the setInterval time to achieve smooth scroll behavior.

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