Saving record from an interface

Question

Hi Team, 
 We have multiple sections in the form and user will be updating them in between of time. (Interval of 5, 10, 15 minutes or an hour) 
 User want data to be saved as soon as they enter or select on the form and no save button. 
 I am thinking of off focus save like when user enters data and come out it should be saved in the record/db. Challange is what if they change the data. 
 Can you suggest any other way to handle the requirement considering performance point and no data loss.

Mike Schmitt · Answer

It's a challenging scenario, and potentially a conflict between the typical design paradigms supported by Appian, versus user expectations which can sometimes reach into the fantastical / "magic wand" type category, even if individual pieces seem reasonable. 
 One particular design occurs to me - if this is the one place you need this sort of thing, and the criticiality is high - you could potentially design a specialized "save target" database which would serve to save just a temporary copy of all fields, which is then wiped out when the form is submitted and the "real" copy of the data is written to your normal DB table(s). 
 That is, have a special table that maps (just) to this form's inputs, and creates a new row immediately anytime a user starts filling it out (after querying to see whether they have a partially completed copy, in which case that version is loaded instead). Every single field could attempt a "write to data store" after user interaction, which again for something critical, might be worth the performance hit.

Saving record from an interface

Top Replies