|
We have a form which has Save/Cancel buttons down at its bottom. A part of this form is managing a collection of file attachments. The user can add, open and delete as many files as she likes. Should the Save/Cancel buttons determine whether changes made to the file attachments are saved or discarded? Or would users expect that these changes are automatically and independently saved, since they entail file operations?
|
|||
|
|
It actually depends on how you will display these changes. Apply/Cancel behaviour should differentiate applied changes from changes which aren't yet saved thus helping user to understand the workflow (modify then apply/save, unsaved changes will be lost, etc). Or, otherwise, you may apply all the changes immediately and provide ability to undo operations (no save/cancel button; gmail uses this approach). So, in a case you're going with "Apply/Cancel" approach you should think about how to show your users that some changes aren't yet applied (activating Apply/Save buttons and marking file attachments as "new" or "unsaved", etc should be enough). I recommend you to join details and file attachments at the single screen like it's done, for example, at gmail, so your users will be aware of all the changes (including file attachments) from the first sight:
|
|||
|
|
|
In an ideal world I would like to be able to edit the attachments to my record and then undo that... to restore my record to how it was, including all attachments. if we are treating attachment operations as totally separate and permanent then I have no buttons to undo that. |
|||||||
|
