Re:The screen that set off the ballistic missile alert on Sa...
by kpil on Tuesday January 16, 2018 @01:09PM
(#16160441)
I ended up with a checkbox plus a mandatory input field requesting a reason for one irreversible action in a system I worked on.
Just adding a checkbox and later a popup with an additional warning wasn't enough.
An undo function is obviously best, but ufortunately while technically possible, it took a while - possibly a day - to restore due to ripple effects in other systems, and it normally wasn't the person clicking the button that had any reason to notice something was wrong.
Re:The screen that set off the ballistic missile alert on Sa...
by Someone1234 on Tuesday January 16, 2018 @02:09PM
(#16161184)
Undo is definitely the ultimate UI safeguard.
Unfortunately a lot of organizations don't want to invest the time/resources into creating it. Particularly when it gets into discussing exactly how the underlying data should be handled during the undo window (e.g. does it exist? Is it just flagged deleted? What about relations? Do all of our queries that touch this data check that? Etc).
They could consider a different UI response between a drill and active alert. Since drills are the majority of their workload they'd get dialog blindness to the drill confirmation, and then you'd design the active alert confirmation to be a-typical of the drill (for example a different color dialog, and have an "I agree" checkbox on the active, but none of the drill).