SR-D37275 · Issue 519027
Enabled PDF attachment for iPad Safari
Resolved in Pega Version 8.1.8
It was not possible to select the PDF option when attempting to attach a file while using iPad Safari. This has been corrected.
SR-D76134 · Issue 542160
"Offline" icon shows when simulating offline mode
Resolved in Pega Version 8.1.8
When simulating offline mode by selecting "Settings->SystemInfo->Simulate Offline checkbox" and moving to MyWork, "Offline" did not appear in the header. This has been corrected.
SR-D71408 · Issue 534932
DIrty check flag triggered by adding columns and filters
Resolved in Pega Version 8.1.8
If a report was edited and closed without saving, the dirty check worked as expected. However, if new columns or filters were added and the report closed without saving, the dirty check did not appear. This has been resolved by updating the check logic.
SR-D53176 · Issue 541793
Error when adding function filter will persist
Resolved in Pega Version 8.1.8
When an exception occurred while adding a filter in the report viewer, the error was shown but cleared due to an immediate refresh of the parent section. Analysis found that step2 of pzGetFiltersFromContent was failing, after which the error was shown, the section reload happened, and the error disappeared. To resolve the error being cleared prematurely, the pzOnLoadReloadReport control has been modified so that when there are messages on the top level page (pyReportContentPage), a parameter will be set on HarnessContextMgr to not to clear them during the next refresh call.
SR-D76204 · Issue 543591
Index conflict resolution logic updated
Resolved in Pega Version 8.1.8
After configuring a dedicated index on delivered Class - PegaCA-Interface-Contact, trying to generate the index resulted in an error indicating a type conflict in delivered classes/properties. This has been resolved by updating the conflict resolution logic.
INC-175994 · Issue 667480
Removed redundant Microsoft Outlook email interaction chain
Resolved in Pega Version 8.5.6
When opening an email interaction case, the email editor user interface area showed the complete email chain of the email for every new message that came in related to the case. This was traced to the difference in the selectors that various email clients use to construct a response to an email with email history in it, and has been resolved by updating the selectors for Microsoft Outlook in pyRichTextEmailHistorySelector so no conversation is repeated when using that client.
INC-184155 · Issue 673073
Entity Detection prefers first detected entity
Resolved in Pega Version 8.5.6
Entity detection shown in the "Training data" tab of the email channel did not match with the results of running the corresponding text analyzer rule. This occurred when a single piece of text was detected as multiple entity values, which led to the last entity detected being picked for case mapping because of the unclear scenario of duplicate entities. To resolve this, pxmapresponseentities has been updated to prefer the first detected entity.
INC-184243 · Issue 682331
Page data preserved for WebChat timeouts
Resolved in Pega Version 8.5.6
Attempting to change the font size in Webchatbot after the interaction time-out resulted in a DisplayError screen. This was traced to the page data not being available, and has been resolved by preserving workPage and newAssignPage for this use.
INC-184902 · Issue 669451
Corrected portal image display for authenticated request
Resolved in Pega Version 8.5.6
Email images for the user portal were not displayed in the browser but were showing correctly in the manager portal. The URL to the image was the same in both cases, however for the user portal the URL request was requiring authentication. This has been resolved by updating the API to use currentsessionURL.
INC-185255 · Issue 669439
More responsive attachment loading for interaction portal
Resolved in Pega Version 8.5.6
Attempting to view a large email attachment in the interaction portal was resulting in slow loading and page responsiveness issues. Investigation showed there were numerous unnecessary height calculations happening when checking the dom elements, and this has been resolved with an update which will use the property mapping js file to make the screen more responsive when highlighting.