In the web-ui, there are multiple situations were the user clicks a button, the application goes off to do something in the background, and there is no 'working' spinner to indicate to the user that something is in progress.
This leads the user to think that nothing has happened, and click the button again, or cancel and retry.
Often retrying cases SMT to error as it is performing the same task twice.
Examples include:
- Clicking "Prepare Migration" -- takes many seconds but there is no loading screen.
- Dialogs for Setting up source and target connection profiles in Prepare Migration (when they do not already exist) -- it takes many seconds to create these resources, but the dialogs remain on screen with the Save and Cancel buttons shown.
Good UX practice for long running activities is to indicate to the user that something is happening with a modal spinner to prevent the user from doing something like trying
Example:
- the loading screen shown when "test connection" is pressed when connecting to source.
- the loading screen shown when connecting to source.
In the web-ui, there are multiple situations were the user clicks a button, the application goes off to do something in the background, and there is no 'working' spinner to indicate to the user that something is in progress.
This leads the user to think that nothing has happened, and click the button again, or cancel and retry.
Often retrying cases SMT to error as it is performing the same task twice.
Examples include:
Good UX practice for long running activities is to indicate to the user that something is happening with a modal spinner to prevent the user from doing something like trying
Example: