@SHAUN_KERSLAKE the short answer is that no, it’s not possible to hide it via Page Designer or any other configuration options.
What prompts your engineers to trigger initialize?
Best regards,
Rukmal
@Rukmal Fernando There are many issues with IFS MWO Service currently, and we have lots of support cases open. Unfortunately if an engineer comes across an issue such as not receiving work to their device, they re-initialize and this has been seen to resolve the issue sometimes. So it is a behavioural issue with the users that we were hoping to control.
We have stressed multiple times to not initialize unless stated to do so, but this has been ignored and we can see engineers initializing on a daily basis.
Hi
This is a Mobile framework functionality and it is not possible to hide or turn it off.
I agree that the user should not use that button if not really required.
In reality we have two buttons, but the second is not shown before you have hit the initialize button.
- The Initialize button will first send any unsent transactions to backend, before loading the metadata again. So you should not loose any unsent work
- When you have hit the Initialize button, you can go to the three dots and there you will see a Force Initialize. That one will just remove everything in the local database and do not even try and send any unsent transactions. This is like a last resort if the initialize doesn’t work. This one an enduser should not use.
@JOOLSE and @Rukmal Fernando Thanks both for your responses.
It’s good to understand the difference between the two initialize buttons and I have passed this onto the business to make them aware.
Shame we can’t hide the button but I guess we will persist in trying to communicate and educate our engineers.
@JOOLSE One quick thing that has been brought to my attention.
The IFS Documentation doesn’t quite align with that you described above and contradicts a little:
Troubleshooting Mobile Apps Introduction - Technical Documentation For IFS Cloud
Seems to suggest that Initialize will delete any failed transactions, and if you look at the documentation for this it states:
“Deleting transactions could result in a mismatch between the data in IFS Cloud and the mobile app. The delete option should therefore be used with caution and steps should be taken after deleting a transaction to ensure the data in IFS Cloud and the mobile apps are aligned. Either by changing the data in IFS Cloud to match the mobile app or instructing the mobile app user to perform an Initialization which will reset the mobile app data so that it once again matches IFS Cloud.”
Failed Transactions - Technical Documentation For IFS Cloud
From what you said no work is lost when initializing but deleting failed transactions will cause a mismatch of data….
What are your thoughts on this?
Hi
What you see in the documentation is correct. If there is a failed transaction it will be deleted and the end user needs to re work the job. So yes you are correct that we can phase a data loss.
Regards
Johan
