SR-D73237 · Issue 539124
Pagination updated to resolve repeating Pulse notes
Resolved in Pega Version 8.3.3
After adding a case and entering 15 Pulse notes, scrolling down resulted in the notes being duplicated. Investigation traced this to entering more than 10 posts in a single interaction on a previously empty case when "Progressive pagination" was enabled for the repeating dynamic layout. On Private Edit, if the pagination was changed to "NONE" then the issue was resolved. Pagination depends on the pzPagingStartDateTime property, which is set on D_pzFeedParams, but since there were no results in this scenario this property was not being set. To resolve this, an update has been made so that pzPagingStartDateTime will be set if it is empty.
SR-D76620 · Issue 544576
Resolved touch events issue with updated Google Chrome
Resolved in Pega Version 8.3.3
After upgrading Google Chrome, touch events on a flow action under the Action Button in a case or on the application under "Launch web interface" were not reacting and the flow actions were not accessed. Investigation showed that Google Chrome's latest upgrade (79.0.3945.130) removed the ontouchstart property in the window, causing the isTouchable capability identification method to fail. This has been resolved by adding a check for navigator.maxTouchPoints to identify for Google Chrome whether the device involved has a touchscreen.
SR-D85551 · Issue 548075
Resolved touch events issue with updated Google Chrome
Resolved in Pega Version 8.3.3
After upgrading Google Chrome, touch events on a flow action under the Action Button in a case or on the application under "Launch web interface" were not reacting and the flow actions were not accessed. Investigation showed that Google Chrome's latest upgrade (79.0.3945.130) removed the ontouchstart property in the window, causing the isTouchable capability identification method to fail. This has been resolved by adding a check for navigator.maxTouchPoints to identify for Google Chrome whether the device involved has a touchscreen.
SR-D82882 · Issue 544165
Special characters excluded in the create tag activity
Resolved in Pega Version 8.3.3
The system was allowing the creation of a tag with special characters at the case level from the Actions tab. This was traced to the pxCreateTag activity 3rd step, which passed the current page parameter without invoking the pyValidateTagName activity. This has been corrected by updating the logic.
INC-134618 · Issue 582776
Corrected logic for deep pagelists on mobile
Resolved in Pega Version 8.5.1
After completing a workorder in the mobile app, the synchronization failed intermittently with the error "fail: pyWorkPage - Validation failed: Errors Detected. Finish Assignment action failed as pyWorkPage has messages: Validation failed: Errors Detected. ... The page contains an undefined property: .pxUniqueElementID". This was traced to incorrect logic for handling deep pagelists, and has been resolved.
INC-131961 · Issue 571700
Mobile app correctly determines online status after sleep
Resolved in Pega Version 8.5.1
After not using the mobile device for some hours, the app was not recognizing that the device had become online again and continued to show the red 'offline' bar. Restoring network connectivity required logging off and relogging into the network. This was traced to a bug in Android webview which causes window.navigator.onLine to return as false after wakeup despite the connection being present. To resolve this, version 8.5.103 of PIMC (Pega Infinity Mobile Client) contains new native mechanisms which are exposed to the webview as plugins and that work completely independent of webview.
INC-130727 · Issue 573340
Resolved mobile app java.lang.OutOfMemoryError
Resolved in Pega Version 8.5.1
After working with the mobile app for a period, logging in failed and the app crashed with java.lang.OutOfMemoryError exceptions. This was traced to each sync adding a new version of allow-list datapages to the client store which were not cleared, and has been resolved.
INC-135159 · Issue 580675
Logic updated for deepMergeObj API
Resolved in Pega Version 8.5.1
Issues with the embedded page values being removed when navigating from a flow action and inconsistent localization of labels and captions in a mobile app were traced to the deepMergeObj API; the logic for the API has been revised to ensure the pxObjClass property is not removed from embedded pages during the doSave function.
INC-131991 · Issue 583041
Logic updated for deepMergeObj API
Resolved in Pega Version 8.5.1
Issues with the embedded page values being removed when navigating from a flow action and inconsistent localization of labels and captions in a mobile app were traced to the deepMergeObj API; the logic for the API has been revised to ensure the pxObjClass property is not removed from embedded pages during the doSave function.
INC-137352 · Issue 583664
Mobile app improvements for poor connectivity conditions
Resolved in Pega Version 8.5.1
When the mobile app was used in areas with poor data network connectivity, the screen was freezing or a number of sync errors were seen. Improvements have been made in the processing and wait conditions to smooth the functions when connectivity is intermittent.