INC-172124 · Issue 651293
Improved Operator ID selection in Mobile Logs Retrieval section
Resolved in Pega Version 8.7
Data-Admin-Operator-ID.pzOperatorsByApplication returns only the first 500 operators, which is insufficient for large-scale use. There was a workaround of turning off paging for this report definition and setting maximum records to a bigger value, but this caused potential performance issues when opening very large users list. To resolve this, an autocomplete control will now be used to select Operator ID in the Retrieve Device Logs section of Mobile Channel. When part of an operator ID is typed into this control, the first 100 best results are shown and may be selected.
INC-173633 · Issue 650278
Google Key security updated
Resolved in Pega Version 8.7
Cross-site scripting protections have been added for Google Key.
INC-175000 · Issue 657006
Handling added for Address Map control in Microsoft Internet Explorer 11
Resolved in Pega Version 8.7
Microsoft Internet Explorer 11 does not support Class, async, await and arrowed functions due to not implementing the necessary EC6 features. This caused Address Map Control to not work in this browser because pypega_map_googlegis js creates a js class. To resolve this issue, alternate methods have been added for use with Microsoft Internet Explorer 11.
INC-175684 · Issue 658697
Parameterized data pages updated on record change
Resolved in Pega Version 8.7
Changing source data page records without changing the parameter value was not updating parametrized data pages. This has been resolved by updating the system so the parametrized data page populator function is now called every time the page is accessed.
INC-179175 · Issue 664047
Mobile barcode scan sets value with correct context
Resolved in Pega Version 8.7
After implementing a list of items where each has a unique barcode, scanning the barcodes using the mobile app worked correctly the first time but subsequent scans were setting the value on the first element of the list and missing the context of the current scan position. This has been resolved with an update to ensure the scan barcode action sets the value on the correct property when using repeating dynamic layers.
INC-180233 · Issue 660578
Offline.Rulecache UI module capacity increased
Resolved in Pega Version 8.7
Clicking the save button on a modal window caused the application to freeze and all the buttons were disabled. This was traced to the pega.offline.rulecache UI module having a default hard limit of 500 rules. Once the hard limit was reached, the system intermittently silently refused caching additional rules depending on the amount of rules packaged or the order in which the rules are loaded to the cache. To resolve this, the system has been updated to only log a console warning once the maximum threshold is reached, allowing the application to operate normally and at the time inform about the potential impact of having too many rules in memory.
INC-181126 · Issue 663307
Signature Accept callback fires correctly in offline app
Resolved in Pega Version 8.7
Clicking on the Accept button in the Pega mobile signature control was not properly calling the necessary pega.ui.signature.acceptSignatureCallback method. This has been resolved by adding code for the Post Success and Failure callback on Signature accept in the offline app.
INC-183485 · Issue 681360
Updated background refresh for off-screen worklist
Resolved in Pega Version 8.7
After update, performance impacts were seen on the field service mobile app. This was traced to Worklist refresh, and has been resolved by adding an update which will postpone the refresh when the worklist webview is in the background (not visible on the screen).
INC-183559 · Issue 664814
Handling added to process Actions chunks on multiple nodes
Resolved in Pega Version 8.7
If the synching of chunks to a node was interrupted, attempting to resume the remaining chunks resulted in a processing issue if the Load Balancer passed the connection to a different node than was used for the first connection. As an example, if chunks were synched to node "A" and the restarted sync saved the remaining chunks to node "B", when all chunks were synced node "B" incorrectly determined node "A" was actually doing the work and skipped the processing of the chunks on node "B". This resulted in queued chunks being left untouched. To resolve this, the logic has been updated to allow multiple nodes to process the chunks.
INC-183822 · Issue 667502
Filename with non-ASCII characters normalized for Apple Safari upload
Resolved in Pega Version 8.7
When using the Apple Safari browser, attaching a file name that contained Japanese characters resulted in an "attachment doesn't exist" error message when trying to open it again. This was caused by the special characters in the FileName for the Data/Query string not being encoded during the file upload, and has been resolved by updating the UploadFileToADocument activity to normalize the FileName if the Safari Browser is being used.