INC-192649 · Issue 706133
Basereference context available for attach content control
Resolved in Pega Version 8.7.2
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-195601 · Issue 685770
Basereference context available for attach content control
Resolved in Pega Version 8.7.2
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-198249 · Issue 705092
Security updates for packaging mobile app
Resolved in Pega Version 8.7.2
Unsafe properties such as password and userId are now explicitly filtered from the Operator object during the mobile app packaging process.
INC-201633 · Issue 706556
Reload icon disappears when refresh is ready
Resolved in Pega Version 8.7.2
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-210526 · Issue 705639
Mobile supports icons for file attachment
Resolved in Pega Version 8.7.2
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 709647
Added fallback handling for missing Google Maps marker value
Resolved in Pega Version 8.7.2
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 709282
Access group context handling updated for Mobile
Resolved in Pega Version 8.7.2
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.