INC-146114 · Issue 604411
Create Survey routes case correctly
Resolved in Pega Version 8.5.2
The Create Survey utility was not routing the case to the user who initiated the case, but instead was routing it to the user who checked-in the case. This was traced to an error related to pxRequestor.pxUserIdentifier in the data transform pzpopulate survey params which is called when the survey utility is used, and has been corrected.
INC-146676 · Issue 601940
Field Service app localizations updated
Resolved in Pega Version 8.5.2
Localization has been added to the 'getDirections' alert and other popup alerts in the Field Service app.
INC-148727 · Issue 603752
Activity updated for Mobile attachment access
Resolved in Pega Version 8.5.2
Preview and download were not working for attachments stored in Pega Cloud Storage repository for mobile devices. Attempting to open an email attachment to preview or download resulted in a console error and the tracer showed the message 'Class pxLinkedRefTo does not exist'. This has been resolved by updating "pzpega_control_attachutil" to use the activity "GetAttachmentReference" for interactions with the attachments from any storage type.
INC-120299 · Issue 578183
Added null check to ActivityStatusExceptionHandler
Resolved in Pega Version 8.5.2
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 591378
Layout Group tab alignment correctly shown in Microsoft Internet Explorer
Resolved in Pega Version 8.5.2
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 Internet Explorer 11, and has been resolved by adding dom manipulations for all layout groups.
INC-132176 · Issue 588809
Cache cleared before PDF generation to ensure proper fonts
Resolved in Pega Version 8.5.2
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-132219 · Issue 580266
Values with accent characters are sorted properly
Resolved in Pega Version 8.5.2
Table Layout column values using a pagelist were not sorted properly when the data contained French accent characters. This has been resolved.
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.