[PAID] [3rd Party Feeds] Implement API calls for 3rd part workspace feeds v1

[dylanexpensify]

Coming from this thread, we have some clean up to-dos for the Third-party workspace feeds v1 initiative.

Issue Owner

Current Issue Owner: @strepanier03

[melvin-bot[bot]]

Auto-assigning issues to engineers is no longer supported. If you think this issue should receive engineering attention, please raise it in #whatsnext.

[VickyStash]

Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue.

[robertjchen]

WorkspaceCompanyCardsPage.tsx

• OpenPolicyCompanyCardsPage(policyID)

WorkspaceCompanyCardsListHeaderButtons.tsx

• AssignCard(policyID, bankName, encryptedCardNumber, email, startDate, reportActionID)

WorkspaceCompanyCardsSettingsPage.tsx

WorkspaceCompanyCardFeedSelectorPage.tsx

WorkspaceMemberNewCardPage.tsx

• OpenPolicyCompanyCardsFeed(policyID, bankName)
• SetCardExportAccount(cardID, exportAccountDetails)
• SetCardName(cardID, cardName)

CardSelectionStep.tsx

• OpenPolicyCompanyCardsFeed() called earlier in the flow should already load the list of cards 🤔

[narefyev91]

Hi, I'm Nicolay from Callstack - expert contributor group - will help here as well (from tomorrow). Will pick:

• WorkspaceCompanyCardsSettingsPage.tsx
• WorkspaceMemberNewCardPage.tsx OpenPolicyCompanyCardsFeed(policyID, bankName) SetCardExportAccount(cardID, exportAccountDetails) SetCardName(cardID, cardName)

[joekaufmanexpensify]

Assigned!

[VickyStash]

@robertjchen I have a question about reportActionID for this API call: AssignCard(policyID, bankName, encryptedCardNumber, email, startDate, reportActionID).

Is it for this message? Should I optimistically create it?

I'm asking cause it looks like we don't create similar messages optimistically while issuing Expensify Cards. ^^ @mountiny

[robertjchen]

Interesting! That's a good point- if these messages are not being optimistically created, then the reportActionID is not needed 👍

[mountiny]

@robertjchen I think it's a bit different thought, right? With Expensify cards, we have to talk to Marqeta, a third-party service, and so there is a higher chance of the call with fail, so we do not create the actions optimistically. In this case, when we already have the list of the available cards, there are fewer things that can cause it to fail, so I think we could consider adding these optimistically; what do you think, @robertjchen?

[robertjchen]

That makes sense, that context definitely helps!

Since we already have all the info we need in Onyx at time of assignment, we can definitely do it optimistically which would make for a better user experience

[mountiny]

@VickyStash Feel free to add the optimistic reportActionID param to the api call and create the action optimistically and we can add it to BE

[VickyStash]

@robertjchen Could you say what action name this optimistic report action should have? I'm talking about the one created during AssignCard API call.

[robertjchen]

@VickyStash It would be CARDASSIGNED

[VickyStash]

I've prepared a Draft PR with:

• AssignCard API call
• Plain implementation of RequestFeedSetup API call
• Support of CARDASSIGNED report action display
• TODOs resolution

@robertjchen Please, let us know when RequestFeedSetup is deployed so we can start extensive testing of the functionality with the real data.

[robertjchen]

Yes, it appears to be under review at the moment 👍

[dylanexpensify]

Making progress

[VickyStash]

Updates:

• Updated params passed to RequestFeedSetup
• Waiting for API fixes

[dylanexpensify]

TY @VickyStash!

[VickyStash]

Updates:

• I was finally able to create a feed using RequestFeedSetup API call!
• Fixed Feed switcher display in pending state
• Fixed feature check at Update Feed name
• Added some TS/lint fixes
• Reported a couple of API related issues and waiting for test setup of feed with cards

[VickyStash]

Updates:

• Integrated OpenPolicyCompanyCardsFeed API call
• Fixed card feed selector
• Waiting for API fixes to be unblocked

[VickyStash]

Updates:

• Updated types and data structure to follow BE updates
• Fixed No Cards view
• Fixed card assignment flow (real-life card selection instead of mocked)
• A lot of minor checks/UI fixes

https://github.com/user-attachments/assets/fa194161-8e8a-4ff0-b0a2-733f85417c14

TODOs (waiting for responses in slack):

• Card names storing/display (slack link)
• Card details data display: Last updates and Transaction start date (slack link)
• CARDASSIGNED report action display - should be fixed by API (slack link)
• Update card (sync) - can be implemented in a separate PR (slack link)
• Getting data to display all workspace member assigned third-party cards (slack link)
• Improve Company Cards screen loading on the first open after login
• Remove Card Feed - can be implemented in a separate PR

[VickyStash]

Not a lot of updates from yesterday:

• Updated member details page to display all of the member cards.
• Waiting for API updates mentioned above

[VickyStash]

Updates:

• Implemented custom card names storing/display
• Waiting for API fixes

[allgandalf]

I am available for reviewing this flow if no C+ is assigned for this already 👋

[VickyStash]

Updates:

• Implemented some improvements related to card details display after the latest API updates got merged.
• Resolved conflicts caused by the latest main, there were pretty much of them since in parallel the work on v2 is going on.
• Fixed minor issues.
• Added test steps and part of the screenshots to the PR.

TODOs: Test the app on mobile platforms and record the videos. After that, I'll open the PR for review. If everything is smooth it should be tomorrow first part of the day.

[VickyStash]

The PR has been opened for the review.

[melvin-bot[bot]]

Triggered auto assignment to @strepanier03 (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO.

[dylanexpensify]

Reassigning as I head to parental leave next week! Thanks Sheena!

[allgandalf]

♻️ PR was merged

[melvin-bot[bot]]

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

[melvin-bot[bot]]

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

• https://github.com/Expensify/App/pull/49928

If no regressions arise, payment will be issued on 2024-10-29. :confetti_ball:

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

• @VickyStash does not require payment (Contractor)
• @narefyev91 does not require payment (Contractor)
• @allgandalf requires payment (Needs manual offer from BZ)

[melvin-bot[bot]]

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:

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

[allgandalf]

No checklist here, this belongs to a project, Only payment remains 🙏 (This is a 3rd party feed project and not direct feed so...)

[mountiny]

$250 to @allgandalf

[allgandalf]

🤣 i wonder what you are doing in 🇯🇵 these days

[mountiny]

psst

[melvin-bot[bot]]

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

• https://github.com/Expensify/App/pull/51080

If no regressions arise, payment will be issued on 2024-10-30. :confetti_ball:

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

• @VickyStash does not require payment (Contractor)
• @narefyev91 does not require payment (Contractor)
• @allgandalf requires payment (Needs manual offer from BZ)

[melvin-bot[bot]]

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:

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

[allgandalf]

No checklist, payment summary here

[mountiny]

New feature so no checklist needed here

[melvin-bot[bot]]

Payment Summary

[Upwork Job]()

• Contributor: @VickyStash is from an agency-contributor and not due payment
• Contributor: @narefyev91 is from an agency-contributor and not due payment
• ROLE: @allgandalf paid $(AMOUNT) via Upwork (LINK)

BugZero Checklist (@strepanier03)

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

[strepanier03]

Payment Summary

• [x] @VickyStash is from an agency-contributor and not due payment
• [x] @narefyev91 is from an agency-contributor and not due payment
• [x] $250 - @allgandalf paid $250 via Upwork (LINK)

[melvin-bot[bot]]

@strepanier03 @mountiny Be sure to fill out the Contact List!

[strepanier03]

The contact list is an old process we don't do any longer, not sure why it's resurfaced. https://expensify.slack.com/archives/C01SKUP7QR0/p1729883091032869