SR-B87284 · Issue 336618
Menus work for Offline group
Resolved in Pega Version 7.4
When working online in an access group that was offline enabled, clicking a more icon (3 dots) to present a menu with more actions did not produce a popup menu. This was traced to the ChangeTracker not reinitializing during offline packing, causing the THREAD to not be properly switched. To fix this, the code has been modified to ensure ChangeTracker is reinitializing for every harness packing and the THREAD is properly switched.
SR-B87284 · Issue 315103
Menus work for Offline group
Resolved in Pega Version 7.4
When working online in an access group that was offline enabled, clicking a more icon (3 dots) to present a menu with more actions did not produce a popup menu. This was traced to the ChangeTracker not reinitializing during offline packing, causing the THREAD to not be properly switched. To fix this, the code has been modified to ensure ChangeTracker is reinitializing for every harness packing and the THREAD is properly switched.
SR-B94429 · Issue 341175
Mobile client correctly opens child case
Resolved in Pega Version 7.4
Given a scenario where a parent case was online-only and the child case was offline-enabled, the offline-enabled child case was not able to be opened when the mobile device was in online mode. This was traced to the handling for processing the offline case and retrieving the parent case work object resulting in newAssignPage being lost, and has been fixed.
SR-C10224 · Issue 351129
D_PZOFFLINEATTACHMENTLIST reused for offline delta sync
Resolved in Pega Version 7.4
In offline delta sync, the data page D_PZOFFLINEATTACHMENTLIST was populated twice. This was caused by pzDataSyncPackager populating the page on the initial line tools.findPage call, deleting the new page, then issuing another findPage to recreate the page. The code has now been modified to use the page from the clipboard instead of re-creating it.
SR-C10909 · Issue 352697
Handling added for null OfflineCaseAttachment source
Resolved in Pega Version 7.4
An exception was being generated on each offline mobile-sync with the tracer message: "Unable to load data page D_pzOfflineCaseAttachments. Required parameter LinkRefFrom cannot be blank." This occurred when the required parameters for D_pzOfflineCaseAttachments DP were not populated. To address this, D_pzOfflineCaseAttachments DP has been changed to the pyGetAllOfflineAttachments activity, and handling has been added to exit if the parameter is empty.
SR-C573 · Issue 346166
Sync error page retains uploaded changes
Resolved in Pega Version 7.4
After changes were made to a case offline and the case was then uploaded after the case had already been reassigned to someone else, a Pega-Work-OfflineSync work object was created and a copy of the case data was placed on the embedded pySyncErrorCase page but the changes were missing. To fix this, the pzStoreAndForwardProcessItems function has been modified to ensure the changes from the uploaded version are present on the pySyncErrorCase page.
SR-C6870 · Issue 349625
Performance improvement for finishAssignment sync
Resolved in Pega Version 7.4
Analysis of a trace on the output related to a finishAssignment sync found a second read of the work object within the pzDataSyncPackageCases activity (after it was previously read in pzCheckLockingMode). In order to improve performance, the system will make use of the existing open work object to avoid the dual DB read.
SR-C7706 · Issue 350556
Performance improvement for WorkID sync
Resolved in Pega Version 7.4
In order to improve performance, changes have been made to the pzStoreAndForwardProcessItems and pzGetAllOfflineWorkIDs activities: these will populate skipDPOfflineWorkIDsInteraction to conditionally skip the DP packaging, in order to ensure the offline temp ID reconciliation does not populate the data D_pzOfflineWorkIDs twice during delta sync.
SR-B78040 · Issue 334019
Shape-retrieval logic updated for nested proxy flows
Resolved in Pega Version 7.4
A complicated proxy flow with nested subprocesses was hanging when 'next' was clicked. This was traced to getPreviousShape failing to get the correct shape due to the nested configuration, and has been fixed by modifying the logic in the getPreviousShape and hasPreviousShape methods used by process_flow.js to find the correct shape.
SR-B84173 · Issue 339408
Fixed intermittent Bulk Transfer failure
Resolved in Pega Version 7.4
Bulk Transfer action was not working for some cases in a flow which applied to an embedded data class, resulting in nothing showing up when attempting to 'transfer' those cases. This was caused by bulk transfer running the "pyTransferAssignment" flow action on the flow's applies to class (i.e., embedded data class); that flow action calls "pyTransferAssignment" section which is present in "@baseclass" which would run on the top page. In case of bulk transfer, this top page would be the flow's applies-to class, causing failure in cases using "Data-Party" flows. To correct this, the system will call the top page FA for embedded pages.