cancel
Showing results for 
Search instead for 
Did you mean: 

Manual delta sync required for Background sending

0 Kudos
79

Hi All,

The ideal behaviour of an Agentry application is to allow background sending after the initial sync is done.

But the application that we use forces us to do a delta sync after the initial sync, for the background sending to be enabled.

Without doing a delta sync, the background sending does not get enabled and hence the data is not posted to the backend

The transmit configurations (Angel and AngelLite) in Agentry, have the "'Stay Logged into Server" checked.

Please share your thoughts on this

Thanks,

Pooja

View Entire Topic
bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Pooja,

The reason for that is when you do the initial sync your client does not have any definitions yet.  It doesn't know about the two transmit configurations.  The initial sync will download all the definitions and run your main fetches.   Once that completes, from that point forward the client will have knowledge of what transmit configuration you are using.  So by performing the delta sync after the initial sync it then utilizes one of the transmit configurations and can stay connected.  I hope that helps explain why the second sync is needed to get into a stay connected session.

--Bill

Former Member
0 Kudos

There is an option at the Module screen in the editor called "Successful Login Action "  You can put a transmit action here.  This way when the user logs into the device a transmit will happen that the enable the stay connected to server.

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Just to note, I don't believe the successful login action has been implemented in all of the clients yet so be sure to test first.

--Bill