Skip to content
This repository has been archived by the owner on Dec 13, 2020. It is now read-only.

UX: Error Messages #2656

Open
metas-mk opened this issue Mar 25, 2020 · 1 comment
Open

UX: Error Messages #2656

metas-mk opened this issue Mar 25, 2020 · 1 comment

Comments

@metas-mk
Copy link
Member

metas-mk commented Mar 25, 2020

Is this a bug or feature request?

FR

What is the current behavior?

Currently, some error messages are used in metasfresh that the user does not understand and even worse, leaves the user in a situation without solutions proposal and a lost and frustrating feeling. Further, error message and info boxes are shown in the same area (top right) which leaves the user in a bad feeling seeing an info box after receiving an error message.

Which are the steps to reproduce?

Example: Try to reactivate a Sales order which is already delivered.
image
image

What is the expected or desired behavior?

  • The User shall receive a clear error message that shall guide to a solution that can be done by the user
  • Use simple language and don't concern the user with technical details
    • What problem occured?
    • Why did it happen?
    • How can you solve it?
  • Don't blame the user, stay humble
  • Distinguish between error message (general popup or directly where it occurs e.g. under field etc.) and info messages (other look and feel
  • Redesign the look and feel of all message popups to make them much more friendly
@metas-mk
Copy link
Member Author

Error messages in Filter Parm screen

Reproduce:

  • Open Filter criteria with multiple mandatory parms. Leave the mandatory parms empty. Press done.
    • the Filter parm screen disappears and the user receives an error message for the first filter parm.

ToDo

  • When pressing done and mandator parms are not filled, then leave the filter screen open and display the error messages for each field underneath the field, telling the user what is needed.
  • Have a cancel button that closes without using the filter (behavior shall be like closing by clicking outside filter screen).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants