Users should receive error message when a username is already taken

[danfox01]

Describe the bug In Polaris, users who try to choose a username that's already taken should get an error message. This is not currently happening. Instead the page just reloads with no feedback explaining why.

There is an error message defined in Polaris for this case, but we're not showing it in our customized version.

To Reproduce (Provided by Karrie Armetta)

1. Got to bcpl.info and select "Account"
2. Select "Create Username"
3. Enter Barcode = 21183039619142 and Password = 5628 (this is a test accounts)
4. Under "Change Logon" check the box next to “Change Username”
5. New Username = karmetta; Verify Username = karmetta (This is the username for my account already in use)
6. Save
7. Note you are taken to the top of the page, but no other feedback is given.

Expected behavior When the steps above are completed, the user should receive an error message. The exact message is already defined in Polaris as PACML_CHANGEUSERNAME_1307 -- ideally, we would just display this string when the user clicks save in the process above.

Affected device and browser:

• All

Additional context I was unable to find a similar inline error message that we could replicate the styling on. When it comes time to design the error layout and figure out where it goes, here are some guidelines:

• If the entire page reloads and takes the user to the top, the error should display near the top of the content area as well, so the user will see it immediately.
• If the page does not reload and the error simply appears when it's triggered, the message should go in the Change Logon box, near the inputs it's referring to.
• Check in with @sdurphy or @hburnopp for exact styling when you're ready for it.

[tmccoy529]

@danfox01 so looking at this I noticed that when the screen re-loads and jumps to the top it shows Username: [None]. It looks like we can add to that the error message you have listed above in place of none which really doesn't make sense. Scrolling down to where you can change username its all highlighted red to signify there's a problem so that might be a temporary solution and would be quick since it doesn't seem like we have an alert section setup on this page.

However is there a test account in ils-test I can use to see if these changes work? Using that barcode in ils got me yelled at.

[mcorasan]

@tmccoy529 - I sent you the credentials for ilstest via teams and it has been added to the Web Services keepass

[tmccoy529]

@jdomasky this is ready for a look. Im not sure the best place to put the error message so I just placed it at the top as Dan had suggested since it reloads to the top but it might need some tweaking.

[tmccoy529]

Page to move: repos\Polaris Skin for BCPL\patronaccount\default.aspx

[jdomasky]

@tmccoy529 Thanks! I'll review this in Polaris dev either today or early next week.

FYI @hburnopp @mcorasan @theilman7 @tthbcmd

[jdomasky]

@tmccoy529 I've confirmed the solution in dev and I recommend it for deployment to prod with a suggested change to the layout:

• Before testing, I confirmed the issue (i.e., the message doesn't appear in Polaris prod when I use my own credentials with the "karmetta" username).
• Then I triggered the error message in Polaris dev when I use the provided credentials. The message ("The Username you entered is unavailable. Please try another Username.") appears in desktop and mobile.

The error message seems to be indented 1.25em at the mobile breakpoint. However, at all other breakpoints, the message is displayed flush with the left DIV boundary, as shown in the screenshot of the tablet breakpoint above.

Recommendation: Apply the 1.25em indent at all breakpoints.

FYI @hburnopp @mcorasan @theilman7 @tthbcmd

[tmccoy529]

@jdomasky I have added the 1.25em to all break points. This is ready for a look.

files to move: repos\Polaris Skin for BCPL\custom\themes\bcpl-powerpac\site.css

[jdomasky]

@tmccoy529 I reviewed the CSS change in dev and the error message is now displayed consistently at all breakpoints. I recommend this solution for deployment to production.

FYI @hburnopp @mcorasan @theilman7