[DEW]: Update SubmitReport API command

[abzokhattab]

Explanation of Change

Add support for Dynamic External Workflow (DEW) in the report submission flow.

Key Changes:

1. No optimistic updates for DEW policies - When submitting on a DEW policy, the app doesn't optimistically update stateNum, statusNum, managerID, or nextStep since the backend determines the actual workflow
2. New pending state tracking - Uses reportMetadata.pendingExpenseAction to track DEW submissions in progress
3. New report action type - DEW_SUBMIT_FAILED for when the backend rejects a DEW submission
4. UI feedback:
   • Shows "queued to submit via custom approval workflow" in LHN when DEW submit is pending
   • Shows error next step when DEW submission fails
   • Shows offline-specific next step message when submitting while offline
5. Beta gated - Behind CONST.BETAS.NEW_DOT_DEW flag

Fixed Issues

$ #75222
PROPOSAL:

Tests

Prerequisites:

• Have a policy with DEW enabled (ask an internal employee)
• Add at least 1 additional member to the policy (so, at least 2 including yourself)

Test 1: Submit Success - Online

1. Create an expense on a DEW-enabled workspace
2. Change the description of the expense to the email address of another policy member
3. Submit the report (while online)
4. Verify:

• "submitted" message appears
• Next step updates to show approver

Test 2: Submit Success - Offline → Online

1. Create an expense on a DEW-enabled workspace
2. Change the description of the expense to the email address of another policy member
3. Go offline (CMD+D → Force offline)
4. Submit the report
5. Verify:

• Shows "queued to submit via custom approval workflow" (greyed out)
• Next step unchanged

6. Go online (disable Force offline)
7. Verify online:

• "queued to submit" replaced with "submitted"
• Next step updates to show approver

Test 3: Submit Failed

1. Create an expense on a DEW-enabled workspace
2. Rename report to "ERROR"
3. Submit the report
4. Verify:

• "failed to submit the report because..." in comments
  RBR in LHN
• Next step: "This report can't be submitted. Please review the comments to resolve"
• Validate that the submit button is still shown and user is able to resubmit .
• Also validate that the report preview displays submit

Offline tests

1. Create an expense on a DEW-enabled workspace
2. Change the description of the expense to the email address of another policy member
3. Go offline (CMD+D → Force offline)
4. Submit the report
5. Verify:

• Shows "queued to submit via custom approval workflow" (greyed out)
• Next step changed to Waiting for you to come back online to determine next steps
• The submit button is removed from the expense.
• The report preview displays view not submit

QA Steps

Same as tests

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 verified there are no new alerts related to the canBeMissing param for useOnyx
• 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 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, 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.2025-11-27.at.00.22.59.mov

Android: mWeb Chrome

Screen.Recording.2025-11-26.at.23.46.27.mov

iOS: Native

Screen.Recording.2025-11-26.at.23.34.28.mov

iOS: mWeb Safari

Screen.Recording.2025-11-26.at.23.36.50.mov

MacOS: Chrome / Safari

Screen.Recording.2025-11-26.at.23.13.16.mov

Screen.Recording.2025-11-26.at.23.23.00.mov

Screen.Recording.2025-11-26.at.23.30.08.mov

Screen.Recording.2025-12-02.at.21.18.46.mov

[melvin-bot]

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

[codecov]

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/CONST/index.ts	83.47% <ø> (ø)
src/components/LHNOptionsList/LHNOptionsList.tsx	87.50% <100.00%> (+0.15%)	⬆️
...m/TransactionPreview/TransactionPreviewContent.tsx	76.59% <100.00%> (-0.25%)	⬇️
src/components/Search/SearchList/index.tsx	3.44% <ø> (ø)
src/components/Search/index.tsx	34.06% <100.00%> (+0.32%)	⬆️
...stWithSections/Search/TransactionGroupListItem.tsx	71.42% <ø> (ø)
src/libs/OptionsListUtils/index.ts	73.07% <100.00%> (+0.13%)	⬆️
src/libs/ReportPreviewActionUtils.ts	91.34% <100.00%> (+0.16%)	⬆️
src/libs/ReportUtils.ts	73.10% <100.00%> (-0.04%)	⬇️
src/pages/home/report/ReportActionItem.tsx	100.00% <100.00%> (ø)
... and 17 more
... and 26 files with indirect coverage changes

[abzokhattab]

translation confirmation was requested here: https://expensify.slack.com/archives/C01GTK53T8Q/p1763725986769179

[bernhardoj]

LGTM, other than the offline case. The queued message is still shown when going online, but I think if we really want to fix this, we should first remove the Onyx.connect usage for the last action and then revisit this, but that's for another issue.

web.offline.mp4

We can merge this for now.

[francoisl]

Let's do this!!

[francoisl]

Hmm Github is telling me some commits are not signed, so it won't let me merge because they're required at the repo level. The GH UI isn't loading all commit details on the /commits page, I'll check on the command line.

[francoisl]

Those are the unsigned commits it looks like:

❯ git log --format="%H %G? %s" main..HEAD | grep ' N '
c1a38a0cd04baed162d71aa9f39f0d69afab8e4c N Refactoring test cases
b85993e30c7c8e3445f621bdd1fee994ed50ad7d N making err as next step instead of next step status
3261d5592d186a53adcdaf05fd488e05f4e781c6 N remvoe the unneeded hasDewError const

[OSBotify]

✋ 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]

🚀 Deployed to staging by https://github.com/francoisl in version: 9.2.95-0 🚀

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

[izarutskaya]

Hi @abzokhattab We can use our Expensifail accounts for testing this PR and no need special settings in a Workspace, right?

Create an expense on a DEW-enabled workspace

[francoisl]

Can you tell me what account you're testing from? I'll need to enable something on that account first.

[izarutskaya]

@francoisl There are accounts for testing the PR:

• applausetester+piyozx@applause.expensifail.com
• applausetester+rg_46@applause.expensifail.com
• applausetester+ndk80@applause.expensifail.com

[izarutskaya]

Let me know when it's done. Thank you in advance

[francoisl]

Ok I enabled it on these policies so you should be able to test with those:

Policy name	ID	Owner
Applause's Workspace	08C0123EE122C260	applausetester+piyozx@applause.expensifail.com
Jujutsu Workspace	0C441392C1B6885C	applausetester+rg_46@applause.expensifail.com

It doesn't look like the account applausetester+ndk80@applause.expensifail.com exists though. Let me know if you need to use any other account

[izarutskaya]

@francoisl Could you please enable it in this account applausetester+ndk74@applause.expensifail.com as well? Thank you

[francoisl]

Done! (policy 4DF895B89CD9CF90)

[OSBotify]

🚀 Deployed to production by https://github.com/arosiclair in version: 9.2.95-5 🚀

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