Skip to content

Set "Delayed submission" to "Manually" by default on new Workspaces#57676

Merged
dangrous merged 18 commits into
Expensify:mainfrom
twilight2294:delayedSubmission
Mar 26, 2025
Merged

Set "Delayed submission" to "Manually" by default on new Workspaces#57676
dangrous merged 18 commits into
Expensify:mainfrom
twilight2294:delayedSubmission

Conversation

@twilight2294

@twilight2294 twilight2294 commented Mar 3, 2025

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixed Issues

$ #56367
PROPOSAL: #56367 (comment)

Tests

Same as QA

  • Verify that no errors appear in the JS console

Offline tests

Same as QA

QA Steps

Test 1:

  1. Sign up as a new user
  2. Choose "Manage my team's expenses" (This create a new Workspace)
  3. Open workspace settings
  4. Open the Workflow tab
    Verify that Set "Delayed submission" is set to Manually

Test 2:

  1. As account A, send an expense to account B (Brand new account with no workspaces)
  2. As Account B go to pay the expense with a business bank account

Verify that Set "Delayed submission" is set to Manually when workspace is created

  • 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
    • MacOS: Desktop
  • 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 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
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • 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 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)
  • 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.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • 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.
  • 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_20250309_170645.mp4
Android: mWeb Chrome
Screen_recording_20250309_170331.mp4
iOS: Native
Simulator.Screen.Recording.-.Expensify.testing.-.2025-03-09.at.17.04.17.mp4
iOS: mWeb Safari
Simulator.Screen.Recording.-.Expensify.testing.-.2025-03-09.at.17.05.49.mp4
MacOS: Chrome / Safari
Screen.Recording.2025-03-09.at.4.58.12.PM.mov
MacOS: Desktop
Screen.Recording.2025-03-09.at.5.02.11.PM.mov

@twilight2294 twilight2294 requested a review from a team as a code owner March 3, 2025 13:18
@melvin-bot melvin-bot Bot requested a review from abdulrahuman5196 March 3, 2025 13:19
@melvin-bot

melvin-bot Bot commented Mar 3, 2025

Copy link
Copy Markdown

@abdulrahuman5196 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 March 3, 2025 13:19
@twilight2294

Copy link
Copy Markdown
Contributor Author

@abdulrahuman5196 please review this one, i will upload videos shortly

@dangrous

dangrous commented Mar 5, 2025

Copy link
Copy Markdown
Contributor

bump on review please @abdulrahuman5196 thank you!

Comment thread src/libs/actions/Policy/Policy.ts Outdated
Comment thread tests/actions/PolicyTest.ts Outdated
Comment thread tests/actions/PolicyTest.ts Outdated
Comment thread src/libs/actions/Policy/Policy.ts Outdated
Comment thread src/libs/actions/Policy/Policy.ts Outdated
@abdulrahuman5196

Copy link
Copy Markdown
Contributor

Hi, Checking today. Sorry for delay

@dangrous

Copy link
Copy Markdown
Contributor

bumping this, thanks!

@abdulrahuman5196

Copy link
Copy Markdown
Contributor

Checking now.

@abdulrahuman5196

Copy link
Copy Markdown
Contributor

@twilight2294 I don't see any tests added or updated. Can we add/update tests similar to #50391 ?

@twilight2294

Copy link
Copy Markdown
Contributor Author

I was OoO most of last week, working on it today!

@abdulrahuman5196

Copy link
Copy Markdown
Contributor

Hi @twilight2294 , kindly let us know once tests are added. I can review again

@twilight2294

Copy link
Copy Markdown
Contributor Author

@abdulrahuman5196 I updated please check

@dangrous

Copy link
Copy Markdown
Contributor

@twilight2294 did you add unit tests as well? If so, maybe they didn't get pushed? I only see the updates to the testing steps in the PR description. We can update PolicyTest in order to confirm these settings.

Thanks!

@dangrous

Copy link
Copy Markdown
Contributor

bump @twilight2294 thanks!

@abdulrahuman5196

Copy link
Copy Markdown
Contributor

@twilight2294 did you add unit tests as well? If so, maybe they didn't get pushed? I only see the updates to the testing steps in the PR description. We can update PolicyTest in order to confirm these settings.

Thanks!

Gentle ping

@twilight2294 twilight2294 left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@abdulrahuman5196 all yours

callback: (value) => (allTransactionViolations = value),
});

let introSelected: OnyxEntry<IntroSelected>;

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Had to move this Up to make use of it in createDraftInitialWorkspace

approvalMode: CONST.RED_BRICK_ROAD_PENDING_ACTION.ADD,
reimbursementChoice: CONST.RED_BRICK_ROAD_PENDING_ACTION.ADD,
},
areWorkflowsEnabled: shouldEnableWorkflowsByDefault,

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@dangrous @abdulrahuman5196 The PR #50391 missed to add areWorkflowsEnabled I updated it in our PR.

Comment thread tests/actions/IOUTest.ts
createWorkspace(CARLOS_EMAIL, true, "Carlos's Workspace");
const policyID = generatePolicyID();
createWorkspace(CARLOS_EMAIL, true, "Carlos's Workspace", policyID);
setWorkspaceAutoReportingFrequency(policyID, CONST.POLICY.AUTO_REPORTING_FREQUENCIES.INSTANT);

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

The test was for correctly submits a report with Submit and Close approval mode, so had to change the mode here

Comment thread tests/actions/IOUTest.ts
Comment on lines +3838 to +3839
createWorkspace(CARLOS_EMAIL, true, "Carlos's Workspace", policyID);
setWorkspaceAutoReportingFrequency(policyID, CONST.POLICY.AUTO_REPORTING_FREQUENCIES.INSTANT);

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

same as ^

expect(onboarding?.hasCompletedGuidedSetupFlow).toBeTruthy();
});

it('create a new workspace with delayed submission set to manually if the onboarding choice is newDotManageTeam or newDotLookingAround', async () => {

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This is the new test we added for our changes

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I don't think we need a similar case for Looking around, but let me know if we need that too, it's not a big change, so i didn't add it here

@danielrvidal

Copy link
Copy Markdown
Contributor

Awesome, so this should be deployed this week, right?

@dangrous

Copy link
Copy Markdown
Contributor

Should be! @abdulrahuman5196 can you give this its final review so we can keep it moving forward? thank you!

workspaceName,
);

const shouldEnableWorkflowsByDefault =

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.

nit: It would be good to move this to a common function to avoid duplicate code.
But for now i am fine if this PR is required urgently @dangrous

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.

yeah I think that's okay for now!

@abdulrahuman5196

Copy link
Copy Markdown
Contributor

Checking now

@abdulrahuman5196

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 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.
  • 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: Native
Screen.Recording.2025-03-27.at.12.50.41.AM.mp4
Android: mWeb Chrome
Screen.Recording.2025-03-27.at.12.31.23.AM.mp4
iOS: Native
iOS: mWeb Safari
Screen.Recording.2025-03-27.at.12.28.20.AM.mp4
MacOS: Chrome / Safari
Screen.Recording.2025-03-27.at.12.13.13.AM.mp4
MacOS: Desktop
Screen.Recording.2025-03-27.at.12.17.43.AM.mp4

@abdulrahuman5196

Copy link
Copy Markdown
Contributor

Hi, I am having trouble in building ios native application alone. But tested in all other platforms and the code looks good as well. So i think it should be fine.

@abdulrahuman5196 abdulrahuman5196 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.

Changes looks good and works well. Reviewers checklist is also complete.

All yours. @dangrous

🎀 👀 🎀
C+ Reviewed

@melvin-bot melvin-bot Bot requested a review from dangrous March 26, 2025 19:26

@dangrous dangrous 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.

I'm going to go ahead and merge this for expediency, but I'd love a quick follow up just adding two things to the tests:

  • Making sure the settings are set appropriately with no intro choice
  • Checking the workflows enabled and harvesting enabled as well as the autoreporting frequency

@dangrous dangrous merged commit 69f2b25 into Expensify:main Mar 26, 2025
@OSBotify

Copy link
Copy Markdown
Contributor

✋ 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

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/dangrous in version: 9.1.20-0 🚀

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

@dangrous

Copy link
Copy Markdown
Contributor

I'm going to go ahead and merge this for expediency, but I'd love a quick follow up just adding two things to the tests:

  • Making sure the settings are set appropriately with no intro choice
  • Checking the workflows enabled and harvesting enabled as well as the autoreporting frequency

Bumping this when y'all have a chance to do the followup @twilight2294, thank you!

@twilight2294

Copy link
Copy Markdown
Contributor Author

Will work on this today

@github-actions

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.1.20-2 🚀

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

@twilight2294

Copy link
Copy Markdown
Contributor Author

@dangrous @abdulrahuman5196 follow up PR is here: #59579

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.

5 participants