[Patternfly] Pattern for form actions

[Gabriel Cardoso]

I’m working on a project that has lots of forms (LiveOak), and I’m thinking about the best way to display the buttons “Cancel”, “Save”, “Delete” and “Clear changes”.

- Scenario 01: the user is trying to create some artefact, e.g. “Create Application”.
	- Initial state: the buttons “Cancel” and “Save” are displayed. “Cancel” takes to the previous page if clicked. “Save” is disabled, since the required fields where not yet fulfilled. 
	- Required fields are edited: “Save” is now enabled. The user stay in the same page after Saving.

- Scenario 02: the user is editing some artefact, e.g. “Edit Application”.
	- Initial state: the button “Delete” is displayed.
	- After some edition: “Delete” is hidden and replaced by “Clear changes” and “Save”.
	- After saving or clearing changes: “Clear changes” and “Save” are replaced by “Delete” again.

I’m struggling more with the scenario 02, since buttons appear / disappear depending on the action. However, the interaction feels good in the console.

Another point is that we are using “clear changes”, which undo the user’s changes and keep him in the same page. The button “Cancel” could work to, but the difference is that “cancel” would take it to the previous page (probably the applications list).

What do you guys think about this approach? How are you guys dealing with this in your projects?

Thanks,
Gabriel

---
Gabriel Cardoso
User Experience Designer @ Red Hat

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/patternfly/attachments/20140409/01c49c37/attachment.htm>