Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable "Save and continue" for Requestor Info, Beneficial Owners, and Validate Steps until all mandatory fields have an entry #4842

Merged
merged 9 commits into from
Sep 1, 2021

Conversation

luacmartins
Copy link
Contributor

@luacmartins luacmartins commented Aug 26, 2021

Details

The Save and Continue button for Requestor Info, Beneficial Owners and Validate Steps should be disabled until all required fields have an entry.

Fixed Issues

$ #4836

Tests

  1. Login to New Expensify (make sure your account does not have the Expensify Card enabled nor withdrawal bank accounts setup)
  2. Create a workspace
  3. Select Get Started in Expensify Card tab of workspace
  4. Go through VBA flow using SO credentials to add a PENDING account and note that in the three mentioned steps, Save and Continue is disabled until all required fields are filled out.
  • Requestor Info Step (all fields)
    requestor

  • Beneficial owners (accept terms and certify information is accurate)
    beneficial

  • Validate Step (all fields)
    validate

QA Steps

Steps above.

Tested On

  • Web
  • Mobile Web
  • Desktop
  • iOS
  • Android

Screenshots

Web

web.mov

Mobile Web

mobile-web.mov

Desktop

desktop.mov

iOS

ios.mov

Android

android.mov

@luacmartins luacmartins self-assigned this Aug 26, 2021
@luacmartins luacmartins requested a review from a team August 26, 2021 17:16
@luacmartins luacmartins marked this pull request as ready for review August 26, 2021 17:16
@MelvinBot MelvinBot requested review from Julesssss and removed request for a team August 26, 2021 17:16
@shawnborton
Copy link
Contributor

Hey @luacmartins - there are a couple of small things I'd love to squeeze into this PR if you don't mind.

First, there seems to be extra white padding on top of the fixed bottom button:
image

There shouldn't be any extra white space there, and that bottom area should start right at the top edge of the button.

Second, I think our disabled button styles are incorrect and they've been bugging me for a while. We currently have two different button styles (default = gray background, success = green background) and so I think we should also have two different styles for each. Basically the disabled green button should still appear somewhat green, like this:
image

Thoughts on making that quick change? Disabled style is pretty simple - it just makes the whole button at 50% opacity.

@luacmartins
Copy link
Contributor Author

Hey @shawnborton! Yea, I don’t mind squeezing those in. I’m ooo until Tuesday, so I’ll make the changes then.

@Julesssss
Copy link
Contributor

Hey @luacmartins, no rush in responding as you're OOO, but I'm not seeing the 'Get Started' option. Is this create card feature geoblocked by any chance or behind a beta?

Screenshot 2021-08-27 at 12 36 23

@luacmartins
Copy link
Contributor Author

@shawnborton I changed the disabled button style and removed the space/padding on top of the button. Can you confirm that these look correct?

Screen Shot 2021-08-31 at 2 57 52 PM
Screen Shot 2021-08-31 at 3 03 55 PM
Screen Shot 2021-08-31 at 3 04 34 PM
Screen Shot 2021-08-31 at 3 04 55 PM

@luacmartins
Copy link
Contributor Author

luacmartins commented Aug 31, 2021

@Julesssss This feature is behind the free plan beta and AFAIK it is not geoblocked. From your screenshot it seems that your test account already has the Expensify Card enabled or a withdrawal bank account setup for payment. If that's the case you won't be able to see the Get Started option and I would try testing with an account without Expensify Cards or withdrawal bank accounts. Let me know if you have any issues.

I updated the test steps to reflect those requirements.

@shawnborton
Copy link
Contributor

shawnborton commented Aug 31, 2021 via email

@luacmartins luacmartins requested a review from a team as a code owner August 31, 2021 23:20
@luacmartins
Copy link
Contributor Author

Updated!

@MelvinBot MelvinBot requested review from joelbettner and removed request for a team August 31, 2021 23:21
Julesssss
Julesssss previously approved these changes Sep 1, 2021
Copy link
Contributor

@Julesssss Julesssss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tests well, I just have one code-style comment.

@luacmartins luacmartins removed the request for review from joelbettner September 1, 2021 16:29
@luacmartins
Copy link
Contributor Author

Updated!

@Julesssss Julesssss merged commit 998d25e into main Sep 1, 2021
@Julesssss Julesssss deleted the cmartins-disable-button branch September 1, 2021 18:18
@OSBotify
Copy link
Contributor

OSBotify commented Sep 1, 2021

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify
Copy link
Contributor

OSBotify commented Sep 2, 2021

🚀 Deployed to staging by @Julesssss in version: 1.0.91-1 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

@isagoico
Copy link

isagoico commented Sep 2, 2021

@luacmartins @Julesssss Hello! We're currently able to access the add bank account flow via the URL method bank-account/new. We will proceed to test this PR this way. Also, we're only able to test this on Web and mWeb since they are the only environments that we have access to the URL.

@Julesssss
Copy link
Contributor

Thanks for reminding us. I'm tagging @kevinksullivan and @MitchExpensify to ensure we test this again ourselves once it's deployed.

@luacmartins
Copy link
Contributor Author

@isagoico comment surfaces the fact that a user can navigate to any of the steps in the process via the URL, e.g. bank-account/requestor without having completed the previous steps. While the flow does not allow the user to advance, it might be a nice polish to redirect the user back to the actual step they are in.

@OSBotify
Copy link
Contributor

OSBotify commented Sep 3, 2021

🚀 Deployed to production by @roryabraham in version: 1.0.92-0 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

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

Successfully merging this pull request may close these issues.

5 participants