SR-D74839 · Issue 537323
Corrected map zoom issue with iOS13
Resolved in Pega Version 8.4.1
After including a map control with markers in an application for iOS13, viewing via a mobile app and zooming introduces a gray bar across the map. This has been resolved by setting transform translateZ to the div of address map.
SR-D76620 · Issue 544578
Resolved touch events issue with updated Google Chrome
Resolved in Pega Version 8.4.1
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-D76927 · Issue 541424
VirusCheck added to all Pulse uploads
Resolved in Pega Version 8.4.1
The upload file activity has been updated to invoke VirusCheckActivity for all Pulse uploads.
SR-D77268 · Issue 542339
Updated URL opening for iOS 12 & 13
Resolved in Pega Version 8.4.1
Attempting to open a URL did not work on iPad/iPhone with iOS 12 and 13 and PIMC version 8.3.500. This has been resolved by updating previewPIMCAttachmentOnline function to handle URL opening by using the application.openurl function.
SR-D81859 · Issue 543766
Maps and signatures inside layout groups scroll correctly
Resolved in Pega Version 8.4.1
A map configured in the screen was getting grayed out while scrolling horizontally. Analysis showed that when an address map is inside a layout group, the layout group swipe was triggered instead of scrolling. To resolve this, the target parent now has the data attribute "data-nogestures" = true so the layout group swipe will not be triggered. This will also prevent swipe on signature while scrolling horizontally.
SR-D85551 · Issue 548077
Resolved touch events issue with updated Google Chrome
Resolved in Pega Version 8.4.1
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-D85780 · Issue 547815
Corrected iosVersion handling for getDirections
Resolved in Pega Version 8.4.1
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-D70569 · Issue 538510
Tracer retains modified user settings
Resolved in Pega Version 8.4.1
User settings in tracer were not shown when the settings window was closed and reopened. Investigation showed that settings are filtered based on watchInsKey, but this parameter was passed as "null" for global tracer because of a missing condition to check the session type. This has been resolved by adding a check so the WatchInsKey parameter is passed if the session type is rule watch.
SR-D75431 · Issue 544199
DMaps cleared to set correct JobScheduler next run time
Resolved in Pega Version 8.4.1
When items were added into a QP, the items shown under Scheduled and weren't being processed immediately. Investigation found that the job scheduler which fetched the entries for QP to process wasn't running as expected, and the "Next run" time stamp for JS was incorrectly populated and entries weren't being fetched at all. To correct this, updates have been made to clear entries in DMap belonging to the node during shutdown and from the membership listener so the correct next run time is set.
SR-D76861 · Issue 544607
Job Scheduler will be stopped by node shutdown detection
Resolved in Pega Version 8.4.1
LifeCycle Job Scheduler was trying to start already stopped background services during node shutdown, causing exceptions to be logged. This has been resolved by stopping Job Scheduler execution when node shutdown is detected.