Users shouldn't have to understand SAVE. However, they already understand and you should make use of SUBMIT.
In other words. Store the heck out of the thing at any point, and then require the user to Submit the form at the end and flip in. Store every time the user changes a page, store internally whenever the user switches form fields when there has been a change, and show the user how much they have completed and where they need to go to finish. It is also helpful to allow the user to navigate away and come right back to where they left off without having to skip pages by hand. This works even for repeat forms, since the Submit process logically clears the form. This only doesn't work completely if the user needs to edit multiple forms all at once, or will need to swap between more than one form at a time of the same format. However, it can be made to do that easily with some thought. Also, don't forget to have defaults for everything that makes sense to have a default. If you aren't sure what would make a good default. Have the system generate one automatically by keeping track of fields that need a default... For example... you may not know what a good default might be for something like an internal ORG code, but you can keep track of which code is used the most and make that the default. Or better, keep track for everyone, and also for each individual, and after they have submitted a form use their own default. The end result should be something really fast to fill out repeatedly, and even if it is something people fill out once only, it will be faster because the defaults are truly logical. Remember, a wrong default is better than no default. Will . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=34463 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
