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.
INC-152542 · Issue 610947
Support extended for document tags
Resolved in Pega Version 8.7
An enhancement has been added to extend the support for document tags, including showing tags added to a case in a workpool other than the application workpool; showing tags from other operators such as partner sales rep, sales reps, etc; and displaying tags in the "recently added by me" section.
INC-160485 · Issue 655297
Trailing "/" added to public links for SSO use
Resolved in Pega Version 8.7
Links generated using pyWorkLinkWithLabel were not working with SSO due to not having a trailing "/" on the URL. This has been corrected by adding code to append the "/" if the public link url doesn't end with it.
INC-161214 · Issue 640893
Push notification of shape-created child case opens correct case
Resolved in Pega Version 8.7
In a scenario with two cases, CaseA and its child case, CaseB, when CaseB was created from CaseA with a standard shape and a push notification was sent right after creation, the "Custom message" notification received on a mobile device opened CaseA instead of CaseB. If CaseB was created as a standalone case, the push notification opened it properly. This was traced to an edge case where the Primary.pzInsKey was empty because the child case was not available in database when the push notification payload was created by push shape, leading to the CaseID retrieved by getInstanceHandleFromPage to fetch the parent Case ID instead. This has been resolved by modifying the process to get the pzInsKey from the step page.
INC-161398 · Issue 639855
DataSync SynchronizationResponseStreamer logging enhancements
Resolved in Pega Version 8.7
The PegaRULES log contained "Response page does not match request, will generate failure response" errors even though no functional impact was observed. In order to enhance troubleshooting, additional DEBUG logs have been to DataSyncHandler, SynchronizationResponseStreamer is now logged on INFO level and contains more detail, and the error message has been modified to "Cannot prepare continuation response because offline package was stale. Will generate reset schedule response." to be more informative.
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.