SR-123581 · Issue 188015
Scrolling corrected for Safari on mobile devices
Resolved in Pega Version 7.1.8
When using the global search on a tablet or mobile device, the results are displayed in a modal pop up in the browser. However, scrolling was not working when using Safari on a mobile device. To correct this, the Search Panel CSS and js were modified to enable scroll support on mobile devices.
SR-125913 · Issue 192447
Fixed file attachments in Mobile
Resolved in Pega Version 7.1.8
When using the AttachContent Control functionality in mobile, attaching a file popped up a window with the message 'File attached successfully', but no Action Sets associated with file attachments were actually run. Using the same functionality on desktop did not have any issues. This problem was traced to an error in the JavaScript code for the mobile control relating to the access group, and has been corrected.
SR-A18905 · Issue 233955
OrgName error resolved for MobileOffline:Obj-Open-By-Handle
Resolved in Pega Version 7.2.1
If Obj-Open-By-Handle was configured on the Org Name link in MobileOffline for the master details of a Contact Work Object, clicking on the link generated an "Empty Work Item Handle" error despite the OrganizationID(Handle) being present on the data page. This was an error in the actions array for the "runScript" API, and has been fixed.
SR-A21298 · Issue 239141
NPE on mobile list open resolved
Resolved in Pega Version 7.2.1
A null pointer exception was being generated on mobile device when opening list items. A null check has been added to pega_ui_modaldialog to resolve this exception.
SR-A21636 · Issue 240162
Fixed auto-complete use in iPhone Opportunity creation
Resolved in Pega Version 7.2.1
Issues were seen when selecting items using Auto-Complete on an iPhone while creating an Opportunity. This was due to a positioning error in the logic, and has been fixed.
SR-A24787 · Issue 247535
SA mobile app hang fixed
Resolved in Pega Version 7.2.1
Hitting the 'back' button in the SA mobile app before a work-object fully loaded the master-details caused the app to hang. This was traced to an issue with the thread switching that caused a JS exception, and has been resolved.
SR-A24787 · Issue 245849
SA mobile app hang fixed
Resolved in Pega Version 7.2.1
Hitting the 'back' button in the SA mobile app before a work-object fully loaded the master-details caused the app to hang. This was traced to an issue with the thread switching that caused a JS exception, and has been resolved.
INC-101011 · Issue 556725
Pulse mentions correctly tagged in Google Chrome
Resolved in Pega Version 8.4.2
Pulse mentions of spaces or users were not getting tagged correctly. This issue was due to recent changes in the way touch events are handled in Google Chrome: the latest upgrade removed the ontouchstart property in the window, causing the isTouchable capability identification method to fail. As part of the work done to resolve this, it was discovered that the initAutocomplete function in the pzJquerymentionsInput .js was failing to delegate the mousedown event. This has been corrected by delegating touchstart and mousedown while initializing if screen isTouchable.
INC-119803 · Issue 561686
Placeholder text added for question dropdown sourced by a datapage
Resolved in Pega Version 8.4.2
In a flow action with question pages where each question page was configured with a set of question rules, one question which displayed a country list in a dropdown sourced from a datapage always displayed the first value by default in the dropdown instead of place holder text (like Select..). In addition, the default selection value of the dropdown was not saving to the clipboard on submission of the flow action, causing it to appear in the UI like the first value had been selected even though nothing was saved on the clipboard. These issues have been resolved by adding place holder text in pzSetQuestionStreamSimpleDynamicSelect for a dropdown with a datapage source
INC-120326 · Issue 564438
Landing page refresh modified to avoid frequent reloads
Resolved in Pega Version 8.4.2
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.