cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Integrity error/confirmation dialogs are easy to be accidently accepted/closed when popping up

Participant

Integrity error/confirmation dialogs are easy to be accidently accepted/closed when popping up

Integrity error/confirmation dialogs are easy to be accidently accepted/closed when popping up from nowhere:

The problem here is that Integrity forces users from time to time to make a decision when such a dialog pops up and doesn't allow to ignore that to a later point in time.

 

So even if you bring another application in focus and you try to continue your non-Integrity work without dealing with that waiting Integrity dialog it happpens that the Integrity dialog blocks you and comes to foreground.

In case of real Integrity error messages it becomes even more annoying. Sometimes the error dialog reoccurs again and again even if you confirm it a hundred times. So working outside Integrity in any other application is impossible as Integrity always catches the focus with every new error dialog. This only stops when you kill the Integrity process. Waiting is no option as Integrity won't let you use your system as long as an error message is available.

 

So, even if that behavior is declared as design, it needs to be improved in terms of usability and user satisfaction. It's a clear defect.

 

 

1 REPLY 1

Re: Integrity error/confirmation dialogs are easy to be accidently accepted/closed when popping up

I agree with your sentiment.  Hence why we are starting to roll out a new web UI with the first release in July to support some basic use cases and the infrastructure.  Then additional use cases will be added quarterly and released more quickly than the core Integrity solution.