Welcome to the Alloy Ideas Portal đź‘‹ Here, you'll be able to browse improvement ideas raised by our community, vote on ideas you agree with or even raise your own ideas. We review all ideas raised and we endeavour to respond to all raised ideas.
Any ideas submitted will be immediately visible on the portal for others to vote on, please do not include anything in your ideas you do not wish to be shared with others.
Currently when a sync is performed you cannot do anything like complete inspection or raise a job. It would be good if we could have option of continual sync could be going on in the back ground it would keep device more up to date and reduce the chances of failed syncs etc. But we would need the device to stay operational and be able to keep working at the same time
Thanks for your feedback and votes on this. As it stands, any updates to the local mobile database (db) are prevented during a sync. A sync may remove, update and create several records - it can even restructure the db if designs have changed or update the user's permission set. This pause prevents local data corruption. However, we appreciate the use case and are investing time in future iterations of sync. Push notifications are on our wish list, along with hiding any visibility of sync to the user.
Hi, is there any update to this idea? this is an ongoing point that is raised by front line operatives
This is one of our most frequent complaints from our crews. A background sync would help us greatly.
100% agree, this and "push notifications" are the bigest gains on Mobile
I would agree with this. The only issues we have is with SYNC issues and this has often caused loss of data
We'd benefit from this too - having to have the operatives remember to sync throughout the day is disruptive, and the auto-sync blocking them from working isn't suitable. Would be better if syncing simply bundled up everything that had been done up to a certain point, synchronised that and allowed the user to crack on.
Would wholly support this development - Mayrise operated on a background sync basis - at present we have an operational workaround to avoid downtime/disruption during sync