SR-C9536 · Issue 354488
Check added to ensure fresh app data for delta sync
Resolved in Pega Version 8.1
When the application data was updated on the web (server side), the changes were not reflected on the phone app (client side). When an application login and delta sync were performed on the mobile device, the changes made on the server side still did not show up. The changes made to the web application did show up if the mobile cache was cleared and a new login was started. This issue was traced to an implementation error where an editable data page once loaded on clipboard was always packaged as-is even when things had changed in the DB. To correct this, a check has been added to remove the stale datapage and fetch a fresh version when doing datapage packaging in pzDataSyncPackager.
SR-C973 · Issue 349954
Move report shortcut shows consistent categories
Resolved in Pega Version 8.1
When opening a Report in the Case Manager Portal, the Analyze Performance category is first in the out of the box implementation. However, when attempting to move one report from a different category, the Analyze Performance category was not shown in drop-down This was caused by different field values being used to display the category label in the browser and category dropdown, which led to them being localized differently in the display on the right ( "Analyze Performance") and the dropdown ("Performance analysis"). To correct this, the field values have been updated to make them consistently localized.
SR-C9791 · Issue 350823
Code added to ensure unique IDs for control elements
Resolved in Pega Version 8.1
In order to improve accessibility, code has been added to ensure unique IDs are generated for Radio buttons, checkboxes, and other controls. This also resolves an issue where the duplicate labels caused a click to fire on an unexpected harness element.
SR-C9804 · Issue 350937
ResultCount methods updated to handle null results
Resolved in Pega Version 8.1
Autocomplete controls were not working via mobile app. This was due to the Autocomplete control not rendering a list supplied by a data page, and was traced to the results of the datapage var resultCount = res.responseText.get("pxResultCount");being returned as null. In order to ensure the correct results, an alternate way of getting the pxResultCount has been added.
SR-C9824 · Issue 355932
Behavior change for error handling when using "Call superclass data transform"
Resolved in Pega Version 8.1
Previously, when "Call superclass data transform" was enabled for data transfers, the initial data transform would continue working even if the subsequent transforms it called failed. As an example, given data transform A, which called another data transform B, which called another data transform C, and data transform A performed some actions after calling data transform B; If an error occurred while processing data transform C, data transform C ended processing, data transform B also ended processing, but data transform A continued working. This was confusing behavior. To create a more consistent environment, whether or not “call superclass data transform” is used, when any of the chained data transforms fail the entire process will exit. The documentation has also been updated to indicate this new behavior.
SR-C9887 · Issue 354825
Reports list properly updated when switching applications
Resolved in Pega Version 8.1
When switching applications, some of the report browser was displaying information from the first application. This was due to incomplete clearing of the data, and has been fixed by calling pzRBSetFilters in Data-Report-Browser!pzRBForceDataPageRefresh to reset the report browser when it is opened.