FSA Sync Capability

The FSA has a change to the synchronisation, where as with the Classic apps the sync would queue and then automatically start immediately after the in progress sync had finished. Now with the FSA the sync doesn't queue effectively, it holds and only starts to sync when the next sync is performed. There is no logic to this, as now we find engineers saying records have been done, but whilst they have been done on the FSA they haven't been sync'd back because one sync was already underway. This means the engineer is having to re-access the app and manually start a sync to send a record back they believed was already done?

 

What is the underlying problem do you intend to solve with this idea?
Some data isn't coming back timely.
How is the problem being addressed today, if at all?
Engineers are having to wait until one sync is finished until a new sync is started.
Product Area?
FSA
What version of ServiceMax are you on?
18.3
Tags (1)
1 Comment
Product Team
Product Team
Status changed to: On The Roadmap

This will be addressed in FSA 3.5.4 scheduled for early June 2019. 

To leverage this, ensure the Aggressive sync setting SET019 is set to True / Full Sync.