INC-162360 · Issue 635817
Unneeded AUC error percentage calculation removed for better system performance
Resolved in Pega Version 8.6
When generating snapshots of the ADM models, an inefficiency in the metric calculation for the AUC error percentage caused an excessive amount of memory to be allocated which could cause slowdown or require a system reboot. This has been resolved by removing the problematic AUC error percentage calculation as it is not used in the UI.
INC-163940 · Issue 634491
CustomerData schema added to list of databases for optimization
Resolved in Pega Version 8.6
was no "Create?" column. This column appeared for the PegaDATA database but not for CustomerData. To resolve this, the Optimize Schema Landing Page has been updated to treat the CustomerData schema as a shipped Pega database.
INC-118743 · Issue 609580
System improvements related to ActiveDocumentType
Resolved in Pega Version 8.6
Alerts were seen for unexpected properties in HTTP requests related to pyActiveDocumentType, and system slowness was seen when the request was trying to update the properties. This was traced to a condition where a page remove cleared property registration, and has been resolved.
INC-118907 · Issue 565630
Document statetracker updated for more consistent Scenario Testing
Resolved in Pega Version 8.6
Inconsistent behavior was seen when running Scenario Tests: the same scenario test case run multiple times without any changes would sometimes pass and sometimes fail, and sometimes the fields were automatically filled in and sometimes they weren't. Scenario tests depend on the document-statetracker for moving from one step of the execution to the next, but an intermittent failure to reset the document statetracker back to the idle state caused inconsistencies in the execution. To resolve this, a new pub-sub mechanism will be used on the document statetracker.
INC-120299 · Issue 583025
Added null check to ActivityStatusExceptionHandler
Resolved in Pega Version 8.6
Invalid Parameter Exceptions were being logged in the production environment related to an 'CPMInteractionPortalWorkArea' execution error on page 'pyTmpDisplayHarness' indicating "Invalid value for aReference passed to com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.getProperty(String, char)". This has been resolved by adding a null check before reading the DC data model in the activity ActivityStatusExceptionHandler.
INC-128279 · Issue 591380
Layout Group tab alignment correctly shown in IE
Resolved in Pega Version 8.6
Even though the responsive breakpoint for a layout group was disabled, the tabs were getting changed to Menus in Microsoft Internet Explorer. This was traced to Tab-overflow being triggered in very small viewports when using IE11, and has been resolved by adding dom manipulations for all layout groups.
INC-128639 · Issue 608654
Updated dynamic container event listener for JAWS
Resolved in Pega Version 8.6
Upon tabbing in, JAWS 2020 was reading the entire contents of the center panel including announcing "Center Panel", "Tab Panel", "Frame" and all UI elements in the center panel without stopping. This has been resolved by updating the 'pega.util.Event.addListener' function in PZPEGA_UI_DYNAMICCONTAINER.
INC-132176 · Issue 588810
Cache cleared before PDF generation to ensure proper fonts
Resolved in Pega Version 8.6
The font File OCRAEXT.ttf added at location "/usr/local/tomcat/fonts" was not being picked when the PDF was generated via an agent execution. When the same activity was run manually, the font issue was sporadic. Investigation showed that when multiple apps use the same props directory but different fonts directories, the handling would sometimes cause one app to use another app's props file with the result of the improper fonts mapping. To resolve this, an update has been made to clear the cache before PDF generation starts to ensure the library reads the proper fonts.
INC-132500 · Issue 602633
Updated class name resolution for runtime with after-screen render load
Resolved in Pega Version 8.6
Rule Resolution was not working as expected with the dropdown property “.ErrorType”, if the load behavior was configured as “After screen renders”. This was traced to the Class name resolution not happening at runtime, and has been resolved by moving the code related to class names to runtime.
INC-132569 · Issue 595176
Resolved case detail overwrite
Resolved in Pega Version 8.6
In the interaction portal, when the same property (dropdown) was used to populate the details of sections in two cases, the first section (email case) details were replaced by the second section (outbound call case) details. Investigation showed that the refresh API was getting the reloadElement in the entire DOM based on the event target name property. To resolve this, updates have been made to use context DOM APIs to get the correct section.