In the iPhone Summer 16 app, if there is a sync conflict, there is no clear notification to the user that this has occured unless you go and look for it.
The iPhone app should be updated to work in the same way the iPad app does:
Examples on the iPad:
Great suggestion Adam. We are definitely looking at how we can handle and notify users in the event of sync conflict/failure/error.
For one thing, the upcoming phone app will support background sync so that even if the user is not using the servicemax app the sync will still run according to schedule/configuration. We will also have local notification so that when there is sync error and the servicemax mobile app is not in the foreground we will notify the user with a notification alert (banner or alert box depending on your notification setting).
We have not finalized the UI but in the event of sync error, we will be sure to have a clear (perhaps similar to what we have for iPad Classic) visual indicator that conflict/error has occurred on the app. Badge in the tap bar or somewhere in the navigation seem like a logical choice.
Hi Joseph, thanks for the feedback, but I'm assuming this will all be for the FSA Phone app?
What you are suggesting does sound great, especially the background sync and notifications of errors, but are there any plans to upgrade iPhone Classic to have parity with iPad Classic?
A simple upgrade to iPhone Classic like I have suggested in the idea would massively help our field techs work with sync conflicts. We are currently in the process of deploying the iPhone Classic app to approx 600 techs and constantly get feedback that sync conflicts are not easy to detect which causes problems because the techs don't resolve them straight away, then nothing else syncs until they realise and resolve/remove them. We are having to tell the techs to look for the spinny wheel in the tool bar after every save and if it doesn't appear then chances are you have a conflict so go and check for one. This really isn't intuitive for a field tech, consumes a lot of time and results in confusion. Just bringing the iPhone Classic app into parity with how the iPad handles it for now would be a great step forward until FSA arrives and we are able to deploy it.
Thanks and I think this is an important update. Not being able to see when a sync conflict occurred is a big issue and we will address it in iPhone Classic. We are however currently working on "multi-server compatibility" for our classic apps including the iPhone app, so the enhancement to display sync conflict or sync error will be added once the multi-server compatibility work has been completed. For timing, this means that the enhancement will be available approximately with the Winter release (Jan 18) or shortly after the Winter release date.
Great news, thanks for the update! FYI Rob van Waveren Tom Greco
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.