What will be the optimal solution for the following use case: A dialog is opened on the screen, when clicking on an action button to send the dialog (after filling in details), in some cases a warning should appear. The user can either accept the warning and send the data or make changes in the dialog and send it again. Where, ideally, I will place the warnings? Should I have a toggle button?
3 Answers
You have a couple of options:
- Warning Notice/Alert
- Waning Notice/Alert with confirmation
- Confirmation Dialog
Warning Notice/Alert
Alerts tend to attract the attention, yet require no further action from the user and could be ignored in some cases, and as @Franchesca has mentioned, this pattern can be placed directly where the issue stands.
Warning Notice/Alert with confirmation
Alerts with confirmation are similar to plain alerts, but they do require action from the user to ensure that they are aware of what is going on, the downside is that it's not recommended to place it with the field, but instead with the action, this means the user would still have to scan and find where the issue is.
Confirmation Dialog
Dialogs attract extra attention as they are stronger in terms of interruption, that's why many designers use it only when it is crucial, they can also generate disappointment, can you imagine a user filling the form for a long time, and just when they thought they are ready, they get this annoying message that notifies them with the bad news.
So let's look at how it goes from the user perspective:
Alerts example:
- Hmm i need to fill the date, i want the entire data in my report.
- Oh, this is some strange message, i'll ignore it.
- Green generate button, all looks good!
- Big Report downloaded, took some time but i'm happy.
Alerts with Dialogue
- Hmm i need to fill the date, i want the entire data in my report.
- Oh, what's this message, i cannot ignore it otherwise i cannot download.
- Ah okay, i'll modify the dates.
- Scanning for date, Date modified, all is set.
- Green generate button, all looks good!
- Small Report downloaded, i'm happy.
Confirmation Dialogue
- Hmm i need to fill the date, i want the entire data in my report.
- Green generate button, all looks good!
- Oh, what? now you're telling me? sigh.
- Screw it, big report so be it, i'm not going back now!
- Big Report Downloaded, Compromise made, Feels meh..
-
Thanks a lot. In the first option- did you mean that the warning will appear after first clicking on the 'generate' button? If so, will the user have to click on the generate button again? if so, what will happen if the user will make some changes? It's important to say that the warning might be related to more than one input field, therefore I need it to appear at the end of filling the form.– May.LaviCommented Oct 11, 2018 at 13:28
-
1if the warning is related to a single field then show it immediately after the field is filled, if it's related to a group of fields then immediately after the group is filled, you want to warn the user as early as you can, so that the user doesn't lose focus and move on thinking all is good when its not– UX LabsCommented Oct 11, 2018 at 13:35
-
There's a problem with "after the field is filled." Does that mean "when the cursor leaves the field" (blur event) or "when the user types a key"? In the first case, that event may never happen when the user immediately clicks Generate after typing in the field. In the second case, the notification may come up too early, when the user is not ready typing. So I feel this is not a clear, workable recommendation... Commented Jun 12 at 15:36
I would suggest that such functionality is better implemented in-place, rather than opening an extra dialog.
If you present a subset of information in such dialog, it could be lacking some context. This would then require the user to have to remember what was on the previous screen, or they might click cancel to go back to the previous screen (to remind themselves of the context), and then need to remember which errors were listed in the dialog.
It would be better to show all the warnings in-place in the form, beside the relevant fields. A overall warning can be placed beside the submit button, and the button itself can be disabled until the issues with the data are fixed.
If you need to allow users to override the warnings, provide a checkbox to tick which re-enables the submit button.
-
Thanks! what if the warning messages are too long to present in-place? would you add another section to the dialog (where?) that will contain all the warnings?– May.LaviCommented Oct 11, 2018 at 11:46
-
@May.Lavi The approach would depend on what type of application this is, and which devices you need to support. Is this a web UI, or a desktop application, or what? Commented Oct 11, 2018 at 12:33
-
-
@May.Lavi I think it is fine to push the controls / content down to be able to include the error messages beside the relevant fields. Provided your warnings are a line or 2 of text and not a full paragraph. Commented Oct 11, 2018 at 14:00
I think, when sending this with error is possible, then displaying it on the top of the div element with error color defined in design system(red, pink, orange) and text, which inform user about warning and how to fix it.