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-120326 · Issue 564437
Landing page refresh modified to avoid frequent reloads
Resolved in Pega Version 8.1.9
Approximately every two weeks, clients were able to login but it was not possible to work as the landing page refreshed constantly until all of the nodes were rebooted and the issue was cleared. Investigation indicated the frequent reloads were related to the cacheing of the operator details, and this has been resolved by updating the datapage reload strategy based on 'when' so frequent reloads will be avoided.
INC-130158 · Issue 572051
iOS file attachment works in Safari
Resolved in Pega Version 8.1.9
Attaching PDF and images from iOS devices using Safari was not working. This was traced to iOS 13 launching the file browser by default if the file-input element had an accept=/ attribute value pair, and has been resolved.
INC-136752 · Issue 587728
Adding handling for custom image on S3 storage space
Resolved in Pega Version 8.1.9
When using an S3 repository for Content storage, trying to create a new space with a custom image did not upload the image. Investigation showed that when attachment storage is configured as an external repository, the pyAttachStream property which is used to create the the thumbnail was getting cleaned as part of the saving logic. This has been resolved by adding an update that will hold the attachStream value in a local property before calling attachment save.
INC-141920 · Issue 595139
Unable to delete the Spaces after loggin off
Resolved in Pega Version 8.1.9
If a Space was created and then deleted in the same login session, the delete worked as expected. If the Space was created and then actions were taken to delete it on a subsequent login, the Space was not actually deleted. Investigation showed this was due to v8.1 not having a stream/blob (PZPVSTREAM) in the pc_work_group table, and this behavior was the result of extra properties included on the page. To resolve this, the extra properties on the page will be removed before the obj-save/commit .