Skip to content

Onboarding: capture accounting system name for Other - #96160

Open
KJ21-ENG wants to merge 15 commits into
Expensify:mainfrom
KJ21-ENG:KJ21-ENG/93290-onboarding-other-accounting-system-name
Open

Onboarding: capture accounting system name for Other#96160
KJ21-ENG wants to merge 15 commits into
Expensify:mainfrom
KJ21-ENG:KJ21-ENG/93290-onboarding-other-accounting-system-name

Conversation

@KJ21-ENG

@KJ21-ENG KJ21-ENG commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Adds an optional accounting-software name input when an onboarding user selects Other. The name is stored separately from the existing userReportedIntegration: 'other' value, trimmed, and sent as userReportedIntegrationName with CreateWorkspace and CompleteGuidedSetup only when Connections remains enabled and the name is non-empty.

The accounting screen reveals the input without automatically focusing it or forcing the options viewport to scroll. The option grid remains stationary, the top row stays visible, and the responsive card layout does not shift when the content becomes scrollable.

Fixed Issues

$ #93290
PROPOSAL: #93290 (comment)

Tests

  1. Verify that no errors appear in the JS console.
  2. Sign in with a new account and start the onboarding flow for managing a team.
  3. Continue to the accounting-software step and select Other.
  4. Verify the Your accounting software input appears below the option grid without automatically receiving focus, moving the cards, clipping the first row, or being hidden behind the fixed Continue footer.
  5. Enter Acme Books and press Continue.
  6. On Interested Features, leave Connections enabled and press Continue.
  7. Verify the CreateWorkspace and CompleteGuidedSetup requests keep userReportedIntegration: 'other' and include userReportedIntegrationName: 'Acme Books'.
  8. Repeat the flow, enter a custom name, then select a supported integration. Verify the input is hidden and neither request includes userReportedIntegrationName.
  9. Repeat with Other and a blank/whitespace-only input. Verify onboarding can continue and neither request includes userReportedIntegrationName.
  10. Repeat steps 3-9 on a narrow/mobile viewport and a wide/desktop viewport. Verify selecting Other does not jump or force-scroll the options viewport, the first row remains visible, the input remains reachable above the footer, and the option cards retain their widths and spacing. On a genuinely constrained viewport, verify the screen can still be scrolled manually to the input.
  • Verify that no errors appear in the JS console

Offline tests

  1. Open the accounting-software onboarding step, then go offline.
  2. Select Other, enter Acme Books, and press Continue.
  3. Verify the Interested Features step opens with Connections enabled and the input remains restored when navigating back.
  4. Return to Interested Features and verify Continue is disabled while offline.
  5. Reconnect, finish onboarding, and verify the onboarding requests send userReportedIntegration: 'other' with userReportedIntegrationName: 'Acme Books'.
  6. Verify that no errors appear in the JS console.

QA Steps

  1. Sign in with a new account and start the onboarding flow for managing a team.
  2. On the accounting-software step, select Other and verify the Your accounting software input is fully visible above the footer.
  3. Enter Acme Books, continue with Connections enabled, and complete onboarding.
  4. Verify both onboarding requests include userReportedIntegration: 'other' and userReportedIntegrationName: 'Acme Books'.
  5. Repeat with a supported integration, None, and a blank Other input; verify userReportedIntegrationName is omitted in all three cases.
  6. Repeat on narrow and wide layouts and verify selecting Other does not automatically focus the input, jump or force-scroll the options viewport, clip the first row, change the card spacing, or hide the input behind the footer. On a genuinely constrained viewport, verify the input remains reachable through manual scrolling.
  7. Verify that no errors appear in the JS console.
  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover 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 tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • 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 that 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)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • 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 new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • 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)
  • 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.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • 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.

Screenshots/Videos

Android: Native
Screen.Recording.2026-08-05.at.1.26.19.AM.mov
Android: mWeb Chrome
Screen.Recording.2026-08-05.at.2.37.42.AM.mov
iOS: Native
Screen.Recording.2026-08-04.at.11.29.38.PM.mov
iOS: mWeb Safari
Simulator.Screen.Recording.-.iPhone.17.-.2026-08-05.at.02.06.35.mov
MacOS: Chrome / Safari
Screen.Recording.2026-08-04.at.11.29.38.PM.mov

@melvin-bot

melvin-bot Bot commented Jul 15, 2026

Copy link
Copy Markdown

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

@KJ21-ENG
KJ21-ENG force-pushed the KJ21-ENG/93290-onboarding-other-accounting-system-name branch from 885b7d8 to 62a15bd Compare July 15, 2026 07:47
@KJ21-ENG
KJ21-ENG marked this pull request as ready for review July 15, 2026 10:04
@KJ21-ENG
KJ21-ENG requested review from a team as code owners July 15, 2026 10:04
@KJ21-ENG

Copy link
Copy Markdown
Contributor Author

FYI :- Failing jest tests are unrelated to this PR. Thanks!

@melvin-bot
melvin-bot Bot requested review from ahmedGaber93 and flaviadefaria and removed request for a team and flaviadefaria July 15, 2026 10:04
@melvin-bot

melvin-bot Bot commented Jul 15, 2026

Copy link
Copy Markdown

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

@melvin-bot
melvin-bot Bot removed the request for review from a team July 15, 2026 10:04
Comment thread src/pages/OnboardingAccounting/BaseOnboardingAccounting.tsx Outdated

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 62a15bd735

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/pages/OnboardingAccounting/BaseOnboardingAccounting.tsx Outdated
@KJ21-ENG

Copy link
Copy Markdown
Contributor Author

@ahmedGaber93 Does this looks good? means on mobile screen our optional text field is displayed under 'None' field. so when user selects 'Other' then he will be unaware about this optional field. So there are possibilites that he can just move forward without mentioning any name not because he dont wants to but may be he is unaware about the field.

Though I have followed existing pattern, but I think we should take feedback of designing team. Maybe we can do something like, screen gets auto scrolled when 'Other' is selected so our optional text field gets on screen. WDYT ? 👀

1784147952161917.mp4

@ahmedGaber93

Copy link
Copy Markdown
Contributor

@KJ21-ENG The BE PR BE is deployed to staging, could you please complete checklist and the screenshots? thanks!

@ahmedGaber93

Copy link
Copy Markdown
Contributor

@dannymcclain WDYT here #96160 (comment)?

@KJ21-ENG

Copy link
Copy Markdown
Contributor Author

@ahmedGaber93 Sure, On it.

@ahmedGaber93

ahmedGaber93 commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

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 that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • 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 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 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)
  • 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)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • 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
    • 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 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.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • 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: HybridApp
a.mov
Android: mWeb Chrome
aw.mov
iOS: HybridApp
i.mov
iOS: mWeb Safari
iw.mov
MacOS: Chrome / Safari
w.mov

@dannymcclain

Copy link
Copy Markdown
Contributor

@dannymcclain WDYT here #96160 (comment)?

I think we should either move the Other option to be the last option, or add the input directly underneath Other (and thus above None. @Expensify/design any thoughts/feelings here?

@flaviadefaria

Copy link
Copy Markdown
Contributor

I think we should do this:

add the input directly underneath Other (and thus above None)

KJ21-ENG added 3 commits July 28, 2026 21:22
…arding-other-accounting-system-name

# Conflicts:
#	src/ONYXKEYS.ts
#	src/libs/actions/Welcome/index.ts
#	src/pages/OnboardingAccounting/BaseOnboardingAccounting.tsx
#	src/pages/OnboardingInterestedFeatures/BaseOnboardingInterestedFeatures.tsx
#	tests/actions/ReportTest.ts
@codecov

codecov Bot commented Jul 28, 2026

Copy link
Copy Markdown

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/libs/actions/Policy/Policy.ts 70.51% <ø> (ø)
src/libs/actions/Report/index.ts 71.41% <ø> (-0.48%) ⬇️
.../OnboardingAccounting/BaseOnboardingAccounting.tsx 97.72% <100.00%> (+2.41%) ⬆️
src/hooks/useCompleteOnboarding.ts 0.00% <0.00%> (ø)
... and 51 files with indirect coverage changes

@KJ21-ENG

Copy link
Copy Markdown
Contributor Author

We will have to wait before proceeding here as confirmation on this might change direction of this PR little bit.

@flaviadefaria @ahmedGaber93 @dukenv0307

@dannymcclain

Copy link
Copy Markdown
Contributor

Yep let's send it.

@KJ21-ENG

KJ21-ENG commented Aug 6, 2026

Copy link
Copy Markdown
Contributor Author

Done in de97514 . Thanks

@ahmedGaber93

Copy link
Copy Markdown
Contributor

@flaviadefaria Is it correct for the text input to be optional here, or should it be required?

Screen.Recording.2026-08-07.at.6.41.04.PM.mov

@ahmedGaber93

Copy link
Copy Markdown
Contributor

@KJ21-ENG Should the input autofocus after selecting "Other"?

It doesn't appear to autofocus in your video here: #96160 (comment)

CC @dannymcclain

@dannymcclain

Copy link
Copy Markdown
Contributor

Should the input autofocus after selecting "Other"?

Oh yeah good shout. I think it should autofocus.

@flaviadefaria

Copy link
Copy Markdown
Contributor

@flaviadefaria Is it correct for the text input to be optional here, or should it be required?

It should be optional.

@ahmedGaber93

ahmedGaber93 commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Bug: The keyboard hides the input field when it opens.

Platforms: Native Android / mWeb safari

Screen.Recording.2026-08-07.at.7.25.46.PM.mov
Screen.Recording.2026-08-07.at.7.37.59.PM.mov

@KJ21-ENG

KJ21-ENG commented Aug 9, 2026

Copy link
Copy Markdown
Contributor Author
Screen.Recording.2026-08-10.at.12.48.21.AM.mov

@ahmedGaber93

Copy link
Copy Markdown
Contributor

@KJ21-ENG any updates here #96160 (comment)?

@KJ21-ENG

KJ21-ENG commented Aug 12, 2026

Copy link
Copy Markdown
Contributor Author

Strange, I thought I pushed a commit along with this comment.

Apologies here, I am doing it. Thanks.

@KJ21-ENG

Copy link
Copy Markdown
Contributor Author

@ahmedGaber93 Does this look good to you?

Screen.Recording.2026-08-12.at.9.06.22.PM.mov

@dubielzyk-expensify

Copy link
Copy Markdown
Contributor

@ahmedGaber93 Does this look good to you?

Looks nice to me even though I'm not who you tagged :)

@quinthar quinthar removed the #convert label Aug 13, 2026
@ahmedGaber93

Copy link
Copy Markdown
Contributor

@KJ21-ENG Thanks for updates.

Bug: The keyboard hides the input field when it opens.
Platforms: Native Android /

The bug is fixed on native Android, but it still doesn’t work as expected on mWeb Safari.

Are you facing the same issue?

Screen.Recording.2026-08-13.at.11.34.02.AM.mov

@KJ21-ENG

KJ21-ENG commented Aug 13, 2026

Copy link
Copy Markdown
Contributor Author

@ahmedGaber93 Fixed in 0e0b0c1. Root cause: the page’s ScreenWrapper max-height and virtual-viewport handling suppressed Safari’s focused-input reveal after the keyboard resized the viewport. mWeb Safari now keeps the autofocused input visible above the keyboard.

Screen.Recording.2026-08-13.at.2.46.19.PM.mov

@ahmedGaber93 ahmedGaber93 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@melvin-bot
melvin-bot Bot requested a review from tylerkaraszewski August 13, 2026 09:50
@KJ21-ENG

Copy link
Copy Markdown
Contributor Author

FYI, failing jest test is unrelated to thi PR

@KJ21-ENG

Copy link
Copy Markdown
Contributor Author

@ahmedGaber93 Does this look good to you?

Looks nice to me even though I'm not who you tagged :)

@dubielzyk-expensify haha, is there any way to tag all designe members at once ? something like designing team tag ? as i ofent misses to tag one or other member (though this time i missed to tag any of the designing member) 🤔

@dannymcclain

Copy link
Copy Markdown
Contributor

@dubielzyk-expensify haha, is there any way to tag all designe members at once ? something like designing team tag ? as i ofent misses to tag one or other member (though this time i missed to tag any of the designing member) 🤔

Again, not the person who was tagged 🤣 but YES! you can use the tag @Expensify/design to summon us all 😁

@KJ21-ENG

Copy link
Copy Markdown
Contributor Author

Wait, what ? this thing @Expensify/design actually sends you guys notification ? The whole time I was thinking that it does not work simply because when I type it, it doesn't show me suggestions from the dropdown, like it shows for any individual person. 🤣

Thats really cool, @dannymcclain Thanks for the Info It made my work a bit easier to not remember to tag each of you guys individually when I need a design opinion in general. 😃

@ahmedGaber93

Copy link
Copy Markdown
Contributor

The whole time I was thinking that it does not work simply because when I type it, it doesn't show me suggestions from the dropdown, like it shows for any individual person. 🤣

@KJ21-ENG Unfortunately, mentioning teams is not available for contributors.

@KJ21-ENG

Copy link
Copy Markdown
Contributor Author

@KJ21-ENG Unfortunately, mentioning teams is not available for contributors.

Ahh 🫤

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants