SR-123581 · Issue 188015
Scrolling corrected for Safari on mobile devices
Resolved in Pega Version 7.1.8
When using the global search on a tablet or mobile device, the results are displayed in a modal pop up in the browser. However, scrolling was not working when using Safari on a mobile device. To correct this, the Search Panel CSS and js were modified to enable scroll support on mobile devices.
SR-125913 · Issue 192447
Fixed file attachments in Mobile
Resolved in Pega Version 7.1.8
When using the AttachContent Control functionality in mobile, attaching a file popped up a window with the message 'File attached successfully', but no Action Sets associated with file attachments were actually run. Using the same functionality on desktop did not have any issues. This problem was traced to an error in the JavaScript code for the mobile control relating to the access group, and has been corrected.
SR-A18905 · Issue 233955
OrgName error resolved for MobileOffline:Obj-Open-By-Handle
Resolved in Pega Version 7.2.1
If Obj-Open-By-Handle was configured on the Org Name link in MobileOffline for the master details of a Contact Work Object, clicking on the link generated an "Empty Work Item Handle" error despite the OrganizationID(Handle) being present on the data page. This was an error in the actions array for the "runScript" API, and has been fixed.
SR-A21298 · Issue 239141
NPE on mobile list open resolved
Resolved in Pega Version 7.2.1
A null pointer exception was being generated on mobile device when opening list items. A null check has been added to pega_ui_modaldialog to resolve this exception.
SR-A21636 · Issue 240162
Fixed auto-complete use in iPhone Opportunity creation
Resolved in Pega Version 7.2.1
Issues were seen when selecting items using Auto-Complete on an iPhone while creating an Opportunity. This was due to a positioning error in the logic, and has been fixed.
SR-A24787 · Issue 247535
SA mobile app hang fixed
Resolved in Pega Version 7.2.1
Hitting the 'back' button in the SA mobile app before a work-object fully loaded the master-details caused the app to hang. This was traced to an issue with the thread switching that caused a JS exception, and has been resolved.
SR-A24787 · Issue 245849
SA mobile app hang fixed
Resolved in Pega Version 7.2.1
Hitting the 'back' button in the SA mobile app before a work-object fully loaded the master-details caused the app to hang. This was traced to an issue with the thread switching that caused a JS exception, and has been resolved.
SR-D17418 · Issue 498723
Attached note header displays properly in Hebrew locale
Resolved in Pega Version 8.4
With the locale set to Hebrew, the whole portal is presented correctly from right to left, but when opening a case note (attached email) the header was not displayed as right to left. This has been resolved by updating the 'DisplayNote' HTML of class 'Data-WorkAttach-Note' and 'Show' HTML of class 'Data-Corr-Email' to use locale information from the operator.
SR-D17575 · Issue 492689
Survey route to work queue option restored for smartshape
Resolved in Pega Version 8.4
After upgrade, routing to workqueue was no longer available for the new create survey smart shape. This has been restored.
SR-D18589 · Issue 495717
Google Map API updated
Resolved in Pega Version 8.4
When using Address Map control with enabled markers whose source is a datapage, the location in the map was redirected as expected to the address populated by the datapage, but the marker overlay that appeared by default containing address details and a link to "Open in Google Maps" did not load. Clicking on random places on the map caused it to load correctly. This has been corrected with the creation of a custom activity to get section markup that will use reload section with proper context to fix the issue. In addition, enhancements have been made to enable automatic upgrade of existing apps which use Address Map to use pxMap by auto-generating pxMap from the existing configuration. Properties set in Address Map's design time configuration should be mapped to corresponding properties in pxMap as given below. If report definition, clipboard page. or list property was used as marker source, a data page will need to be created manually. 'Starting Lat, Long' property is mapped to 'Custom initial lat / long' 'Markers source' is mapped to 'MARKERS' as follows: - 'None' to 'None' - 'Data page' to 'Data page', 'Property for location' -> 'Location property', 'Marker info section' -> 'Info section' - 'Property' to 'Property', 'Address property' -> 'Address property', 'Allow marker repositioning to change the address value' -> 'Drag marker position to update address value', 'Report lat long in property' -> 'Lat / long logging property', 'Report incorrect address' and 'Error message' is ignored at this time - 'Report definition' is ignored - 'Clipboard page' is ignored - 'List defined on property' is ignored 'Visibility' and 'Tour ID' are mapped 1to1 It is also possible to disable rendering of the Map control from the Address Map configuration: when switched off, pxAddressMap will be generated instead of pxMap.