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-B47858 · Issue 304348
Access Group Guardrail warning removed from password change
Resolved in Pega Version 7.4
Changing the password for the '[email protected]' operator generated the warning: 'The same Access Group should not be shared by Operators and Requestor Types. Access group PRPC:Agents was also referenced by Requestor Type DATA-ADMIN-REQUESTOR PRPC!BATCH'. The password change did take effect as expected. This guardrail warning was shown if the Access group used by the [email protected] operator, i.e. PRPC:Agents, was specified in any of Data-Admin-Requestor instance, and has been resolved by removing the unnecessary check.
SR-B96972 · Issue 343423
Specification rule save-as loads requirements
Resolved in Pega Version 7.4
While doing 'Save As' of a Specification rule from a locked ruleset version to a higher unlocked version of the ruleset, the linked Requirements were not shown in the Requirements section under the Details tab. Sometimes a refresh would show the requirements, but intermittently an exception would be generated. This was traced to the system not auto-populating the requirements list on 'save as' of the specification, and code has been added to PostActionSaveAs of the 'Rule-Application-UseCase' class to populate the Requirements link on 'save as' of this rule.
SR-C1910 · Issue 344160
Performance improvement for D_StartingFlows
Resolved in Pega Version 7.4
The algorithm for loading D_StartingFlows has been adjusted to be specific to when "optimistic packaging" is enabled, so that D_StartingFlows is not loaded during typical delta sync response generation.