Reusing MDT Tags For Crew Devices In Workaround For 'Runtime settings not found in MDT file'
Last updated on MARCH 20, 2017
Applies to:Oracle Utilities Mobile Workforce Management - Version 184.108.40.206 and later
Information in this document applies to any platform.
On : 220.127.116.11 version, Mobile Application
Creating MDT tags for crew devices
Crews report that they cannot log onto MWM on their device. The get the message 'Runtime settings not found in MDT file'.
User usually do one of the following things to fix:
1. Delete the MDT file and when you click on MWM App the MDT file recreates
2. Reinstall the MWMAPP to get the crew working again
3. Edit the MDT file to get the MWMAPp working again
In scenarios 2 and 3, user having to recreate the MDT TAG for the device. The reason have to recreate the MDT TAG is because got the error on the device 'MDT Registration already exists.'
So for example, if if have TAG HH09999, user forced to create a new MDT TAG HH09999-1 - so the crew can continue using the same device.
User would like stop recreating the MDT TAG. So when a crew reports they get the message 'Runtime settings cannot be found in MDT file', want to fix the MDT file by using steps 2 and 3 above BUT WITHOUT creating the new MDT TAG.
What change to make so when MWM checks the MDT TAG, it is still able to use the original one - so HH09999 ?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms