INC-164429 · Issue 633222
Map address control works in read only view
Resolved in Pega Version 8.7
The pyTrackingMap control was not showing position when used in read-only mode. This was traced to a missed use case, and was caused by the property handle being considered in order to get the value of the current address, but in the case of read-only the property handle was empty and the address field was considered. To resolve this, in case of a read-only track map, the addressproperty value will be considered instead of the property handle.
INC-164947 · Issue 639862
Handling added for missing div when opening work object
Resolved in Pega Version 8.7
In mobile offline app, opening a work object in a specific scenario for the second time resulted in an endless busy indicator. It was not possible to navigate away, and the app had to be closed and reopened to continue. Investigation showed that some app sections had an action that tried to load a harness section where one specific div was missing, and this has been resolved by updating reloadSectionOSCOHandler to handle the missing div in the failure callback. Additionally a console.error() will appear for the missing section.
INC-165779 · Issue 641975
SQL query handling updated for mobile
Resolved in Pega Version 8.7
When the check box in mobile channel "Disclose application size when users log in for the first time" was enabled it produced the error "There was a problem getting a list: SQLState: Message: ERROR: relation "pr_data_full_sync_stats" does not exist". Investigation showed that all SQL queries passed to getDb().executeRDB(...) method were using the SQL table directly, ignoring any customizations to table mapping or database prefixes. This has been resolved by replacing the table name with a class reference ("Class: Pega-OfflineFullSyncSizeStatistics") so that table mapping can replace the reference with a proper table name and proper database prefix.
INC-166048 · Issue 659534
Navigation icons added for use in offline mobile
Resolved in Pega Version 8.7
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-167388 · Issue 651309
Values treated as strings for offline data transform concatenate
Resolved in Pega Version 8.7
When using a Data Transform to construct a URL using multiple properties that contain values with a leading or trailing "0", the "0" was trimmed when the corresponding mobile JS code was generated using pega.process.expression.getValue("pyWorkPage.PlanData.SegmentID", "pyWorkPage.PlanData") . This was traced to the offline property type assuming that any numbers-only string should be treated as a number, so the data transform concatenate was converting “0001” to 1. To resolve this, the value will be treated as a string when being evaluated in an offline data transform.
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.