fix: don't show DEW approve error next step for auto-approval failures

[abzokhattab]

Explanation of Change

Restores the automaticAction check for DEW approve failure next steps that was accidentally removed in #79165. When DEW blocks auto-approval (DEW_APPROVE_FAILED with automaticAction: true), the report should keep the normal workflow next step (e.g. "Waiting for A to approve the report"). The red error next step should only appear for manual approval failures (automaticAction: false) when the current user is the approver.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/652010
PROPOSAL:

Tests

Prerequisites for all tests:

• Have a policy with DEW enabled (ask an internal employee)
• Add at least 2 additional approver members (A and B) to the policy
• Create a report
  • Create a new expense that contains the email address of user A as a description
  • Create a new expense that contains the email address of user B as a description

Test 1: Manual approve failed (regression check)

1. Rename report to "APPROVE_ERROR"
2. Submit the report
3. Verify report gets submitted to A
4. Sign in as user A, open the report
5. Click the Approve button
6. Verify:
   • "failed to approve the report because..." appears in comments
   • Next step: "This report can't be approved. Please review the comments to resolve"
   • Approve button is still shown and user is able to re-approve

Test 2: Auto-approve failed

1. Edit policy settings:
   • Enable "Auto-approve compliant reports" in the workflows page
   • Change audit rate to 0%
2. Create an expense on a DEW-enabled workspace (ensure total < $100 auto-approve limit)
3. Change the description of the expense to the email address of user A
4. Rename report to "AUTOAPPROVE_ERROR"
5. Submit the report
6. Verify:
   • Next step changes to "waiting for A to approve the report"
   • Report actions show:
     • " submitted"
     • " report routed to A due to custom approval workflow"
     • " failed to approve via [workspace rules] because..."

• Verify that no errors appear in the JS console

Offline tests

Same as tests

QA Steps

Same as tests

• 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 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, 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.
• 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

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[melvin-bot]

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

[Eskalifer1]

Hi! I will review it in a couple of hours 😃

[abzokhattab]

its not ready for review yet sorry ... i am not sure if c+ is needed .. need to confirm with @sakluger