I have just returned from a parental leave and have discovered that my team has implemented a 'Save, Submit, Ok, Close' button group on windows. The apparent logic behind the decision was that the Product Manager did not like that clicking 'Save' also closed the window. So currently, the 'Save' button saves the info and provides some text indicating such. 'Submit', closes the window and changes the status of the form, 'Ok', saves & closes and 'Cancel' closes without saving.
We're desigining an application for creating personalized photo books
through a Flash-based interface. When the application first opens, we
display a dialog encouraging the user to give their project a name
(if they don't, it just gets a default name).
I'm currently working on a project that consists of a fairly lengthy
data entry activity.
Today, this process is done through filling out a series of paper forms,
which themselves are fairly. There is an initial set of forms, and then
depending on how those are filled out, other forms may be required. The
smallest possible set of forms consists of 12 full pages of data.
We are now working to put this process online. The original thinking was
to utilize a stepped process for moving the user through the forms