INC-132569 · Issue 595174
Resolved case detail overwrite
Resolved in Pega Version 8.5.2
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.
INC-133576 · Issue 590325
Expandable Grid behavior corrected
Resolved in Pega Version 8.5.2
Expanding any row in master details was collapsing a previously expanded row. This has been corrected.
INC-133978 · Issue 587698
Overlapping columns fixed in ReportViewer
Resolved in Pega Version 8.5.2
When Report Viewer was used for Report Definition, displaying it on dashboard columns resulted in columns that overlapped each other. This was traced to a resize issue related to the scrolling checkbox and has been resolved.
INC-135181 · Issue 597425
Clipboard handling updated to accommodate custom Cosmos portal
Resolved in Pega Version 8.5.2
After upgrading and moving to Theme-Cosmos, a browser-level refresh on the user portal was not remaining on the same screen that issued the refresh, but rather on the default screen of the user portal. This was traced to a difference in clipboard handling of the Body parameter value for strJSON that was exposed through a customized Cosmos User Portal where Ajax Container was not used but still present in DOM. In order to support this use case, the tab_support file in sendReqToUpdateClipboard method has been updated.
INC-135195 · Issue 598071
PD4ML library updated
Resolved in Pega Version 8.5.2
When generating a PDF from a report definition with more than 1000 records, the system would hang abruptly and stop responding. There was also a noticeable size difference in the generated file. This was an issue with the included version of PD4ML, and has been resolved by updating the version from 4.0.6 to 4.0.9fx1.
INC-135405 · Issue 582004
Simple button style updated to allow customization
Resolved in Pega Version 8.5.2
The Simple button style was not picking up the correct border style that was defined in the Skin rule when in the hover state. This was traced to the border radius value hard-coded in one of the custom files taking precedence over the value added for the border radius in the skin format. To resolve this, the simple button styles code has been removed from the controls.css file that had the border radius value hardcoded. The styles for simple button format will be configured in the skin, and a mixin has been added for modal buttons border styles that can be configured in the skin itself.
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-135992 · Issue 595353
Corrected Windows attaching file to incorrect case
Resolved in Pega Version 8.5.2
When using Microsoft Internet Explorer with Windows 10, opening multiple cases in multiple browser tabs and switching between the different cases created a condition where a file might be attached to the wrong case. This has been addressed by updating pzHarnessInlineScripts.
INC-136563 · Issue 607418
Tenant Switching updated
Resolved in Pega Version 8.5.2
When working on new “tenant switching” implementations in a multi-tenant environment, the API itself seemed to be working as expected (case details from another tenant were shown correctly in review mode), but clicking on the assignment unexpectedly opened the case in a new window that contained the same review view of the case rather than the perform view. Clicking the assignment link again caused yet another review window to open with the same issue, over and over. This has been resolved by adding a UI-side update to send the requests on proper sub-domain URL instead of using the parent domain, and by ensuring the document threads are properly deleted for multitenant usecases.
INC-136659 · Issue 593767
Template circumstancing works for report definitions
Resolved in Pega Version 8.5.2
On circumstancing the pyMyCasesReport using the Template option, it always displayed the base report definition instead of the circumstanced one when referenced the same report in the table in section. Because the grid component called two activities 'pxRetrieveReportData' and 'pxRetrieveReportMetadata' to render the table, the step page passed to these activities was from @baseclass. This caused the circumstanced template created in work- class to not get picked up. To resolve this, updates have been made to ensure the step page to the above activities will be of the report definition class.