The ability to view and resolve a sync conflict in Go compared to the old Classic app is vastly improved.
However, the options which are presented to the user are not as clear and concise as they could be.
Classic and Go are compared side by side below:
The options in Classic are clear and self-explanatory.
But in Go, the "Keep server's changes" option can be hard to understand.
In our example above, the sync has failed because it has hit a Salesforce validation rule. There haven't actually been any changes on the server but instead its just hit this rule (also, a user might not know what the "server" is...). However this is the option we have to chose to resolve the conflict to revert back to the previous state of the data and therefore be able to try a again with a new sync.
In Go, we think it would be better if the "Keep server's changes" option was renamed to something like "Discard my changes" to make it clear for the user on what action to take.
What is the underlying problem do you intend to solve with this idea?
Make sync conflicts clearer and easier to resolve
How is the problem being addressed today, if at all?
N/a
Product Area?
Mobile Apps, ServiceMax Go
What version of ServiceMax are you on?
20.1
4 Comments
