INC-136634 · Issue 591678
Thread contention resolved for InteractionHistoryQuery
Resolved in Pega Version 8.5.2
High thread contention was observed while running Inbound load tests. This was traced to pzLoadInteractionHistory invoking a generated strategy to retrieve ihFields from InteractionHistoryQuery using the getUsedInteractionHistoryFields() method: because this method is synchronized, it caused a bottleneck. To resolve this, the synchronized methods have been replaced with the appropriate data structures.
INC-139645 · Issue 597500
Flowaction button responds for grid modal window
Resolved in Pega Version 8.5.2
The submit and cancel buttons were not working on first click for a modal window opened from a grid. Investigation found that this happened when the grid was shown on launching a harness but not if the grid was set to show otherwise in tabs, and was not seen when launching modal windows normally either from tabs or from harness (the pzModalTemplate or pyModalTemplate). This was traced to the system passing the target as a window to getTrackerChanges from triggerEvaluateClientConditions, which caused getTrackerChanges to be called on every window action. To resolve this, the event has been changed to 'focus' so that the method gets called only on focus.
INC-145263 · Issue 600036
Query logic modified for Anypicker
Resolved in Pega Version 8.5.2
A search for results in the Anypicker control for the first time showed the results, but if the results were deleted and the search run again without focusing out from that field, no results were found for the second search. This has been resolved by using slice than splice in the query to avoid mutating the original array source.
INC-142660 · Issue 595390
Pega API system management launches correctly from Help
Resolved in Pega Version 8.5.2
The Pega System Management API did not work when launched from help window, although other APIs such as Case Management were working fine. This has been resolved by updating the basePath in pzSystemManagementDocumentation.
INC-139156 · Issue 592148
Pasting image lands in correct location
Resolved in Pega Version 8.5.2
When pasting an image in a user story or issue, the image did not land where the cursor was placed in the contents of the issue or story. This was traced to the insert element handling for rich-text editor, and has been resolved.
INC-141099 · Issue 598131
Updated Cosmos confirm notification visibility conditions
Resolved in Pega Version 8.5.2
After routing an assignment to different operator, the current operator was still seeing the Go button in Cosmos for processing the assignment. Clicking on the button resulted in an error. To resolve this, the confirm notification section reload has been moved to a different context, and the visibility conditions have been updated to handle more use cases.
INC-135523 · Issue 590435
Tab panel read meaningfully by screen readers
Resolved in Pega Version 8.5.2
When the tabPanel received focus with accessibility, the entire tab content was read instead of the W3 standard of only reading "Edit ". This has been resolved by ensuring the Tabpanel has the proper aria-labelledby.
INC-192935 · Issue 698695
Inline images retrieved for deferred-load email
Resolved in Pega Version 8.7.1
When emails were defer-loaded, inline images with code entered into the non-cache section in pyExtractHtmlFromAttachment were not being displayed. This has been resolved by passing the current page parameter to pyExtractHTMLFromAttachment to convey the pyID.
INC-135720 · Issue 594791
Case link shows in Social messages for the old cases
Resolved in Pega Version 8.5.2
After upgrade from v7, the case link was not visible for the cases that were created in the old platform version. In Pega 7.1.7, metadata was stored in .pyPrivacyContextor while the later versions are using .pxContextType for Case type to show the related data. To resolve this, new properties have been implemented to hold the Case ID link
INC-158519 · Issue 625080
Filter considers all instances pages during deployment
Resolved in Pega Version 8.5.3
During package deployment, attempting to use Filter to skip some of the instances only displayed the result of the current active page instead of all pages. This was an unintended consequence of previous work, and has been resolved by adding the logic to strip quotes in the value and adding the "Pagination activity manages filtering" checkbox by default.