Skip to content

Conversation

@cosmicvulpes
Copy link
Contributor

@cosmicvulpes cosmicvulpes commented Dec 24, 2025

Explanation of Change

This PR adds support for displaying report-level actions (Submit, Approve, Pay) in the selected transactions dropdown when all expenses in a report are selected. This allows users to perform bulk report actions directly from the expense selection UI.

Key Changes

  • Report-level actions in selected transactions dropdown: When all expenses in a report are selected, the dropdown now shows report-level actions (Submit, Approve, Pay) alongside transaction-level actions (Hold, Move, Delete, etc.)
  • useSelectedTransactionsActions hook enhancement: Added reportLevelActions parameter to inject report-level actions into the dropdown options
  • MoneyReportHeader integration: Passes applicable report actions (from applicableTransactionActions) to the selected transactions dropdown via useSelectedTransactionsActions
  • Payment callback refactor: Refactored SettlementButton.onPress to use object params (PaymentActionParams) to support the skipAnimation parameter needed when triggering payments from the selected transactions dropdown

Fixed Issues

$ #72502
PROPOSAL: #72502 (comment)

Tests

  1. Create and open an expense report with multiple expenses
  2. Select all expenses using the checkbox
  3. Verify that Submit/Approve/Pay actions appear at the top of the selection dropdown (depending on report state)
  4. Click the Submit action (if available) and verify the report is submitted and selections are cleared
  5. Select all expenses again
  6. Click the Approve action (if available) and verify the report is approved and selections are cleared
  7. Select all expenses again
  8. Click the Pay action and verify a submenu opens with payment options (Pay as business, Mark as paid, etc.)
  9. Select a payment option and verify the payment is processed and selections are cleared
  10. Verify nested payment options work correctly for invoice reports with bank account selection
  • Verify that no errors appear in the JS console

Offline tests

  1. Go offline
  2. Select all expenses on a report
  3. Verify report-level actions (Submit/Approve/Pay) are shown in the dropdown
  4. Click Submit/Approve and verify appropriate offline behavior
  5. Click Pay and verify payment options are shown and verify appropriate offline behavior

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
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Screen.Recording.2025-12-24.at.5.21.59.PM.mp4

- Fix type import in useSelectedTransactionsActions.ts (use 'import type')
- Remove unused KYCPaymentMethod import in PaymentUtils.ts
- Add ValueOf import and type assertion in ActionCell.tsx for PaymentData compatibility
- Update SettlementButton to use object params for all onPress calls
@cosmicvulpes cosmicvulpes requested review from a team as code owners December 24, 2025 11:48
@melvin-bot melvin-bot bot requested review from flaviadefaria, heyjennahay and situchan and removed request for a team December 24, 2025 11:48
@melvin-bot
Copy link

melvin-bot bot commented Dec 24, 2025

@situchan 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 requested review from JmillsExpensify, joekaufmanexpensify and trjExpensify and removed request for a team December 24, 2025 11:48
<Button
success
onPress={confirmApproval}
onPress={() => confirmApproval()}
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ PERF-4 (docs)

Creating inline arrow functions as props causes unnecessary re-renders because a new function reference is created on every render. React uses referential equality to determine if props changed, so even if the logic is identical, the new function instance triggers re-renders of child components.

Wrap this function in useCallback to preserve referential stability:

const handleConfirmApproval = useCallback(() => confirmApproval(), [confirmApproval]);

// Then use it in the Button:
onPress={handleConfirmApproval}

Note: For this to be fully effective, confirmApproval itself should also be wrapped in useCallback.

value: CONST.REPORT.SECONDARY_ACTIONS.APPROVE,
sentryLabel: CONST.SENTRY_LABEL.MORE_MENU.APPROVE,
onSelected: confirmApproval,
onSelected: () => confirmApproval(true),
Copy link
Contributor

Choose a reason for hiding this comment

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

❌ PERF-4 (docs)

Creating inline arrow functions in object literals that are recreated on every render causes unnecessary recomputations of dependent values. The secondaryActionsImplementation object is recreated on every render, and since applicableTransactionActions depends on it via useMemo, it will also be recreated, defeating the purpose of memoization.

To fix this, wrap secondaryActionsImplementation in useMemo or extract stable callback references:

const handleApproveWithSkipAnimation = useCallback(() => confirmApproval(true), [confirmApproval]);

// Then use in the object:
[CONST.REPORT.SECONDARY_ACTIONS.APPROVE]: {
    text: translate(iou.approve),
    icon: expensifyIcons.ThumbsUp,
    value: CONST.REPORT.SECONDARY_ACTIONS.APPROVE,
    sentryLabel: CONST.SENTRY_LABEL.MORE_MENU.APPROVE,
    onSelected: handleApproveWithSkipAnimation,
}

Alternatively, wrap the entire secondaryActionsImplementation object in useMemo with appropriate dependencies.

@codecov
Copy link

codecov bot commented Dec 24, 2025

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/hooks/useSelectedTransactionsActions.ts 81.39% <50.00%> (-0.37%) ⬇️
src/libs/PaymentUtils.ts 27.05% <0.00%> (ø)
src/components/MoneyReportHeaderKYCDropdown.tsx 0.00% <0.00%> (ø)
...ts/SelectionListWithSections/Search/ActionCell.tsx 56.25% <33.33%> (+1.14%) ⬆️
src/hooks/usePaymentOptions.ts 0.00% <0.00%> (ø)
...ReportPreview/MoneyRequestReportPreviewContent.tsx 60.06% <0.00%> (ø)
src/components/SettlementButton/index.tsx 0.00% <0.00%> (ø)
src/components/MoneyReportHeader.tsx 0.00% <0.00%> (ø)
... and 7 files with indirect coverage changes

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.

1 participant