Workaround And Enhancement For More Consistent Fetch Of Mobile Deployments In MWM v2.3
(Doc ID 2482774.1)
Last updated on MARCH 31, 2020
Applies to:Oracle Utilities Mobile Workforce Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 2.3]
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Mobile Application
Customer cutover to MWM v22.214.171.124 over the week along with deploying a number of custom packages. During the cutover, and re-deploying the approach packages, M1-BMCOM and M1-DPLOY were run and completed/activated successfully.
On the MCP side, the Crews inconsistently received the prompt to "fetch" the latest app bundle when starting their Shifts.
This is resulting in certain functionality working for some crews with the current mobile deployment, but not others who still had the older deployment. Since the batch run does not provide much/any information about the appbundle.
Why are Crews seeing different results or receiving the updated bundle inconsistently?
Is there a way to force the app bundle refresh on the MCP to ensure crews have the latest?
When should a Field Worker get the "FETCH" command?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!