SR-B84636 · Issue 335909
Needed functions/function libraries ported into JS text rules for mobile validation
Resolved in Pega Version 7.4
A validate rule with a simple string expressions attached to a flow action of an offline-enabled case failed to execute when the flow action was submitted in an Android app. This was traced to new handling for Validate rules usage in offline which relied on select Function rules ported to JavaScript functions, and the desired functions has not been ported. These functions/function libraries will now be ported into JS text rules.
SR-B84636 · Issue 335930
Needed functions/function libraries ported into JS text rules for mobile validation
Resolved in Pega Version 7.4
A validate rule with a simple string expressions attached to a flow action of an offline-enabled case failed to execute when the flow action was submitted in an Android app. This was traced to new handling for Validate rules usage in offline which relied on select Function rules ported to JavaScript functions, and the desired functions has not been ported. These functions/function libraries will now be ported into JS text rules.
SR-B84636 · Issue 334503
Needed functions/function libraries ported into JS text rules for mobile validation
Resolved in Pega Version 7.4
A validate rule with a simple string expressions attached to a flow action of an offline-enabled case failed to execute when the flow action was submitted in an Android app. This was traced to new handling for Validate rules usage in offline which relied on select Function rules ported to JavaScript functions, and the desired functions has not been ported. These functions/function libraries will now be ported into JS text rules.
SR-B86387 · Issue 339475
Offline mobile Work ID sync issue fixed
Resolved in Pega Version 7.4
When creating a new Case on the mobile offline application, temporary IDs are created. Once synced with the server, the Server IDs are correctly updated on the device. However, if 3-4 new cases were created, one case was failing due to the Server ID not correctly being updated on the device. This meant the device still carried the temp ID and failed to sync. This was traced to EventListener_executeFunction returning false when there was any exception in the subscribed function during its execution, making the subscriber function null in the Listeners array. To fix this, a safe check has been added in syncAttachmentDP and a try catch has been added in dataPageUpdateAction to handle the exceptions.
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.