Fix submit expense on internal Expensify policy #52794

mountiny · 2024-11-19T19:20:41Z

Explanation of Change

The expenses policy is owned by the accounts_payable@expensify.com, but its not whitelisted. So adding that account here.

For more context, the options are failing to be added here where the account has Expensify participants, but its not seen as owned by expensify account.

Fixed Issues

$ #52515
PROPOSAL:

Tests

Have account on the Expenses - Expensify Contractors (Expenses and Healthcare only) policy
Go to the workspace chat
Click on the + button
Make sure you can see the Submit expense button there
Go to some open or submitted expense report
Click on the + button
Verify you can submit expenses there too
Submit an expense
Click on the Global Create +
Click on the QAB to submit expense to this policy
Verify the page in RHP opens and it's not showing not here page

Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

Same as tests
// TODO: These must be filled out, or the issue title must include "[No QA]."

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

melvin-bot · 2024-11-19T19:20:47Z

@mollfpr Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

mountiny · 2024-11-19T19:22:47Z

src/CONST.ts

@@ -2082,6 +2083,7 @@ const CONST = {

    ACCOUNT_ID: {
        ACCOUNTING: Number(Config?.EXPENSIFY_ACCOUNT_ID_ACCOUNTING ?? 9645353),
+        ACCOUNTS_PAYABLE: Number(Config?.EXPENSIFY_ACCOUNT_ID_ACCOUNTS_PAYABLE ?? 10903701),


Its the correct accountId

github-actions · 2024-11-19T19:30:35Z

🚧 @mountiny has triggered a test build. You can view the workflow run here.

github-actions · 2024-11-19T19:55:01Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/52794/index.html	https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/52794/index.html

Desktop 💻	Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/52794/NewExpensify.dmg	https://52794.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

mountiny · 2024-11-19T20:12:53Z

mountiny · 2024-11-19T20:13:21Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

mountiny · 2024-11-19T20:14:12Z

Added the checklist as I have tested on the build as well and Nathalie already approved but she is out for the day so do not want to block on this

OSBotify · 2024-11-19T20:25:37Z

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

github-actions · 2024-11-21T01:45:35Z

🚀 Deployed to staging by https://github.com/mountiny in version: 9.0.65-0 🚀

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

mountiny · 2024-11-21T15:33:06Z

I can submit the expenses now

github-actions · 2024-11-22T19:49:38Z

🚀 Deployed to production by https://github.com/chiragsalian in version: 9.0.65-5 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	failure ❌
🍎🔄 iOS HybridApp 🍎🔄	failure ❌

mountiny added 2 commits November 19, 2024 20:13

Add the Accounts_Payable account

7dda715

Revert one change

f7f8372

mountiny added InternalQA This pull request required internal QA Ready To Build labels Nov 19, 2024

mountiny self-assigned this Nov 19, 2024

mountiny requested a review from a team as a code owner November 19, 2024 19:20

melvin-bot bot requested a review from mollfpr November 19, 2024 19:20

melvin-bot bot removed the request for review from a team November 19, 2024 19:20

mountiny removed the request for review from mollfpr November 19, 2024 19:22

mountiny commented Nov 19, 2024

View reviewed changes

nkuoch approved these changes Nov 19, 2024

View reviewed changes

mountiny merged commit f5425e9 into main Nov 19, 2024
18 of 19 checks passed

mountiny deleted the vit-52515 branch November 19, 2024 20:14

github-actions bot mentioned this pull request Nov 21, 2024

Deploy Checklist: New Expensify 2024-11-21 #52862

Closed

65 tasks

melvin-bot bot mentioned this pull request Nov 22, 2024

[HOLD for payment 2024-11-29] Not able to submit expense to Expenses - Expensify CA workspace #52515

Closed

8 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix submit expense on internal Expensify policy #52794

Fix submit expense on internal Expensify policy #52794

mountiny commented Nov 19, 2024 •

edited

Loading

melvin-bot bot commented Nov 19, 2024

mountiny Nov 19, 2024

github-actions bot commented Nov 19, 2024

github-actions bot commented Nov 19, 2024

mountiny commented Nov 19, 2024

mountiny commented Nov 19, 2024 •

edited

Loading

mountiny commented Nov 19, 2024

OSBotify commented Nov 19, 2024

github-actions bot commented Nov 21, 2024

mountiny commented Nov 21, 2024

github-actions bot commented Nov 22, 2024

Fix submit expense on internal Expensify policy #52794

Fix submit expense on internal Expensify policy #52794

Conversation

mountiny commented Nov 19, 2024 • edited Loading

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Nov 19, 2024

mountiny Nov 19, 2024

Choose a reason for hiding this comment

github-actions bot commented Nov 19, 2024

github-actions bot commented Nov 19, 2024

mountiny commented Nov 19, 2024

mountiny commented Nov 19, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

mountiny commented Nov 19, 2024

OSBotify commented Nov 19, 2024

github-actions bot commented Nov 21, 2024

mountiny commented Nov 21, 2024

github-actions bot commented Nov 22, 2024

mountiny commented Nov 19, 2024 •

edited

Loading

mountiny commented Nov 19, 2024 •

edited

Loading