SR-B74088 · Issue 324942
Enhancement for Optimizing Packaging during full & delta sync
Resolved in Pega Version 7.3.1
As part of an enhancement for more contextual, optimistic packaging algorithm in certain conditions, packaging can be optimized based on a setting available at the case type. For example, most Field Service applications where offline capability is heavily used don't have or need the ability to instantiate or create new cases, but rather work on existing assignments routed to the agents. Some sites have the additional constraint where the case types or the flows within a case type may be large in number and dynamically created, which means the first full sync will just not be sufficient for the user to work on later created assignments. This has an adverse impact on the performance of the full sync and the first login time. The following changes have been introduced: - On delta sync - if a new work item ( of new case type which is not there during full sync packaging ) is added to work list. All the dependent rules of this new case type will be packaged and sent to HC. Added an checkbox in the case type rule "Only offline when in user's worklist" which will be visible only when "Enable Offline" is checked. - Provided a new when rule pyPackageAssignmentFlows which is set to false by default. When the true, all the case type with "Only offline when in user's worklist" will have selective flow packaging. - Create a class structure with a page group to hold full packaging and optimized packaging Application.pyOfflineCaseTypes("full") Application.pyOfflineCaseTypes("optimized") Above properties are populated in pzGetStartingFlows activity which is ran on delta sync and full sync. - Flows that are created in the case with "Only offline when in user's worklist" check are listed in pzDataSyncGetworkList which will be packaged during delta sync. The flows are listed for packaging if there is any Work Object created, flow is retrieved from the Assignment's pzInsKey key, and Flow key is built. Changes are made in the PackageRuntime.java to iterate the flow and perform packaging.
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.