We are in the process of migrating from ServiceMax Classic for iPad to FSA for iPad. We have noted that when a work order is opened from the FSA calendar, there is a 3-8 second lag in the "actions" menu from being enabled and the work order page from loading fully. This is quite different from the Classic app. In the Classic app, when opening a work order the Actions menu and the page layout is available instantaneously. Considering that our users have been using Classic for 3+ years, this change to FSA and the lag in response will be a dissatisfier.
We had opened a case with ServiceMax and engineering indicated that this was expected behavior. I would like ServiceMax to consider getting rid of this latency so that the work order actions can be available immediately upon load. This issue will be a challenge for us from a change management perspective, as it is a step backwards from what our users have grown accustomed to.
Note: This behavior is noted in FSA 3.3.4.
What is the underlying problem do you intend to solve with this idea?
We are looking to improve the usability of the FSA so that the response time is equal to or better than the Classic app.
How is the problem being addressed today, if at all?
We will need to train to this shortcoming and hope that the other benefits from the FSA will outweigh the additional inconvenience.