Skip to main content

Hi All, one of the mobile user has reported below MWO error mentioning that the document upload is waiting, and this error has been there for more than one day. And we tried to check if there are any Failed Transactions and there were no records for the subject user to clear.

We tried to expedite the process by connecting Wi-Fi and using Mobile data but it didn't change the status of the error and it's still in ‘Idle’ condition.

We are using IFS MWO Service 10 (UPD 9) and this error has been reported intermittently, 
 

Would you kindly advise,
1. what could we do to have this 336-document uploaded into IEE and
2. Kindly advise if we use initialization can lead to a data loss? Or what could happen if the user use ‘Force Initialization’ option?
 

Many thanks for your kind thoughts and advice. 

 

Can you see any details in the device logs that could explain what is happening?

If you initialize you will lose the document upload transactions.

Cheers

James

Hello @James Ashmore thanks for your kind attention. Exactly and when investigate through device logs the same Work Assignment has been ‘Accepted’ by 02 persons, while they were in ‘Offline’ mode and one user has cancelled the Work Assignment and the cancellation has synced to IEE end but the intended User (above device owner) when reporting in the Assignment, it is not in the backend. And we have got a Failed Transaction for the above user saying that the ‘Work Assignment has been removed by another user’

With this kind of situations would you kindly assist with clarifying below?


1. Will Force initialization only make reset the MWO App and impact(lost) pending document upload transactions or Only Initialization will do the most impact for the data loss?

2. In IFS MWO upgraded versions is there any way to prevent double acceptance of Pool Work Tasks?


3.In IFS MWO upgraded versions, is there are option to facilitate Offline ‘Acceptance’ and carryout the Work, after downloading the Pool work into the Mobile device?

Thanks again for your kind thoughts and advice.

 

Force Initialize will delete the pending transactions and reset the device.

In IFS Cloud there is an option to force the Acceptance of Pool Work Orders only when the device is online (connected to backend). This will prevent your scenario from happening.

Cheers

James

Hi @James Ashmore Thanks for the clarification on Force Initialization impact on MWO pending transactions. Great to hear that IFS cloud version is having the capability to force the Acceptance of Pool Work Orders only when the device is Online. Thanks again for your kind thoughts and advice.

Reply


Terms & ConditionsCookie settings