Petals Web-Console

This is not about clickability, but use :
Reinstalling a SA happens often while developing.
For now, you have to:
Stop the SA
Shutdown the SA
Uninstall the SA
Install a new SA (Install an SA => browse => select your new SA => Validate => Validation page => Continue)

Because reinstalling an SA is a common thing, why not add a "Reinstall" button ?
(again, that's only an idea if you go on an ergonomic improvement pass one day, that's far from essential)

Globally, there are lots of clicks, and we loose references to know where we are (not obvious to see which menu is selected, and sometimes we loose the menu). I used two or three tabs in Firefox avoid clicking all the time.

• Always keep the menu: When selecting files to import, "Clear all" or Charts, we loose all menu references. We get lost.

• "It worked" notification message: Operation validation (clear all, import SA, etc) : Instead of one page telling it worked, and a "continue" button to come back to the main page, why not going directly to the main page, with a highlighted text notification on this main page ? It avoid one click, and avoid disorientation because loosing the menus.

• "Install another SA" button: If you keep the "All SUs of the SA were successfully deployed" validation page (instead of a text notification on the main page) => Adding a "Install another SA" button, aside the "Continue" button, will divide clicks by two.

• Exchange filters activated by default: In my case, exchange filters should be activated by default once created.

• Exchange filters icons: The small icon to activate exchange filters could be more intuitive, and not need a Legend to explain it. Using the same icons and convention as for the SA (start/stop) looks efficient and simple.

Improve clickability (user experience)

• Make the "Petals ESB" logo clickable, as this is a navigation convention (=> go to Home)

• "Change server" and "Manage Connection" are juste aside, with no differenciation. It is very small, and we do not understand it is clickable. 1/ Clickable: Use a clickable text convention, maybe using underline, and increasing text size OR turn it to a button aspect. 2/ We don't make difference between the two links => Add space between them OR underline OR utrn to buttons.

• Unify the clickable text convention: All clickable text have the same color, preferably underlined, and behave the same way when hovered. Look at this page for example : http://www.google.fr/intl/fr/privacy.html

• Make difference between selected and unselected menus. Usually the gray menu is the one in background, and the highlighted one is the one selected. It is the contrary in the webconsole :S