SR-C5089 · Issue 347301
PackageRequest page deleted after each SYNC
Resolved in Pega Version 7.4
Analysis of clipboard use for requestors during/after sync transactions showed that a few larger data pages remained after each sync. In order to improve performance, the PackageRequest page will be removed at the end of the pzGetAndStreamPackage activity.
SR-C5479 · Issue 352671
AddressMap places marker
Resolved in Pega Version 7.4
The marker was not showing in mobile when pxAddressMap was configured on a Dynamic layout with collapsible configuration. This was traced to the address map loading within a hidden div, and has been fixed.
SR-C5479 · Issue 349418
AddressMap places marker
Resolved in Pega Version 7.4
The marker was not showing in mobile when pxAddressMap was configured on a Dynamic layout with collapsible configuration. This was traced to the address map loading within a hidden div, and has been fixed.
SR-C5629 · Issue 347624
Performance improvement for mobile with disabled Push
Resolved in Pega Version 7.4
Changes have been made to the logic for the mobile Push feature in order to improve performance when Push is disabled.
SR-C5700 · Issue 349622
Mobile performance improvements related to SIIP key delta syncs
Resolved in Pega Version 7.4
Mobile performance was slowed by unnecessary SIIP key delta-syncs. To improve performance, engine changes have been made to send empty SIIP for rules which don't change during delta sync, and the pzStartSynchronization service was modified to skip objects with empty SIIP keys.
SR-C6872 · Issue 351148
Mobile performance improvements related to SIIP key delta syncs
Resolved in Pega Version 7.4
Mobile performance was slowed by unnecessary SIIP key delta-syncs. To improve performance, engine changes have been made to send empty SIIP for rules which don't change during delta sync, and the pzStartSynchronization service was modified to skip objects with empty SIIP keys.
SR-C8008 · Issue 351130
TouchID restored for iOS
Resolved in Pega Version 7.4
The TouchID checkbox was not showing up on iPhone. This was caused by a missing compatibility layer in the hybrid client that had not been added to the iOS project. The resource has now been properly linked.
SR-C8798 · Issue 351150
Check added for current mobile login before requesting login
Resolved in Pega Version 7.4
When fast-starting is disabled and "Always prompt for password on start" is selected in the mobile app tab, a second request of ShortPass API (another action for an already started application) for a web login webview was calling sign in once again. This caused a new session cookie to be created, leading to synchronization issues and closing of the API already running for the first call. This was caused by a data-synch issue for actions opened by the openURL app, and has been fixed by adding a checking condition for a logged operator ID saved in window.launchbox.AccountManager.identifier that will bypass the login form when it contains any value (operator ID).
SR-C8798 · Issue 340002
Check added for current mobile login before requesting login
Resolved in Pega Version 7.4
When fast-starting is disabled and "Always prompt for password on start" is selected in the mobile app tab, a second request of ShortPass API (another action for an already started application) for a web login webview was calling sign in once again. This caused a new session cookie to be created, leading to synchronization issues and closing of the API already running for the first call. This was caused by a data-synch issue for actions opened by the openURL app, and has been fixed by adding a checking condition for a logged operator ID saved in window.launchbox.AccountManager.identifier that will bypass the login form when it contains any value (operator ID).
SR-C9000 · Issue 351637
Mobile DB sync performance improvements
Resolved in Pega Version 7.4
Under heavy load testing, the mobile DB synchronization process was found to be a bottleneck due to resource locking. This has been fixed by replacing the sync with ReentrantReadWriteLock which allows any number of threads to "read" the protected resource but will block when the resources is being modified.