SR-B7965 · Issue 291732
Resolved mobile case switching exception
Resolved in Pega Version 7.3
The console error 'Exception while trying to set work item as completed in assignment list' was seen while context switching a case in a custom mobile app. This was caused by the configuration calling submit during preprocessing, and has been fixed by ensuring the onSuccess callback of finishAssignmentAction is called when there is no next Task.
SR-B9286 · Issue 278610
Enhancement to get work items from multiple workpools for mobile user
Resolved in Pega Version 7.3
An enhancement has been added to support multiple workpools belonging to same application for mobile users. The code will iterate through all workpools which are offline enabled for the operator and get the work items in pzDataSyncGetWorkList activity.
SR-B9286 · Issue 287888
Enhancement to get work items from multiple workpools for mobile user
Resolved in Pega Version 7.3
An enhancement has been added to support multiple workpools belonging to same application for mobile users. The code will iterate through all workpools which are offline enabled for the operator and get the work items in pzDataSyncGetWorkList activity.
SR-B9718 · Issue 286254
Corrected picking for mobile circumstanced harness
Resolved in Pega Version 7.3
On mobile devices the circumstanced version of tablet was getting picked instead of the mobile device. The invoke addSectionForOfflinePackaging_X method has been updated to resolve this.
SR-B71423 · Issue 319981
Localization added to pyAccountSettings field labels
Resolved in Pega Version 7.4
Field label localization for the pyAccountSettings section rule has been added to the Pega-IntegrationArchitect ruleset.
SR-B73542 · Issue 327654
JNDI Server field in Connect-JMS supports GRS
Resolved in Pega Version 7.4
Setting the value of the JNDI Server field in the Connect_JMS rule form using Global Resource Setting was only working when the JNDI Server rule instance was specified directly. In addition, attempting to use a GRS to set the value in the JNDI Server field itself resulted in the error "Could not find JNDI Server instance: =D_PegJMS.PegJNDIProp". This was due to the JNDIServerPage receiving the value of JNDIServerName but not being able to use it. To correct this, a local variable actualJNDIServerName has been added to carry the information and make it available to the API.
SR-B74017 · Issue 329731
MimeType set on attachments
Resolved in Pega Version 7.4
In order to correct a problem for mobile users attaching files, pyAttachMimeType will now be set on the pyNewFileAttachment page for both online cases and offline cases.
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.