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-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.
SR-C496 · Issue 343628
Images render correctly in iOS/Android
Resolved in Pega Version 7.4
The mobile app was not rendering images on IOS or Android devices, but the images were visible when running the mobile view from a desktop browser. In addition, the vertical scroll bar was not displayed on lengthy screens. This was due to the template code not appending '+xml' to MIME type when the SVG content did not start with "<?xml ," and has been fixed by always concatenating +xml in IconAssembly.java.
SR-C496 · Issue 342641
Images render correctly in iOS/Android
Resolved in Pega Version 7.4
The mobile app was not rendering images on IOS or Android devices, but the images were visible when running the mobile view from a desktop browser. In addition, the vertical scroll bar was not displayed on lengthy screens. This was due to the template code not appending '+xml' to MIME type when the SVG content did not start with "<?xml ," and has been fixed by always concatenating +xml in IconAssembly.java.
SR-B94506 · Issue 341185
Unneeded clipboard use cleared during sync
Resolved in Pega Version 7.4
During the "delta sync" process, a very large clipboard size (96 MB) was observed for offline sync service requestors. Further analysis showed that the application page contained a property pyOfflineCases which increased the application page size from 28K to 679K. Since the property isn't present in the saved application rule model, the pzDataSyncPackager rule will clear it from the clipboard to improve performance.
INC-135015 · Issue 591982
Handling added for overriding questions rules
Resolved in Pega Version 8.6
After overriding questions rules and then upgrading/validating Question Groups, questions were not shown. It was necessary to manually edit, save, and refresh for the questions to appear, affecting mainly Rule-PegaQ-QuestionGroup rules. This was traced to missing handling for this usecase. The commit was added in Revalidate and Save, which was committing different data because the upgraded data was not copied back to step page being used. Due to this, the commit in BulkValidateSave was overriding the changes done in the pzUpgradeSurveyInstance activity, and the survey upgrade was failing. To support this use, Page-Copy has been added to pzUpgradeSurveyInstance after the pzSaveSurveyInstance call step to copy the updated data to the step page which will later be committed by BulkValidateSave during revalidate and save.