SR-D85551 · Issue 548076
Resolved touch events issue with updated Google Chrome
Resolved in Pega Version 8.5
After upgrading Google Chrome, touch events on a flow action under the Action Button in a case or on the application under "Launch web interface" were not reacting and the flow actions were not accessed. Investigation showed that Google Chrome's latest upgrade (79.0.3945.130) removed the ontouchstart property in the window, causing the isTouchable capability identification method to fail. This has been resolved by adding a check for navigator.maxTouchPoints to identify for Google Chrome whether the device involved has a touchscreen.
SR-D76620 · Issue 544577
Resolved touch events issue with updated Google Chrome
Resolved in Pega Version 8.5
After upgrading Google Chrome, touch events on a flow action under the Action Button in a case or on the application under "Launch web interface" were not reacting and the flow actions were not accessed. Investigation showed that Google Chrome's latest upgrade (79.0.3945.130) removed the ontouchstart property in the window, causing the isTouchable capability identification method to fail. This has been resolved by adding a check for navigator.maxTouchPoints to identify for Google Chrome whether the device involved has a touchscreen.
SR-D78306 · Issue 542741
Complex question checkbox labels displayed
Resolved in Pega Version 8.5
Checkbox labels were not shown when a survey was rendered in read-only mode. This has been resolved by updating pzComplexQuestionCheckBoxTemplateRowDetails and ComplexQuestionCheckboxTemplate section to show labels and icons for check boxes when a complex checkbox question is displayed in read-only mode.
SR-D68572 · Issue 543004
Added check for duplicate attachment names with S3
Resolved in Pega Version 8.5
S3 Storage does not allow duplicate file names, but the AttachContent function was allowing duplicate file attachments. Due to this, the sync was failing to attach on the server and the message was never communicated to the client. This has been resolved by adding a check for duplicate file names when the storage is repository.
SR-D76927 · Issue 541423
VirusCheck added to all Pulse uploads
Resolved in Pega Version 8.5
The upload file activity has been updated to invoke VirusCheckActivity for all Pulse uploads.
SR-D91532 · Issue 556405
Resolved Clear Cache error for mobile client
Resolved in Pega Version 8.5
When attempting to clear local storage while logged into the Mobile Client, the error message "You need to be able to connect to the server in order to clear the storage" appeared. This was traced to the application being configured to disable a user's web session immediately after log in, and was due to the "Clear Cache" functionality failing while attempting an AJAX request to invoke the server's "pzAmIOnline" activity. While there was a workaround of using the check box "Access group requires a connection for portions of the application", this has been resolved by updating the Settings - Clear Cache functionality in order be able to detect if it's online in a different way.
SR-D85780 · Issue 547814
Corrected iosVersion handling for getDirections
Resolved in Pega Version 8.5
When opening the map function in the iPhone app, it first navigated to Google maps but clicking on 'get directions' opened Apple maps. This was traced to pzpega_control_actions_getDirections. When using the getMapURL function the value being assigned for iosVersion dictates the behavior: If the iosVersion is greater than 8 it opens Google maps, else Apple maps. However, an error caused the value to be sent as string instead of integer, causing the iosVersion check to fail. This has been corrected.
SR-D67150 · Issue 532023
Resolved attachments when using Mobile page message setting
Resolved in Pega Version 8.5
When using page-level error messages for a work object, trying to add an attachment to that work object resulted in an error and the attachment failed. This has been resolved by adding an error check in the pzAttachContentFile activity.
SR-D87188 · Issue 551350
Mentioned user in Pulse correctly converted to hyperlink
Resolved in Pega Version 8.5
In the Interaction portal, mentioning a user in Pulse using @ was not converting the name to the user name with hyperlink for Email Interactions. @ mentions were working as as expected in Phone Interactions. This problem was introduced as part of using OWASP to sanitize HTML user input in Rich Text support, and was due to OWASP converting @ to an HTML entity. To resolve this, the @ will be excepted from HTML conversion.
SR-D63638 · Issue 544017
Performance improvements for opening cases with embedded images
Resolved in Pega Version 8.5
Opening cases containing email interactions was taking an excessive amount of time. This was traced to the use of embedded images, icons, etc, in the message body and signature, and was caused by the pyGetAttachmentsbyCID activity running multiple times due to discussion threads that were duplicated over and over. In some cases, more than 360 calls to the database were seen. This has been resolved by shifting some case opening processes to executing when the listener thread gets the mail, and storing the results in a .pynote property, and a URL will be used to get images instead of embedding them directly to the HTML. If preferred, this can be reverted to the previous behavior by changing the when rule (pyUseCachedHtmlForDisplay) to false.