User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It only takes a minute to sign up.
Sign up to join this community
I have an admin console where I can add configure different data sources for my web application. The page looks like this :
Some of my queries are :
Another way of approaching this is instead of having two separate buttons for 'test' and 'save', is to incorporate the test connection into the save functionality. This way it becomes more of a validation process (the system prevents you from failing) rather than putting the burden on the user to ensure it works.
If you follow the above process, then that solves this problem. However, even if the consequence of saving a connection that fails is minimal, it is not user centto allow them to do something that will cause an error in the future.
This will depend almost entirely on your specific configuration/scenario, and will not be able to be answered here.
To answer one part of your question:
Should I allow connection to be saved without testing?
A good design would probably be to automatically test when the user presses save (if it hasn't been tested already).
A related question is: should you allow the source to be saved even if the test fails?
I probably would allow this (with a confirmation dialog that warns the user). Since, possibly the connection could be down, but the user knows it is correct and wants to save it anyway.
