SR-B76463 · Issue 340030
Refresh from ruleform correctly passes mandatory parameter
Resolved in Pega Version 7.4
The below error message appeared on the clipboard when going to Action tab and clicking on Refresh button: "Unable to load data page D_ServiceMethods. Required parameters : ServiceType. cannot be blank". This warning message was also visible in the logs whenever the service was called from any SOAP client. In this case, triggering a refresh from Ruleform action was not passing a mandatory parameter to the D_ServiceMethods data page. To fix this, the section Grid has been modified to verify the parameter (i.e. pyServiceType) and then display it.
SR-B78159 · Issue 338941
Mobile dashboard widget name value displays correctly
Resolved in Pega Version 7.4
A problem was seen where the dashboard widget name tag was not resolved on the first visit to the dashboard, but after navigating to the second screen on a mobile device and then returning to the dashboard, the correct value appeared. This was traced to a missing use case for a header using JSP format, and has been corrected.
SR-B78159 · Issue 338952
Mobile dashboard widget name value displays correctly
Resolved in Pega Version 7.4
A problem was seen where the dashboard widget name tag was not resolved on the first visit to the dashboard, but after navigating to the second screen on a mobile device and then returning to the dashboard, the correct value appeared. This was traced to a missing use case for a header using JSP format, and has been corrected.
SR-B78996 · Issue 330406
Proxy Support added for "Mobile App Build" Mechanism
Resolved in Pega Version 7.4
The Mobile Application 'Build' mechanism was not picking up on the JVM Proxy Settings (-Dhttps.proxyHost, -Dhtps.proxyPort, -Dhttps.proxySet). This has been added.
SR-B82481 · Issue 333250
added safecheck to sectionRefreshCallback
Resolved in Pega Version 7.4
When doing a refresh of a section in the PSI app, the Hybrid client in function sectionRefreshCallback in pzpega_ui_ajaxengine.js was causing a crash. This was due to a missing safe check which has now been added.
SR-B82678 · Issue 338616
Optimistic packaging updated to handle missing pxflows
Resolved in Pega Version 7.4
Opening a Work object on a Mobile device generated the error "The reference.pxFlow() is not valid. Reason: unexpected character ')' at position 8, expected subscript (wildcards not allowed)". This was traced to missing pxFlows due to the customized way the case was created, and handling has been added to clear the error messages in pyWorkPage while packaging for optimized cases.
SR-B82678 · Issue 338451
Optimistic packaging updated to handle missing pxflow errors
Resolved in Pega Version 7.4
Opening a Work object on a Mobile device generated the error "The reference.pxFlow() is not valid. Reason: unexpected character ')' at position 8, expected subscript (wildcards not allowed)". This was traced to missing pxFlows due to the customized way the case was created, and handling has been added to clear the error messages in pyWorkPage while packaging for optimized cases.
SR-B84336 · Issue 332037
onOnlineDetected use matches documentation
Resolved in Pega Version 7.4
iOS11 was failing the first login attempt. Documentation for the addListener method in pzPega_offline_datasync rule lists 'onOnlineDetected' as optional, but when the listener was added without onOnlineDetected the console.error occurred. This was originally a documentation error where the rule was incorrectly given as optional even though the event handlers always assumed onOnlineDetected was defined, but as there are reasons to support this use the system has been updated this so onOnlineDetected is truly optional now.
SR-B87422 · Issue 337249
Mobile sync fixed for case data
Resolved in Pega Version 7.4
When a case was updated, the Pega iOSMobile application failed to sync the case data and became stuck due to read-only Data Pages being included in the action data. To ensure the update can be saved properly, code has been added to mergeWorkAndForm which will remove data pages before returning the action data.
SR-B87422 · Issue 337228
Mobile sync fixed for case data
Resolved in Pega Version 7.4
When a case was updated, the Pega iOSMobile application failed to sync the case data and became stuck due to read-only Data Pages being included in the action data. To ensure the update can be saved properly, code has been added to mergeWorkAndForm which will remove data pages before returning the action data.