I've written an application that for 99.9% of the time will be online, and so have not used any offline form functionality.However if I've a user accessing the application whilst travelling, lets say on a train, and he's using a table to access via his 4g ... what would happen if he happens to go under a long tunnel, lose 4g and then hit submit ?
I've tried to test this by creating a simple two step process model. The steps defined as follows, and are activity chained:a!localVariables( local!xxx, local!dateTime, {a!textField( value:local!xxx, saveInto:local!xxx ), a!dateTimeField( value:now(), saveInto: a!save(local!dateTime,now()) ), a!buttonArrayLayout( buttons: { a!buttonWidget( label: "Submit", style: "NORMAL", saveInto:{ a!save(ri!xxx,local!xxx), a!save(ri!dateTime,local!dateTime) }, submit:true() ) }, align: "START" )})
and the second form the same, just with readonly set to true.In my test, when I fill in the first form and then unplug my network cable hit submit i get the 3/4 progress bar. But after 5 mins i plug back in, then the form continues to stay at form1.
I was under the impression that the submit would be queued .... he's see the progress bar travel to about 3/4 full and then pause. When he then emerges from his tunnel and the 4g reconnects then the submit will continue and whatever actions would be followed ?
Discussion posts and replies are publicly visible