Saving data in web client

[amcgilly]

The docs say that autoSave doesn't work in the web client, and you have to issue a controller.saveData explicitly for data to be saved.

A couple questions about this:

1 - does databasemanager.saveData() also work when called from the web client?

2 - I have found that data changes are being saved in the web client when I navigate away from a record I've just edited, even when I don't issue a controller.saveData. It seems like the web client behaves the way the smart client behaves with autoSave turned on and setFocusLostSaveEnabled turned off. Is this in fact the case?

P.S. I notice that setFocusLostSaveEnabled has quietly disappeared from the method editor. Is that intentional?

[grahamg]

Hi Adrian

I've also noticed that navigating away from a record in WebClient saves data in same way as Rich Client. This is a great feature for users who *might* forget to click the 'Save' button.

Have been using controller.saveData to force an immediate save when I want the GUI to reflect changes.

Regards

Graham Greensall
Worxinfo Ltd

[Harry Catharell]

Hi Adrian,

With regard to 'setFocusLostSaveEnabled', I believe that this is now deprecated in favour of databaseManager.setAutoSave() which performs the same function.

The Web Client will still honour transactions and so you can control save/revert operations using that technique.

The servoy_sample_crm solution demonstrates this if it is an option for you

Cheers
Harry

[Westy]

Hi Adrian

I've also noticed that navigating away from a record in WebClient saves data in same way as Rich Client. This is a great feature for users who *might* forget to click the 'Save' button.

Have been using controller.saveData to force an immediate save when I want the GUI to reflect changes.

Regards

Graham Greensall
Worxinfo Ltd

If the user unexpectly exits WebClient the data may not be saved. For this reason we have added an "Exit" button with a controller.saveData to our WebClient solution.

Dean