Create per diem still appears under Quick action after Per diem feature is disabled by nkdengineer · Pull Request #73073 · Expensify/App

nkdengineer · 2025-10-21T09:02:22Z

Explanation of Change

Fixed Issues

$ #72409
PROPOSAL: #72409 (comment)

Tests

Precondition:

Workspace has per diem rates

Go to staging.new.expensify.com
Go to workspace chat
Create a per diem expense
Go to workspace settings > More features
Disable Per diem
Open FAB
Create per diem will not appear under Quick action after Per diem feature is disabled

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

Screenshots/Videos

Android: Native

Screen.Recording.2025-10-21.at.15.54.30.mov

Android: mWeb Chrome

Screen.Recording.2025-10-21.at.15.47.41.mov

iOS: Native

Screen.Recording.2025-10-21.at.15.55.44.mov

iOS: mWeb Safari

Screen.Recording.2025-10-21.at.15.49.19.mov

MacOS: Chrome / Safari

Screen.Recording.2025-10-21.at.15.39.57.mov

MacOS: Desktop

Screen.Recording.2025-10-21.at.16.01.14.mov

…re is disabled

melvin-bot · 2025-10-21T09:02:33Z

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

codecov · 2025-10-21T09:15:16Z

Codecov Report

❌ Patch coverage is 7.69231% with 12 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/libs/actions/Policy/PerDiem.ts	0.00%	9 Missing ⚠️
src/pages/workspace/WorkspaceMoreFeaturesPage.tsx	0.00%	2 Missing ⚠️
src/libs/QuickActionUtils.ts	50.00%	1 Missing ⚠️

Files with missing lines	Coverage Δ
src/libs/QuickActionUtils.ts	`42.85% <50.00%> (+1.19%)`	⬆️
src/pages/workspace/WorkspaceMoreFeaturesPage.tsx	`0.00% <0.00%> (ø)`
src/libs/actions/Policy/PerDiem.ts	`0.00% <0.00%> (ø)`

... and 14 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

abdulrahuman5196 · 2025-10-21T15:33:41Z

    isReportArchived: boolean | undefined,
    isRestrictedToPreferredPolicy = false,
 ) => {
+    if (quickAction?.action === CONST.QUICK_ACTIONS.PER_DIEM && !quickActionPolicy?.arePerDiemRatesEnabled) {


@nkdengineer Why are we moving this? Didn't your proposal suggest to remove this altogether since the optimistic data is updated, right?

I forgot to mention. I tested the issue when users disable PerDiem on the second device, and BE didn't clear it through Pusher so I think we should add this safe guard here

How is quick action normally added/removed via backend? Do we have separate api call for it? Can we check if we can use the same flow? If not we can add a followup request to fix this in backend as followup as well.

@nkdengineer

Also kindly check on the jest failures

merged main and the jest error was fixed

How is quick action normally added/removed via backend? Do we have separate api call for it? Can we check if we can use the same flow? If not we can add a followup request to fix this in backend as followup as well.

@abdulrahuman5196 quick action is added through some APIs such as RequestMoney, ...

we don't have the specific API to add/remove it, so I think we can request BE change if needed

@JS00001 What do you think here? Should we create followup request for backend? Or is frontend fix fine?

Regardless if we just fix in frontend as well, the issue will not be shown to the user.

Im fine with frontend validation as well, so that we dont ever accidentily get out of sync

abdulrahuman5196 · 2025-11-04T13:52:10Z

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
- 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 there are no new alerts related to the canBeMissing param for useOnyx
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.ts 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: HybridApp

Screen.Recording.2025-11-04.at.7.17.25.PM.mov

Android: mWeb Chrome

Screen.Recording.2025-11-04.at.7.19.17.PM.mov

iOS: HybridApp

Screen.Recording.2025-11-04.at.6.31.05.PM.mov

iOS: mWeb Safari

Screen.Recording.2025-11-04.at.6.32.44.PM.mov

MacOS: Chrome / Safari

Screen.Recording.2025-11-04.at.5.43.46.PM.mov

MacOS: Desktop

Screen.Recording.2025-11-04.at.5.45.51.PM.mov

abdulrahuman5196

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

All yours. @JS00001

🎀 👀 🎀
C+ Reviewed

OSBotify · 2025-11-04T18:35:55Z

✋ 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 · 2025-11-04T21:13:41Z

🚀 Deployed to staging by https://github.com/JS00001 in version: 9.2.44-0 🚀

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

OSBotify · 2025-11-05T20:07:06Z

🚀 Deployed to production by https://github.com/luacmartins in version: 9.2.44-5 🚀

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

dukenv0307 · 2025-12-30T02:32:55Z

    isReportArchived: boolean | undefined,
    isRestrictedToPreferredPolicy = false,
 ) => {
+    if (quickAction?.action === CONST.QUICK_ACTIONS.PER_DIEM && !quickActionPolicy?.arePerDiemRatesEnabled) {


Coming from #76046, we should hide per-diem quick action if there's no rate

Create per diem still appears under Quick action after Per diem featu…

ff72eb1

…re is disabled

melvin-bot Bot assigned nkdengineer Oct 21, 2025

nkdengineer marked this pull request as ready for review October 21, 2025 09:02

nkdengineer requested a review from a team as a code owner October 21, 2025 09:02

melvin-bot Bot requested review from abdulrahuman5196 and removed request for a team October 21, 2025 09:02

abdulrahuman5196 reviewed Oct 21, 2025

View reviewed changes

nkdengineer added 4 commits October 23, 2025 11:52

Merge branch 'main' into fix/72409

7258a38

Merge branch 'main' into fix/72409

a095548

update type

ecb440f

Merge branch 'main' into fix/72409

5df3254

JS00001 requested a review from abdulrahuman5196 November 4, 2025 12:25

abdulrahuman5196 approved these changes Nov 4, 2025

View reviewed changes

melvin-bot Bot requested a review from JS00001 November 4, 2025 13:53

JS00001 approved these changes Nov 4, 2025

View reviewed changes

JS00001 merged commit 7e66bda into Expensify:main Nov 4, 2025
27 of 31 checks passed

OSBotify mentioned this pull request Nov 4, 2025

Deploy Checklist: New Expensify 2025-11-04 #74235

Closed

56 tasks

melvin-bot Bot mentioned this pull request Nov 5, 2025

[Due for payment 2025-11-12] [$250] QAB - Create per diem still appears under Quick action after Per diem feature is disabled #72409

Closed

16 tasks

dukenv0307 reviewed Dec 30, 2025

View reviewed changes

Uh oh!

Conversation

nkdengineer commented Oct 21, 2025

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot Bot commented Oct 21, 2025

Uh oh!

codecov Bot commented Oct 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

abdulrahuman5196 Oct 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

abdulrahuman5196 commented Nov 4, 2025

Reviewer Checklist

Screenshots/Videos

Uh oh!

abdulrahuman5196 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

OSBotify commented Nov 4, 2025

Uh oh!

OSBotify commented Nov 4, 2025

Uh oh!

OSBotify commented Nov 5, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

codecov Bot commented Oct 21, 2025 •

edited

Loading

abdulrahuman5196 Oct 21, 2025 •

edited

Loading