feat: add upgrade screen to more features #45131

allroundexperts · 2024-07-09T23:21:12Z

Details

This PR connects Report fields, NetSuite and Sage Intacct with the upgrade flow.

Fixed Issues

$ #43908
$ #43913

PROPOSAL: N/A

Tests

Create a new workspace and go to its settings.
Select More features tab and click on Report Fields.

Verify that workspace upgrade flow opens up.

Enable accounting. Then go to accounting tab.
Click on Sage Intacct and NetSuite.

Verify that workspace upgrade flow opens up.

Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

Create a new workspace and go to its settings.
Select More features tab and click on Report Fields.

Verify that workspace upgrade flow opens up.

Enable accounting. Then go to accounting tab.
Click on Sage Intacct and NetSuite.

Verify that workspace upgrade flow opens up.

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2024-07-10.at.3.59.47.AM.mov

Android: mWeb Chrome

Screen.Recording.2024-07-10.at.3.59.01.AM.mov

iOS: Native

Screen.Recording.2024-07-10.at.3.57.20.AM.mov

iOS: mWeb Safari

Screen.Recording.2024-07-10.at.3.56.27.AM.mov

MacOS: Chrome / Safari

Screen.Recording.2024-07-10.at.3.51.44.AM.mov

MacOS: Desktop

Screen.Recording.2024-07-10.at.3.55.09.AM.mov

melvin-bot · 2024-07-09T23:21:17Z

@rushatgabhane 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]

rushatgabhane · 2024-07-10T23:01:54Z

src/pages/workspace/WorkspaceMoreFeaturesPage.tsx

@@ -204,6 +204,13 @@ function WorkspaceMoreFeaturesPage({policy, route}: WorkspaceMoreFeaturesPagePro
                    return;
                }
                if (isEnabled) {
+                    if (policy?.type !== CONST.POLICY.TYPE.CORPORATE) {


NAB: Could you please replace this with the util function: isControlPolicy().
Reason: Code is duplicated 3 times

https://github.com/Expensify/App/pull/43151/files#diff-89601c1d4ab7d6fb789ea45b8f8e16ead0f925cf0db25d9b5c3561816d7a94c1

The function is currently not in main, so you can just take it from there. Hope that's okay : )

rushatgabhane · 2024-07-10T23:03:59Z

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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- 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

src/components/ConnectToSageIntacctButton/index.tsx

src/CONST.ts

src/languages/en.ts

allroundexperts · 2024-07-15T08:21:27Z

Added GL codes integration as well. Waiting on @garrettmknight for translations of GL codes.

src/CONST.ts

yuwenmemon · 2024-07-17T16:18:59Z

src/CONST.ts

+            },
+            [this.POLICY.CONNECTIONS.NAME.NETSUITE]: {
+                id: this.POLICY.CONNECTIONS.NAME.NETSUITE,
+                alias: 'netsuite',


NAB: This can also use the constant.

OSBotify · 2024-07-17T16:32:58Z

✋ 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 · 2024-07-18T14:12:42Z

🚀 Deployed to staging by https://github.com/yuwenmemon in version: 9.0.9-1 🚀

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

OSBotify · 2024-07-19T11:55:23Z

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 9.0.9-2 🚀

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

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

OSBotify · 2024-07-19T19:36:37Z

🚀 Deployed to production by https://github.com/mountiny in version: 9.0.9-5 🚀

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

OSBotify · 2024-07-23T08:02:52Z

🚀 Deployed to production by https://github.com/mountiny in version: 9.0.10-7 🚀

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

add upgrade screen to more features

c29e243

allroundexperts requested a review from a team as a code owner July 9, 2024 23:21

melvin-bot bot requested review from rushatgabhane and removed request for a team July 9, 2024 23:21

allroundexperts added 3 commits July 10, 2024 21:43

merge with main

7e7d32a

permission file changes

5d162f7

add spanish translations

8885d84

rushatgabhane reviewed Jul 10, 2024

View reviewed changes

src/components/ConnectToSageIntacctButton/index.tsx Outdated Show resolved Hide resolved

yuwenmemon requested changes Jul 12, 2024

View reviewed changes

src/CONST.ts Outdated Show resolved Hide resolved

src/languages/en.ts Show resolved Hide resolved

allroundexperts added 2 commits July 15, 2024 12:23

Merge branch 'main' into feat-43908

8a077b9

add gl codes

fb2d825

allroundexperts added 4 commits July 15, 2024 14:20

handle comments

098b5b5

remove permission changes

e468be4

use isControlPolicy

902ca9d

update translations

d00ae77

yuwenmemon requested changes Jul 15, 2024

View reviewed changes

src/CONST.ts Outdated Show resolved Hide resolved

src/CONST.ts Outdated Show resolved Hide resolved

src/CONST.ts Outdated Show resolved Hide resolved

src/CONST.ts Outdated Show resolved Hide resolved

src/CONST.ts Outdated Show resolved Hide resolved

allroundexperts added 2 commits July 17, 2024 04:32

Merge branch 'main' into feat-43908

b10e6f8

handle comments

03863a6

yuwenmemon approved these changes Jul 17, 2024

View reviewed changes

yuwenmemon merged commit c82183b into Expensify:main Jul 17, 2024
21 checks passed

github-actions bot mentioned this pull request Jul 18, 2024

Deploy Checklist: New Expensify 2024-07-18 #45680

Closed

61 tasks

lanitochka17 mentioned this pull request Jul 18, 2024

[HOLD for payment 2024-08-07] [Upgrades] There is no transition animation when closing upgrade RHP #45689

Closed

6 tasks

shubham1206agra mentioned this pull request Jul 19, 2024

Fixed NetSuite access variant #45761

Merged

51 tasks

This was referenced Jul 19, 2024

[HOLD for payment 2024-08-01] [HOLD for payment 2024-07-26] [Upgrades] Connect NetSuite integration with the upgrade flow #43908

Closed

[HOLD for payment 2024-07-26] [Upgrades] Connect Sage Intacct integration with the upgrade flow #43913

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: add upgrade screen to more features #45131

feat: add upgrade screen to more features #45131

allroundexperts commented Jul 9, 2024

melvin-bot bot commented Jul 9, 2024

rushatgabhane Jul 10, 2024 •

edited

Loading

rushatgabhane commented Jul 10, 2024 •

edited

Loading

allroundexperts commented Jul 15, 2024

yuwenmemon Jul 17, 2024

OSBotify commented Jul 17, 2024

OSBotify commented Jul 18, 2024

OSBotify commented Jul 19, 2024

OSBotify commented Jul 19, 2024

OSBotify commented Jul 23, 2024

feat: add upgrade screen to more features #45131

feat: add upgrade screen to more features #45131

Conversation

allroundexperts commented Jul 9, 2024

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Jul 9, 2024

rushatgabhane Jul 10, 2024 • edited Loading

Choose a reason for hiding this comment

rushatgabhane commented Jul 10, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

allroundexperts commented Jul 15, 2024

yuwenmemon Jul 17, 2024

Choose a reason for hiding this comment

OSBotify commented Jul 17, 2024

OSBotify commented Jul 18, 2024

OSBotify commented Jul 19, 2024

OSBotify commented Jul 19, 2024

OSBotify commented Jul 23, 2024

rushatgabhane Jul 10, 2024 •

edited

Loading

rushatgabhane commented Jul 10, 2024 •

edited

Loading