- Antonio OoiAsked on January 30, 2014 at 07:39 PM
For my case, I lost my LATEST WORK more often than losing my older work. As long as you don't take my older work and overwrite my latest work (which could be due to bad auto-save mechanism), I will be fine. You support staff even asked me not to open JotForm more than 1 browser; as such, I wonder how you guys going to handle "teamwork concurrency" in that case? I always asked your staffs: "Do you really check for the latest saved date-time before you AUTOSAVE and overwrite the current one from the cache?" I hope you can take my point into consideration. Thank you.
This is a re-post of a comment on Introducing Form Revisions: Never Lose Your Work Again!
- CarinaAnswered on January 30, 2014 at 08:52 PM
This is a brand new feature (launched today!) and we are quite excited as it gives support to a lot of requests from the users.
We thank you for your input and would be glad to hear your feedback on this new feature, as we are always trying to improve our products so they fit the needs of our customers.
- cettoxAnswered on January 31, 2014 at 03:33 AM
Hi Antonio Ooi,
Your points are perfectly valid, we need a mechanism that would prevent data losses in case of form is being edited on multiple browsers by multiple(or single) users. There are several solutions to that, one of them is checking last save time, to detect possible overwrite operations.
Yet, we have to implement those solutions to enable data lossless concurrent form editing, Form Revision History feature would allow you to revert back to any old revision(revisions created before/near january 1st 2014) thus preventing any permenant data loss you may encounter during multi browser overwrite situation.
Just go to myforms section and fire up revision history for the form you want, choose appropriate revision and you have just saved your form! This feature would definitely prevent permanent form data loseses, and it is a big step towards multi user concurrent form editing.
- antoniooiAnswered on January 31, 2014 at 04:24 AM
Well, I hope that the revision history won't miss my latest version in case overwritten by the autosave feature. By right, the "autosave" feature that is out of user's control must not be used as the final copy but as a backup in case user exit jotform without saving. It should be saved in a separate draft folder and up to the user to discard it or make it as latest. JotForm cannot simply make their own assumption by keep overwriting the user's work -- what if the user simply wants to try out something and later prefer to exit without saving? So JotForm will be making the user's failed experiment their final work?
In addition to this, if each autosave will be considered as one new revision in the revision history, then there will be a lot of revisions for the user to choose and recover. I personally feel that revision should only be tracked by MANUAL SAVING BY USER without the autosave copies. Autosave copies should be gone into Draft Folder and up to the users to discard them, empty them, or restore as latest version. So whenever the user restore the latest version from the draft folder, you revision history will also keep a copy of the older version. In short: user action = revision history; auto action = draft copies. Revision is only meaningful to the users when it is within the user's knowledge. Autosaved revision copies can never be useful to the users.
As such, I believe your programming work will be much more straightforward than before at the same time 100% guarantee safe to the end users. Just a thought.
- JotForm FounderaytekinAnswered on January 31, 2014 at 06:41 AM
I agree that a draft & publish workflow would work much better especially for forms which are live. I appreciate your feedback on this. I competely agree with your suggestion. We will definitely consider such a workflow in the future versions of the form buillder.
But, for the time being, we do have a solution for this. While working on your form you can disable auto-save. To enable auto-save click on an empty space on the form builder's form canvas. (either above or below the form) Then, select "Disable Auto Save". This will prevent form builder to save your changes to be written.
I also agree that we are not good at collaboration. If you open the same form on multiple form builders you simply write over each other. In the day and age this is not acceptable. We are aware of this problem and have plans to solve it.
- antoniooiAnswered on January 31, 2014 at 08:36 AM
The 'Disable Auto Save' is one great idea for safety purposes before you managed to come out with the new workflow. I appreciate your thoughtful idea on 'Disable Auto Save'. I just tested it: It is globally disabled once disabled -- This is just what I'm looking for at the moment. Thanks a lot!