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-152542 · Issue 610947
Support extended for document tags
Resolved in Pega Version 8.7
An enhancement has been added to extend the support for document tags, including showing tags added to a case in a workpool other than the application workpool; showing tags from other operators such as partner sales rep, sales reps, etc; and displaying tags in the "recently added by me" section.
INC-160485 · Issue 655297
Trailing "/" added to public links for SSO use
Resolved in Pega Version 8.7
Links generated using pyWorkLinkWithLabel were not working with SSO due to not having a trailing "/" on the URL. This has been corrected by adding code to append the "/" if the public link url doesn't end with it.
INC-161214 · Issue 640893
Push notification of shape-created child case opens correct case
Resolved in Pega Version 8.7
In a scenario with two cases, CaseA and its child case, CaseB, when CaseB was created from CaseA with a standard shape and a push notification was sent right after creation, the "Custom message" notification received on a mobile device opened CaseA instead of CaseB. If CaseB was created as a standalone case, the push notification opened it properly. This was traced to an edge case where the Primary.pzInsKey was empty because the child case was not available in database when the push notification payload was created by push shape, leading to the CaseID retrieved by getInstanceHandleFromPage to fetch the parent Case ID instead. This has been resolved by modifying the process to get the pzInsKey from the step page.