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

[HOLD for payment 2024-03-20] [Wave8] [Simplified Collect] [Workflows] Create Payment page #37197

Closed
lakchote opened this issue Feb 26, 2024 · 48 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Daily KSv2 NewFeature Something to build that is a new item.

Comments

@lakchote
Copy link
Contributor

We've recently merged the main workflows page.

The task here is to create the Payment page present under the main worfklows page.

It will appear when we click on the > icon under the Connect bank account menu item:
image

Expected mockups below

No VBBA flow
image

VBBA flow
image

Technical details can be found here.

@lakchote lakchote added Daily KSv2 NewFeature Something to build that is a new item. labels Feb 26, 2024
Copy link

melvin-bot bot commented Feb 26, 2024

@melvin-bot melvin-bot bot added Weekly KSv2 and removed Daily KSv2 labels Feb 26, 2024
@lakchote
Copy link
Contributor Author

Assigning to Tom since he's leading the wave's progress for simplified collect workflows.

@lakchote lakchote added Daily KSv2 and removed Weekly KSv2 labels Feb 26, 2024
@ishpaul777
Copy link
Contributor

I can volunteer as C+ as i have previously reviewed the related PR and already has access to design doc :D

@luacmartins
Copy link
Contributor

@ishpaul777 would you be able to work on the implementation for this issue since you have access to the design doc?

@ishpaul777
Copy link
Contributor

would you be able to work on the implementation for this issue since you have access to the design doc

Sure 😃 i'd love to work on it

@lakchote
Copy link
Contributor Author

would you be able to work on the implementation for this issue since you have access to the design doc

Sure 😃 i'd love to work on it

Perfect! Thank you. Assigning it to you

Copy link

melvin-bot bot commented Feb 28, 2024

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

@ishpaul777
Copy link
Contributor

false alarm ⬆️

@ishpaul777
Copy link
Contributor

ishpaul777 commented Feb 28, 2024

hii @luacmartins @lakchote, started working on this now, quick question do we have any onyx key to get the added bank account information, ONYXKEYS.REIMBURSEMENT_ACCOUNT only has the information achData.state
Screenshot 2024-02-28 at 10 44 24 PM

@luacmartins
Copy link
Contributor

@ishpaul777 the reimbursementAccount key should have these details, I think we can use that to build the bank account name as shown in the image

@ishpaul777
Copy link
Contributor

it has only state

Screenshot 2024-02-28 at 11 12 59 PM

@luacmartins
Copy link
Contributor

This is the object I see when I have a bank account added. Maybe your account doesn't have a bank account properly set up:

Screenshot 2024-02-28 at 10 44 49 AM

@ishpaul777

This comment was marked as off-topic.

@ishpaul777
Copy link
Contributor

I use these steps, i have added a secondary email in olddot also but i still see these detail in as reimbursementAccountDraft
IMG_0038

Screenshot 2024-02-28 at 11 22 03 PM

@ishpaul777
Copy link
Contributor

ishpaul777 commented Feb 28, 2024

@luacmartins i get this details #37197 (comment), when sign out and re sign in is this known/expected 🤔

@ishpaul777
Copy link
Contributor

ishpaul777 commented Feb 28, 2024

from docs https://docs.google.com/document/d/1T--VcAaCm-8aq5oEO78_vVXxBpXY1gq7NiJrboGZNcs/edit#bookmark=id.bv81jb9oqisz

Using withOnyx(), we’ll check for plaidData Onyx key details. When it’s not empty and it has a bankAccount, meaning the VBBA connection went on successfully, we’ll call the SetWorkspaceReimbursement command.

but actually we check this using achData.state in other places in codebase

@luacmartins i am little confused if reimbursementAccount is already setup then where do we redirect when clicking here?

Screenshot 2024-02-28 at 10 44 24 PM

also do we have the api for SetWorkspaceReimbursement and SetWorkspacePayer ready ?

@luacmartins
Copy link
Contributor

we’ll check for plaidData Onyx key details
this seems wrong since that key is temporary only when we're in the process of connecting with Plaid.

That should navigate to ROUTES.BANK_ACCOUNT_WITH_STEP_TO_OPEN, which would show the EnableBankAccount page
Screenshot 2024-02-28 at 1 40 01 PM

@luacmartins
Copy link
Contributor

@ishpaul777 how's it going with this issue? Do you have a branch or draft PR up yet?

@ishpaul777
Copy link
Contributor

@ishpaul777 how's it going with this issue? Do you have a branch or draft PR up yet?

priortizing working on it will raise a pr today

@luacmartins
Copy link
Contributor

Update:

  • Alias PR is merged. You can keep using Policy_setReimbursementFromChoice for testing for now until the new command SetReimbursementFromChoice is deployed.
  • For the reimburser email from VBBA, we should be using the new reimbursementAccount<policyID> key, with the policyID appended to it. It seems like we don't load this information when opening the Workflows page, so we need a command to do that @lakchote.

@luacmartins
Copy link
Contributor

@ishpaul777 we'll have to create an OpenPolicyWorkflowsPage API command that should be called when the user opens the Workflows page to load this data. I wouldn't block your PR on it though

@jjcoffee
Copy link
Contributor

jjcoffee commented Mar 4, 2024

@trjExpensify Could you assign me here as I'll be reviewing the PR as C+? Thanks! 🙏

@luacmartins
Copy link
Contributor

Done

@lakchote
Copy link
Contributor Author

lakchote commented Mar 6, 2024

@ishpaul777 we'll have to create an OpenPolicyWorkflowsPage API command that should be called when the user opens the Workflows page to load this data. I wouldn't block your PR on it though

PR should be merged today

@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Mar 13, 2024
@melvin-bot melvin-bot bot changed the title [Wave8] [Simplified Collect] [Workflows] Create Payment page [HOLD for payment 2024-03-20] [Wave8] [Simplified Collect] [Workflows] Create Payment page Mar 13, 2024
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Mar 13, 2024
Copy link

melvin-bot bot commented Mar 13, 2024

Reviewing label has been removed, please complete the "BugZero Checklist".

Copy link

melvin-bot bot commented Mar 13, 2024

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.51-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

If no regressions arise, payment will be issued on 2024-03-20. 🎊

For reference, here are some details about the assignees on this issue:

  • @jjcoffee requires payment (Needs manual offer from BZ)
  • @ishpaul777 requires payment (Needs manual offer from BZ)

Copy link

melvin-bot bot commented Mar 13, 2024

BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

  • [@jjcoffee / @ishpaul777] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
  • [@trjExpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

@melvin-bot melvin-bot bot added Daily KSv2 Overdue and removed Weekly KSv2 labels Mar 20, 2024
Copy link

melvin-bot bot commented Mar 20, 2024

Payment Summary

Upwork Job

  • ROLE: @jjcoffee paid $(AMOUNT) via Upwork (LINK)
  • ROLE: @ishpaul777 paid $(AMOUNT) via Upwork (LINK)

BugZero Checklist (@trjExpensify)

  • I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
  • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
  • I have paid out the Upwork contracts or cancelled the ones that are incorrect
  • I have verified the payment summary above is correct

@trjExpensify
Copy link
Contributor

Alright, alright...

We'll take care of the regression tests for the simplified collect project. :)

Let me know if that's correct and I'll get these paid out.

@jjcoffee
Copy link
Contributor

@trjExpensify LGTM!

@trjExpensify
Copy link
Contributor

Perfect. Offers sent!

@jjcoffee
Copy link
Contributor

@trjExpensify Accepted, thanks!

@trjExpensify
Copy link
Contributor

@jjcoffee paid you.

@melvin-bot melvin-bot bot added the Overdue label Mar 25, 2024
@trjExpensify
Copy link
Contributor

@ishpaul777 we're still waiting on you to accept the offer.

@melvin-bot melvin-bot bot removed the Overdue label Mar 25, 2024
@ishpaul777
Copy link
Contributor

Oh sorry i missed this @trjExpensify! I'll accept the offer in my morning, Thank you for ping

@trjExpensify
Copy link
Contributor

Paid! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Daily KSv2 NewFeature Something to build that is a new item.
Projects
No open projects
Archived in project
Status: Release 1: Ideal Nav & Collect Simplfied Profile, Members, Categories, Workflows (approvals)
Development

No branches or pull requests

6 participants