INC-180233 · Issue 660580
Offline.Rulecache UI module capacity increased
Resolved in Pega Version 8.5.5
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-183559 · Issue 664812
Handling added to process Actions chunks on multiple nodes
Resolved in Pega Version 8.5.5
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-183864 · Issue 666185
Updated RequestorInitialize to improve performance
Resolved in Pega Version 8.5.5
After updating, initial user logins were taking an excessive amount of time. This was traced to the standard rule "RequestorInitialize", and has been resolved by updating the implementation.
INC-169636 · Issue 659533
Navigation icons added for use in offline mobile
Resolved in Pega Version 8.5.5
When using an offline mobile app, clicking on an image / link on the home page for navigation resulted in the error “Resource missing. See client logs.” This was traced to a missed use case that resulted in some icons not being available in the package, and has been corrected by including the following:webwb/py-menu-toggle.png webwb/pzgrid_downarrow.png webwb/pymenuleftarrow.png webwb/pymenurightarrow.png webwb/pymodal_mask_img.png webwb/py-grid-sort-down.svg
INC-194932 · Issue 686277
Handling updated for offlineWorkIDs map
Resolved in Pega Version 8.8
Intermittent failures were seen when deleting attachments on Mobile. These were traced to pega.ui.DCUtils being undefined, and has been resolved by populating the offlineWorkIDs map for attachment-related actions.
INC-183485 · Issue 699787
ClientCache performance optimization
Resolved in Pega Version 8.8
In order to improve performance for the mobile app, updates have been made to optimize the ClientCache list interations.
INC-190053 · Issue 680232
Mobile attachment count corrected
Resolved in Pega Version 8.8
Parametrized data pages were not being populated as expected, causing an incorrect attachment count when opening a case in Mobile. This has been corrected.
INC-192649 · Issue 706132
Basereference context available for attach content control
Resolved in Pega Version 8.8
An "undefined" error occurred when attaching a file using the attach content control in the mobile harness. To resolve this, support has been added to run attachcontent in basereference context. This can be enabled by setting pega.attachToCtxPage to true.
INC-198193 · Issue 723626
Error correctly shows for each attempt to upload an oversize file
Resolved in Pega Version 8.8
The error message indicating an uploaded file exceeded the permitted file size was only shown on the first try on Android. Subsequent attempts to upload the same oversize file did not generate any error. This was due to a persisting value, and has been resolved by explicitly clearing the input value for the mobile browser upload.
INC-198249 · Issue 705091
Security updates for packaging mobile app
Resolved in Pega Version 8.8
Unsafe properties such as password and userId are now explicitly filtered from the Operator object during the mobile app packaging process.