INC-167794 · Issue 645035
Offline ExpressionEvaluator documentation updated
Resolved in Pega Version 8.7
When working offline, issues may been seen due to the == operator in JavaScript returning true if any 'false' value, e.g. "0", empty string, or "false" is used for comparison, leading to the expression false == "" to return as true. While a solution is in process, the documentation for the Offline ExpressionEvaluator has been updated to reflect this use case may create unexpected behavior in an offline data transform, and outlines the workaround of not using words like "Yes", "No", "false", "true" or 1 0 values.
INC-168290 · Issue 663428
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-168935 · Issue 645394
CalendarGadget updated to display events in Saudi locale
Resolved in Pega Version 8.7
When using the pxCalendar section with the locale setting ar_SA, the calendar was correctly converted to a Saudi calendar but the events which were showing in the English version of the calendar were not showing up in in the Saudi Calendar. This was caused by the CalendarGadget page not populating properly due to the localized Hijri calendar failing a datetime check that was looking for a Gregorian calendar with time in GMT format, and has been resolved by updating the when rule "pzShouldDisplayEvent " to use the proper function for the localized calendar.
INC-171951 · Issue 667124
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-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.