Closed yuwenmemon closed 4 months ago
Triggered auto assignment to @alexpensify (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.
:warning: It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time :warning:
Triggered auto assignment to Design team member for new feature review - @shawnborton (NewFeature
)
Job added to Upwork: https://www.upwork.com/jobs/~017a8c2faf283b52e8
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ishpaul777 (External
)
Hey! I’m Jakub Szymczak from Software Mansion, an expert agency, and I’d like to work on this issue!
📣 @ishpaul777 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app!
Thanks, I've assigned to @SzymczakJ
Update: Even though we are still waiting for API command to be implemented on BE I'll put up a PR with mocked backend interaction. It should be ready tomorrow or on Monday.
@yuwenmemon Can you assign me this one?
@hungvu193 would you be working on whole Sage Intacct project, i dont have any PRs assigned for while so i can help, just let me know : )
Yeah @ishpaul777 - @hungvu193 is working on the whole project and reviewing all PRs underneath since they have broad context.
📣 @hungvu193 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!
Offer link Upwork job Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻 Keep in mind: Code of Conduct | Contributing 📖
PR on this should be ready to review tomorrow(of course we're still waiting for BE but this code could use some checking 😄 ). Btw how is BE work going @yuwenmemon?
Thanks for the update @SzymczakJ!
@SzymczakJ I think we should have the BE done and deployed sometime this week. @NikkiWines said she'll have a PR ready by EOD today! 🎉
Backend PR is up https://github.com/Expensify/Web-Expensify/pull/42400
@hungvu193 PR is ready for review. Please keep in mind that I'm gonna add some API calls/error handling when backend is ready but these should be pretty small changes 😄
Awesome. I'll take a look in a while 👀
Backend PR is up https://github.com/Expensify/Web-Expensify/pull/42400
Please let us know once this is deployed so @SzymczakJ can continue to integrate the API to current PR 😄
What's status of your BE PR @NikkiWines? 😺
It's on staging currently, should be deployed to production on Monday
@NikkiWines how to execute this command properly from FE, doc is missing information on that part. I tried something like
with the credentials with which I logged into Sage Intacct on Old Dot and it's not working 😭. I also tried many other variations of this command usage and all of them fail. Can you give me and example how to invoke ConnectPolicyToSageIntacct
command?
@SzymczakJ the parameter names are slightly different - they're all prepended with intacct
(i.e. intacctCompanyID
, intacctUserID
, intacctPassword
). Also, looks like it should be const parameters: ConnectPolicyToSageIntacct
Other than those two things what you have above should work!
It works! One more question @NikkiWines: what about reusing existing Sage Intacct connection? I have credentials data in intacct config but sage intacct password is encrypted. Using this encrypted password with ConnectPolicyToSageIntacct doesn't work.
I have some problems:
connectionSyncProgress
is not updated when connecting to Sage Intacct. I can connect properly, but I cannot update connection progress because connectionSyncProgress
is undefined all the timewhen will command for updating "Entity" be added on backend(his command is not mentioned in design doc but I guess it should be 😬 )?
@SzymczakJ sounds like you got these answered q's in this slack thread, is that correct?
It looks like the Slack thread has a plan. Keep us posted if you need anything else @SzymczakJ to keep moving forward here. Thanks!
I'll try to check in a few times. If anything urgent is needed here, please ask for help in the #expensify-open-source Slack Room-- thanks!
As we planned to create a follow-up PR, can we create a separate issue for it? @yuwenmemon
Thanks for pointing that out @SzymczakJ, let's me create an issue for it 🙏
⚠️ 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.
@hungvu193 and @SzymczakJ - can we confirm if this deploy blocker notice is accurate or an error? Thanks!
Thank you for this update and swift action.
Reviewing
label has been removed, please complete the "BugZero Checklist".
The solution for this issue has been :rocket: deployed to production :rocket: in version 9.0.5-13 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2024-07-17. :confetti_ball:
For reference, here are some details about the assignees on this issue:
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:
The solution for this issue has been :rocket: deployed to production :rocket: in version 9.0.6-8 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2024-07-22. :confetti_ball:
For reference, here are some details about the assignees on this issue:
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:
I believe the payment date has been moved to 7/22, and will prepare accordingly.
No payment needed for me. I will be paid later after SageIntacct project is completed
@hungvu193 - thank you for that update. Here is the payment breakdown for the records:
Payouts due: N/A
Upwork job is https://www.upwork.com/jobs/~017a8c2faf283b52e8
Tracking GH: https://github.com/Expensify/Expensify/issues/388780
Design doc section: https://docs.google.com/document/d/1k3ZFw8KB55yPUSCG6KYZlwpwEtmRt3eUshwxs7bZq5I/edit#heading=h.w7qju91gpvcq
Before diving into it, let’s add it to the list of the available connections options.
Next, we’re going to show it in the Accounting page. To do this, modify
PolicyAccountingPage.tsx
:Creating the connection button
The code for the
ConnectToSageIntacctButton.tsx
component would look like something like this:Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @alexpensify