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.
INC-192649 · Issue 706134
Basereference context available for attach content control
Resolved in Pega Version 8.6.4
An "undefined" error occurred when attaching a file using the attach content control in the mobile harness. To resolve this, support has been added to run attachcontent in basereference context. This can be enabled by setting pega.attachToCtxPage to true.
INC-195519 · Issue 698498
Support added for using CFW when Pega server is unavailable
Resolved in Pega Version 8.6.4
Data synchronization changes have been added to allow Client for Windows to work in offline mode without an AppCache manifest.
INC-195601 · Issue 685771
Basereference context available for attach content control
Resolved in Pega Version 8.6.4
An "undefined" error occurred when attaching a file using the attach content control in the mobile harness. To resolve this, support has been added to run attachcontent in basereference context. This can be enabled by setting pega.attachToCtxPage to true.
INC-201633 · Issue 703799
Reload icon disappears when refresh is ready
Resolved in Pega Version 8.6.4
After updating the Field Service Mobile App from Pega 8.3 to Pega 8.6, the wait icon continued to be visible even after the refresh was completed. This has been resolved.
INC-206049 · Issue 703468
Resolved activity registration error for Scan Barcode/QR Code
Resolved in Pega Version 8.6.4
Attempting to add the action 'Scan Barcode/QR Code' to a button generated the warning "Unauthorized request detected : Unregistered request encountered with params pyActivity:pzRunActionWrapper pySubAction:runAct pzActivity:pzScanCode". Investigation showed this was due to the pzScanCode activity referred to in pzpega_control_actions_scanCode.js file not being registered, and has been resolved by adding code to register the necessary events for both button and navigation.
INC-210526 · Issue 705640
Mobile supports icons for file attachment
Resolved in Pega Version 8.6.4
Attaching a file to a case in a mobile browser generated a script error popup. This has been resolved with code to support using icons to attach files on mobile.
INC-211208 · Issue 709646
Added fallback handling for missing Google Maps marker value
Resolved in Pega Version 8.6.4
The Google maps location position control was not showing the marker if the marker source was a Property. No issues were seen if a data page was used as the marker source. This was due to the pega.util.Dom.getElementsByName(markerPropertyHandle) being returned as null. Since the property value was not found in DOM, the latitude and longitude values were not resolved for the marker object. This has been resolved by relying on the markerPropertyValue as a fallback in case the property bound to the marker is not part of the DOM.
INC-214160 · Issue 709281
Access group context handling updated for Mobile
Resolved in Pega Version 8.6.4
After update, a new mobile application for a specific access group was not applying the correct access group for an operator with multiple access groups but instead used the default access group. This has been resolved by moving the logic responsible for switching access groups for Pega Mobile Client from the Authorization.getInitialAccessGroup class to the SessionAccessgroupInfo class to ensure Authorization/SessionAuthorization gets the information about the default access group for the current context.