SR-A93531 · Issue 266554
Corrected mobile login issues after sync
Resolved in Pega Version 7.2.2
After forcing a full sync, users already logged into the app (i.e. packaged data is present in client) observed login issues thereafter while new users did not. This has been corrected by updating the logic in the pzpega_ui_doc_HCLoadManager getOfflineStorageCount API call.
SR-A91327 · Issue 259570
Modified cookie name handling to clear operator sync between logins
Resolved in Pega Version 7.2.2
Full sync was happening only at the very initial time the user tried to login and not at every login, creating a scenario where an operator was given a synchronization package for the last logged user. This was an error with part of a session cookie name being hardcoded and not being cleared when the previous user logged out, and the logic has been corrected.
SR-A91240 · Issue 259814
Corrected mobile app login load stream error
Resolved in Pega Version 7.2.2
In some circumstances, a "Failed to load stream" error was appearing when attempting to log in on the Mobile App. To fix this, the login process has been made more robust with the addition of the isSyncProcessingInProgress function to check sync progress, and a check has been added for the panel harness being set in the HCLoadManager js.
SR-A77474 · Issue 253967
Online-only Mobile harness always displays appropriate offline message
Resolved in Pega Version 7.2.2
In the Mobile app, clicking on an online-only harness (check box for online selected) from the navigation menu, then going offline and clicking it again resulted in an alert (0:Communication failure) with no other description. The issue was that in multithread context with possible switching between threads, the network status was not properly updated in desired pxRequestor page. The system will now loop through all the threads and update the pegaserveravailability status for the correct pxRequestor in the Client Cache and correctly display the message "Cannot perform this operation when offline".
SR-A78351 · Issue 255278
Improvements to mobile layout group processing logic
Resolved in Pega Version 7.2.2
The layout group processing logic for mobile has been updated to 1) remove unnecessary in-built event triggering on user interaction to improve JS processing for smooth swipe and scroll and 2) to remove tap delay on the layout group so the system listens to touchstart as well as click.
SR-A92403 · Issue 264239
CustomApp login fixed for Sales Automation Portal
Resolved in Pega Version 7.2.2
When logging in for the first time using a custom app via the Sales Automation Portal, the progress bar would flow to the end but the portal would not open and errors were logged on the console. This was traced to a logic error in the HCLoadManager getOfflineStorageCount API call, and has been fixed.
SR-A103018 · Issue 271159
Mobile Client Cache populated with pyWorkPage info
Resolved in Pega Version 7.2.2
While creating a PegaSurvey question using the simple question rule form, the product was not saving the selected response option to the "Map answer to property" property on the Answers tab of the simple question rule form. It was working online, but on a mobile device (both online and offline) it was failing to save that property to the Client Cache. This was an error with the properties of pyWorkPage defined in pyDefault with empty values not getting packaged, and the API has been updated to correct this.
SR-A99155 · Issue 253246
Mobile dirty page handling corrected
Resolved in Pega Version 7.2.2
When the "X" (Close) icon was clicked in the Mobile Create Opportunity/Lead/Contact form and then the cancel button in the prompt popup was clicked, the same page returned and the app went into infinite loading mode. This was caused by a missed use case; when the document is found to be dirty and user decides to stay on the page, the code just returned. This has been fixed.
SR-A76763 · Issue 251569
Ensured Dirty pop up appears for mobile log off
Resolved in Pega Version 7.2.2
While closing a dirty form on a mobile device, the warning popup was not shown while logging off. A check has been added to control_actions so logging out will return if dirty to resolve this.
SR- · Issue 270969
Mobile Client Cache populated with pyWorkPage info
Resolved in Pega Version 7.2.2
While creating a PegaSurvey question using the simple question rule form, the product was not saving the selected response option to the "Map answer to property" property on the Answers tab of the simple question rule form. It was working online, but on a mobile device (both online and offline) it was failing to save that property to the Client Cache. This was an error with the properties of pyWorkPage defined in pyDefault with empty values not getting packaged, and the API has been updated to correct this.