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-A8445 · Issue 220085
Ensured display of empty user worklist section in hybrid client
Resolved in Pega Version 7.2
The user worklist section was not being displayed in the hybrid client if the login had no assignments (the WL(D_pyUserWorkList pxresultcount is zero) and the crewleaderworklist harness had a repeating dynamic layout. This has been corrected.
SR-A8217 · Issue 223611
Added server retry for push notifications in Sales Automation 7.14 / SFADevelopment for Android
Resolved in Pega Version 7.2
Push Notifications were not working on Sales Automation 7.14 / SFADevelopment for Android. This was traced to an error returned by the GCM server during registration, and the code has been modified to re-try the registration process if a failure is encountered.
SR-A12537 · Issue 224733
Optimistic locking honors OfflineEnabled function
Resolved in Pega Version 7.2
After upgrade, if a top level case type rule was checked out through the Case Explorer by opening the Case Designer and then changing the locking mode to Optimistic, the value reset back to Default after check-in. This was an issue with the pyOfflineEnabled setting being honored, and has been corrected.
SR-A9893 · Issue 220141
Checkbox values retained in Hybrid client on iOS
Resolved in Pega Version 7.2
Checkbox property values were not retained in Hybrid client on iOS inside a repeating dynamic layout, displaying the checkboxes as unchecked even when the property associated with the checkbox had value = true. This was not an issue when running the application on a desktop or in a regular mobile browser. This was traced to the ID attribute value of all the checkboxes being rendered as the same in this circumstance, and the system has been updated to generate unique ID attributes if bOptimized is true in the pzGenerateCheckbox RUF.
SR-125113 · Issue 193442
Localized labels displaying in Safari
Resolved in Pega Version 7.2
Localized headers were not displaying properly on Safari browsers if the Fat List mode was used for the grid headers. Rendering worked as expected using Field Value mode. This was an issue with localized labels not rendering properly when the width of the Safari browser is reduced, and has been fixed. In addition, an issue with the header values being added dynamically instead of using constant values for a mobile browser grid using responsive mode has also been fixed.
SR-125113 · Issue 216785
Localized labels displaying in Safari
Resolved in Pega Version 7.2
Localized headers were not displaying properly on Safari browsers if the Fat List mode was used for the grid headers. Rendering worked as expected using Field Value mode. This was an issue with localized labels not rendering properly when the width of the Safari browser is reduced, and has been fixed. In addition, an issue with the header values being added dynamically instead of using constant values for a mobile browser grid using responsive mode has also been fixed.
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