Customer email gave back error.
Looks like if I want to identify a customer and put their email in the field I need to click on a dropdown.
This whole process seems super weird. Why am I putting in an email? Why do I need to click a dropdown? When should I be putting in their email? Etc.

Consider handing this over to a UX person to see if they can rework this part of the tool? A-Aron might be able to help?

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

snetzlaw created an issue. See original summary.

kfitz’s picture

FileSize
51.99 KB

I think this has been resolved in the most recent update. The input field for the email address now has accompanying verbiage to clarify it's purpose.

smccabe’s picture

Status: Active » Postponed (maintainer needs more info)

snetzlaw, can you confirm that this is what you meant or if there is still an outstanding problem.

snetzlaw’s picture

My issue was two part.

The error message looks to be fixed when testing out the module today. A+

The UX issue of the customer field could still use work.
Right now we have a field called CUSTOMER and one called PHONE NUMBER.

It appears that in the CUSTOMER text field is where you can enter an email or a phone number to look up a customer.
Perhaps name this CUSTOMER LOOKUP or CUSTOMER SEARCH. The text tip could then just be 'email or phone number.'

Whats PHONE NUMBER for? Is it a look up? Is it receipt related? Are we just stoked for Phone numbers?

I assume its to pair the phone number to an account but this is obvious to a business or user.

smccabe’s picture

Status: Postponed (maintainer needs more info) » Needs work
dylf’s picture

Assigned: Unassigned » dylf
dylf’s picture

Status: Needs work » Needs review
FileSize
2.28 KB
dylf’s picture

FileSize
1.43 KB

totally uploaded wrong patch

  • smccabe committed 887f71c on 7.x-2.x authored by dylanf
    Issue #2746747 by dylanf, snetzlaw, kfitz, smccabe: Customer email error
    
smccabe’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.