INC-144311 · Issue 601109
Updates for nested "Append And Map To"
Resolved in Pega Version 8.3.5
Nested actions "Append And Map To" in Data Transforms were producing incorrect results when offline. This was traced to all operations being performed on the Page List which was on first level of nesting, which was caused by changing the Data Transform into JavaScript form for offline use. The JavaScript form of DataTransform uses variable the "targetListObj" to represent the Page List, and this same name was reused regardless of the "Append And Map To" nesting. An additional problem was seen with the "Update Page" Data Transform action when used with conjunction with a nested "Append And Map To" action: the action assumes that top level Pages exists, but "Update Page" did not create them. This caused the "Append And Map To" action to fail. To resolve this, the "Append And Map To" action will use suffixed variable names to reference nested PageLists, and "Update Page" will create the Page if it doesn't exist.
INC-144566 · Issue 600857
User lookup list correctly populated when using # tag
Resolved in Pega Version 8.3.5
When typing '#ANewTag @' in Pulse, the user lookup list was not shown. Using '#ExistingTag @' worked as expected. This was a missed use case in work done to improve the performance of pzJquerymentionsInput by restricting REST calls, and has been resolved.
SR-A76763 · Issue 252485
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-A89212 · Issue 257059
WKWebview updated
Resolved in Pega Version 7.2.2
A partially successful workaround was inserted into the previous version to fix an issue with Apple's WKWebview where an iframe on a case screen was preventing the native Sidebar from working. However, some JavaScript confirm functions with property type Data continued to generate occasional errors. WKWebview has now been updated to resolve the issues, the workaround has been removed, and all confirm functions should be working as expected.
SR-A89212 · Issue 257378
WKWebview updated
Resolved in Pega Version 7.2.2
A partially successful workaround was inserted into the previous version to fix an issue with Apple's WKWebview where an iframe on a case screen was preventing the native Sidebar from working. However, some JavaScript confirm functions with property type Data continued to generate occasional errors. WKWebview has now been updated to resolve the issues, the workaround has been removed, and all confirm functions should be working as expected.
SR-A90165 · Issue 258244
WKWebview updated
Resolved in Pega Version 7.2.2
A partially successful workaround was inserted into the previous version to fix an issue with Apple's WKWebview where an iframe on a case screen was preventing the native Sidebar from working. However, some JavaScript confirm functions with property type Data continued to generate occasional errors. WKWebview has now been updated to resolve the issues, the workaround has been removed, and all confirm functions should be working as expected.
SR-A80668 · Issue 256820
DateTime Accessibility improved for iOS
Resolved in Pega Version 7.2.2
Accessibility has been improved for the DateTime control in iOS, allowing Input, Calendar image, Show Previous Month, Show Previous Year, Show Next Month, and Show Next Year buttons to be read out correctly.
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.