Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

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.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us