INC-201633 · Issue 706557
Reload icon disappears when refresh is ready
Resolved in Pega Version 8.8
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-205683 · Issue 702563
Data transform actions supported in offline app
Resolved in Pega Version 8.8
Support has been added for pre- and post-processing data transform functionality and validation in the local actions of the offline app.
INC-210526 · Issue 705638
Mobile supports icons for file attachment
Resolved in Pega Version 8.8
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 709648
Added fallback handling for missing Google Maps marker value
Resolved in Pega Version 8.8
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 709283
Access group context handling updated for Mobile
Resolved in Pega Version 8.8
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.
INC-220749 · Issue 719942
Optimizations added for large data pages
Resolved in Pega Version 8.8
Attempting to download a material master which has 2 million records timed out after 5 minutes. This has been resolved by adding optimizations that include the batching of large data pages.
INC-222126 · Issue 721902
Improvement for mobile display error related to harness timing
Resolved in Pega Version 8.8
After updating from 8.1 to 8.6, working very quickly on mobile to create a case and refresh it resulted in a "Display error" screen that included the message "Failed to find instance @baseclase.pyCreate of type Rule-HTML-Harness". This was caused by the system not being initialized with the needed content and some target parameters therefore being evaluated as null. A preliminary fix for closeDocCallback when WebView is not loaded has been added which has significantly reduced the frequency of this issue. Additional work will be done towards a complete resolution in a future release.
INC-224923 · Issue 735843
Autocomplete field loads in offline iOS
Resolved in Pega Version 8.8
After converting large data sets to the Large Data Page Structure, some data pages were working in the Android app but not in iOS when Offline Support was enabled. This was traced to the autocomplete field of type 'text' not loading correctly, and has been resolved.
INC-226156 · Issue 735745
Autocomplete field loads in offline iOS
Resolved in Pega Version 8.8
After converting large data sets to the Large Data Page Structure, some data pages were working in the Android app but not in iOS when Offline Support was enabled. This was traced to the autocomplete field of type 'text' not loading correctly, and has been resolved.
INC-201109 · Issue 701941
Servlet management documentation updated
Resolved in Pega Version 8.8
The documentation for Servlet management has been updated to clarify that before you can move URL patterns using the Servlet Management landing page, you must remove the web.xml file from your Pega Cloud environment. If the * URL pattern is still available in the web.xml file, it remains in read only mode and cannot be edited using the indicated steps. More information is available at https://docs.pega.com/security/87/moving-url-pattern-between-servlets