INC-213308 · Issue 712075
Fallback added for missing fileName in MultipartHTTPResponse
Resolved in Pega Version 8.6.4
Given a multipart/form-data response with multiple attachments, when there was no explicit fileName header provided for a body part, the engine skipped processing the part and no data was present on pyRequestAttachmentPage. This has been resolved by adding a fallback in HTTPClientUtils#handleMultipartHTTPResponse() so that if no fileName is present, the 'name' parameter of the Content-Disposition header field will be used.
INC-213502 · Issue 711797
Updated context handling for DxAPI Perform Assignment lock
Resolved in Pega Version 8.6.4
The DxAPI Perform Assignment was generating the error "ValidationMessage:Unable to unlock GROUP-DISPUTES-WORK". This has been resolved by adding an update to ensure proper context is set for getting an additional lock handle.
INC-213808 · Issue 710298
Stability enhancement to improve platform reliability and resiliency
Resolved in Pega Version 8.6.4
During a NBA campaign run, the data flow partition became stuck in the in-progress status and the campaign run did not complete. NoClassDefFoundException errors were logged, indicating a connectivity issue with the database after which the node was not able to recover successfully. This has been resolved by adding an enhancement to better handle situations where a database outage is detected.
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.