Skip to content

[Home page] [Release 4] Adding time sensitive actions for broken connections#80974

Merged
grgia merged 22 commits intomainfrom
vit-homePageRelease4
Feb 4, 2026
Merged

[Home page] [Release 4] Adding time sensitive actions for broken connections#80974
grgia merged 22 commits intomainfrom
vit-homePageRelease4

Conversation

@mountiny
Copy link
Contributor

@mountiny mountiny commented Jan 30, 2026

Explanation of Change

This PR implements Release 4 of the NewDot Home page Time Sensitive section, adding two new widgets:

  1. Fix Company Card Connection - Shows when an admin has a workspace with broken company card connections (import errors)
  2. Fix Accounting Connection - Shows when an admin has a workspace with broken/stale accounting integrations (QuickBooks, Xero, NetSuite, etc.)

Key changes:

  • Added FixCompanyCardConnection widget component that displays broken company card connections with a "Fix" CTA navigating to workspace company cards settings
  • Added FixAccountingConnection widget component that displays broken accounting connections with a "Fix" CTA navigating to workspace accounting settings
  • Updated BaseWidgetItem to support isDanger prop for danger-styled (coral) buttons
  • Added selector using activeAdminPoliciesSelector to filter policies where the user is an admin
  • Used existing useCardFeedErrors hook and hasSynchronizationErrorMessage function to detect broken connections
  • Each broken connection/workspace shows as a separate row in the Time Sensitive section

Priority order (from design doc):

  • Potential card fraud (Release 3)
  • Broken company card connections ← Added in this PR
  • Broken accounting connections ← Added in this PR
  • Early adoption discount (50% or 25%)
  • Expensify card shipping (Release 3)
  • Expensify card activation (Release 3)

Fixed Issues

$ #79970
PROPOSAL:

Tests

Prerequisite: Have a workspace with accounting integration set up

  1. Break the accounting integration connection
  2. Verify that you can see the Fix option on the home page as the admin
  3. Sign in as a member on that workspace
  4. Verify you do not see that time-sensitive widget
  5. As admin, click the Fix
  6. Verify you had been navigated to the Accounting page in the workspace settings
image
  1. Log in as an admin of a workspace that has a broken accounting connection (e.g., QuickBooks with sync error)
  2. Navigate to the Home page
  3. Verify the "Time sensitive" section appears with a "Fix [Integration Name] connection" widget
  4. Verify the widget shows "Workspace > Connections" subtitle
  5. Verify the icon has a coral/salmon background color
  6. Verify the "Fix" button is coral colored (not green)
  7. Click "Fix" and verify it navigates to the workspace accounting settings page
  8. Repeat steps 1-7 for a workspace with a broken company card connection
  9. Verify company card widget shows "Workspace > Company cards" subtitle and navigates correctly
  10. Verify that if multiple broken connections exist across workspaces, each shows as a separate row
  • Verify that no errors appear in the JS console
image

Offline tests

N/A

QA Steps

  1. Log in as an admin of a workspace with a broken accounting integration
  2. Navigate to Home page
  3. Verify "Time sensitive" section shows the broken connection widget with coral styling
  4. Tap "Fix" and verify navigation to workspace accounting settings
  5. Repeat for broken company card connections
  6. Verify multiple broken connections show as separate rows

// TODO: These must be filled out, or the issue title must include "[No QA]."

  • 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 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.
  • I verified that similar component doesn't exist in the codebase
  • I verified that all props are defined accurately and each prop has a /** comment above it */
  • I verified that each file is named correctly
  • I verified that each component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • I verified that the only data being stored in component state is data necessary for rendering and nothing else
  • In component if we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
  • 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)
  • I verified that component 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)
  • I verified that all JSX used for rendering exists in the render method
  • I verified that each 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

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

@mountiny mountiny self-assigned this Jan 30, 2026
@OSBotify

This comment has been minimized.

@OSBotify

This comment has been minimized.

@OSBotify

This comment has been minimized.

@codecov
Copy link

codecov bot commented Jan 30, 2026

@OSBotify

This comment has been minimized.

@github-actions
Copy link
Contributor

🚧 @mountiny has triggered a test Expensify/App build. You can view the workflow run here.


function FixAccountingConnection({connectionName, policyID}: FixAccountingConnectionProps) {
const {translate} = useLocalize();
const icons = useMemoizedLazyExpensifyIcons(['Exclamation'] as const);
Copy link
Contributor

Choose a reason for hiding this comment

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

I suppose it should work without as const


function FixCompanyCardConnection({card, policyID}: FixCompanyCardConnectionProps) {
const {translate} = useLocalize();
const icons = useMemoizedLazyExpensifyIcons(['Connect'] as const);
Copy link
Contributor

@ZhenjaHorbach ZhenjaHorbach Jan 30, 2026

Choose a reason for hiding this comment

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

It should work without as const

@github-actions

This comment has been minimized.

if (!shouldShowDiscount || !discountInfo) {
return null;
// Determine which offer to show based on discount type (they are mutually exclusive)
const shouldShow50off = shouldShowDiscount && discountInfo?.discountType === 50;
Copy link
Contributor

@ZhenjaHorbach ZhenjaHorbach Jan 30, 2026

Choose a reason for hiding this comment

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

It's better to wait until we merge this PR
And then use useTimeSensitiveOffers here

@OSBotify

This comment has been minimized.

@mountiny mountiny requested a review from grgia January 30, 2026 20:28
@mountiny mountiny marked this pull request as ready for review January 30, 2026 20:28
@mountiny mountiny requested review from a team as code owners January 30, 2026 20:28
@melvin-bot melvin-bot bot requested a review from ZhenjaHorbach January 30, 2026 20:28
@mountiny
Copy link
Contributor Author

mountiny commented Feb 4, 2026

I will clean this one up tomorrow

@OSBotify
Copy link
Contributor

OSBotify commented Feb 4, 2026

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index 787f3d3e..3335a4d8 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -1003,6 +1003,12 @@ const translations: TranslationDeepObject<typeof en> = {
                 subtitle: 'Validieren Sie Ihre Karte und beginnen Sie mit dem Ausgeben.',
                 cta: 'Aktivieren',
             },
+            ctaFix: 'Beheben',
+            fixCompanyCardConnection: {
+                title: ({feedName}: {feedName: string}) => (feedName ? `${feedName}-Firmenkartenverbindung reparieren` : 'Firmenkarte reparieren Verbindung der Firmenkarte reparieren'),
+                subtitle: 'Workspace > Unternehmenskarten',
+            },
+            fixAccountingConnection: {title: ({integrationName}: {integrationName: string}) => `${integrationName}-Verbindung reparieren`, subtitle: 'Arbeitsbereich > Buchhaltung'},
         },
         announcements: 'Ankündigungen',
         discoverSection: {
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index b172705b..a3e49b9e 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -1007,6 +1007,12 @@ const translations: TranslationDeepObject<typeof en> = {
                 subtitle: 'Validez votre carte et commencez à dépenser.',
                 cta: 'Activer',
             },
+            ctaFix: 'Corriger',
+            fixCompanyCardConnection: {
+                title: ({feedName}: {feedName: string}) => (feedName ? `Corriger la connexion de la carte d'entreprise ${feedName}` : 'Corriger la connexion de la carte entreprise'),
+                subtitle: 'Espace de travail > Cartes d’entreprise',
+            },
+            fixAccountingConnection: {title: ({integrationName}: {integrationName: string}) => `Corriger la connexion ${integrationName}`, subtitle: 'Espace de travail > Comptabilité'},
         },
         announcements: 'Annonces',
         discoverSection: {
diff --git a/src/languages/it.ts b/src/languages/it.ts
index a2500c32..34345038 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -1002,6 +1002,12 @@ const translations: TranslationDeepObject<typeof en> = {
                 subtitle: 'Convalida la tua carta e inizia a spendere.',
                 cta: 'Attiva',
             },
+            ctaFix: 'Correggi',
+            fixCompanyCardConnection: {
+                title: ({feedName}: {feedName: string}) => (feedName ? `Correggi la connessione della carta aziendale ${feedName}` : 'Correggi connessione carta aziendale'),
+                subtitle: 'Spazio di lavoro > Carte aziendali',
+            },
+            fixAccountingConnection: {title: ({integrationName}: {integrationName: string}) => `Correggi connessione ${integrationName}`, subtitle: 'Spazio di lavoro > Contabilità'},
         },
         announcements: 'Annunci',
         discoverSection: {
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 5aae4900..fdde2c04 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -998,6 +998,12 @@ const translations: TranslationDeepObject<typeof en> = {
                 subtitle: 'カードを認証して支出を始めましょう。',
                 cta: '有効化',
             },
+            ctaFix: '修正',
+            fixCompanyCardConnection: {
+                title: ({feedName}: {feedName: string}) => (feedName ? `${feedName} 会社カード接続を修正` : '法人クレジットカードの接続を修正'),
+                subtitle: 'ワークスペース > 会社カード',
+            },
+            fixAccountingConnection: {title: ({integrationName}: {integrationName: string}) => `${integrationName} 接続を修正`, subtitle: 'ワークスペース > 会計'},
         },
         announcements: 'お知らせ',
         discoverSection: {
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 428e4147..689897ce 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -1002,6 +1002,12 @@ const translations: TranslationDeepObject<typeof en> = {
                 subtitle: 'Valideer je kaart en begin met uitgeven.',
                 cta: 'Activeren',
             },
+            ctaFix: 'Repareren',
+            fixCompanyCardConnection: {
+                title: ({feedName}: {feedName: string}) => (feedName ? `Verbinding bedrijfskaart ${feedName} herstellen` : 'Verbinding van bedrijfskaart repareren'),
+                subtitle: 'Werkruimte > Bedrijfspassen',
+            },
+            fixAccountingConnection: {title: ({integrationName}: {integrationName: string}) => `Verbinding met ${integrationName} repareren`, subtitle: 'Werkruimte > Boekhouding'},
         },
         announcements: 'Aankondigingen',
         discoverSection: {
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index c32c6bfb..90e2f135 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -1003,6 +1003,12 @@ const translations: TranslationDeepObject<typeof en> = {
                 subtitle: 'Zatwierdź swoją kartę i zacznij wydawać.',
                 cta: 'Aktywuj',
             },
+            ctaFix: 'Napraw',
+            fixCompanyCardConnection: {
+                title: ({feedName}: {feedName: string}) => (feedName ? `Napraw połączenie karty firmowej ${feedName}` : 'Napraw połączenie karty firmowej'),
+                subtitle: 'Workspace > Karty firmowe',
+            },
+            fixAccountingConnection: {title: ({integrationName}: {integrationName: string}) => `Napraw połączenie ${integrationName}`, subtitle: 'Przestrzeń robocza > Księgowość'},
         },
         announcements: 'Ogłoszenia',
         discoverSection: {
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 8247dec9..c2d534ce 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -1001,6 +1001,12 @@ const translations: TranslationDeepObject<typeof en> = {
                 subtitle: 'Valide seu cartão e comece a gastar.',
                 cta: 'Ativar',
             },
+            ctaFix: 'Corrigir',
+            fixCompanyCardConnection: {
+                title: ({feedName}: {feedName: string}) => (feedName ? `Corrigir conexão do cartão corporativo ${feedName}` : 'Corrigir conexão do cartão corporativo'),
+                subtitle: 'Área de trabalho > Cartões corporativos',
+            },
+            fixAccountingConnection: {title: ({integrationName}: {integrationName: string}) => `Corrigir conexão com ${integrationName}`, subtitle: 'Espaço de trabalho > Contabilidade'},
         },
         announcements: 'Comunicados',
         discoverSection: {
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index c01f95fd..a606697c 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -988,6 +988,9 @@ const translations: TranslationDeepObject<typeof en> = {
                 subtitle: '验证您的银行卡并开始消费。',
                 cta: '启用',
             },
+            ctaFix: '修复',
+            fixCompanyCardConnection: {title: ({feedName}: {feedName: string}) => (feedName ? `修复 ${feedName} 公司卡连接` : '修复公司卡连接'), subtitle: '工作区 > 公司卡片'},
+            fixAccountingConnection: {title: ({integrationName}: {integrationName: string}) => `修复 ${integrationName} 连接`, subtitle: '工作区 > 会计'},
         },
         announcements: '公告',
         discoverSection: {

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

Add buttonProps={{success: true}} to BaseWidgetItem in ForYouSection
to make the CTA buttons green, consistent with the TimeSensitiveSection
styling approach.
@mountiny mountiny requested a review from grgia February 4, 2026 06:48
@mountiny
Copy link
Contributor Author

mountiny commented Feb 4, 2026

@grgia shoul dbe ready

@github-actions
Copy link
Contributor

github-actions bot commented Feb 4, 2026

🚧 @grgia has triggered a test Expensify/App build. You can view the workflow run here.

@grgia grgia merged commit 55d15db into main Feb 4, 2026
34 checks passed
@grgia grgia deleted the vit-homePageRelease4 branch February 4, 2026 16:39
@github-actions
Copy link
Contributor

github-actions bot commented Feb 4, 2026

🚧 @grgia has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify
Copy link
Contributor

OSBotify commented Feb 4, 2026

✋ 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
Copy link
Contributor

OSBotify commented Feb 5, 2026

🚀 Deployed to staging by https://github.com/grgia in version: 9.3.13-1 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Feb 5, 2026

🚀 Deployed to staging by https://github.com/grgia in version: 9.3.15-0 🚀

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

@IuliiaHerets
Copy link

Hi @mountiny. How can we trigger the broken company card connection on the Home section?
We can trigger a broken connection on the Expense report page using the command from PR 74093, but it will disappear when we refresh or move to another section.

bandicam.2026-02-06.13-03-31-319.mp4

@mountiny
Copy link
Contributor Author

mountiny commented Feb 7, 2026

Hi @mountiny. How can we trigger the broken company card connection on the Home section?
We can trigger a broken connection on the Expense report page using the command from PR #74093, but it will disappear when we refresh or move to another section

I am not sure how QA can do that, maybe we could do InternalQA here @joekaufmanexpensify

@IuliiaHerets
Copy link

@mountiny We tested the broken accounting integration, and it passed.

@joekaufmanexpensify
Copy link
Contributor

Tested broken card connection, error looks good on home and confirmed the Fix button goes to the Company cards page on the workspace with the broken feed

@joekaufmanexpensify
Copy link
Contributor

checked it off on QA 👍

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/lakchote in version: 9.3.15-10 🚀

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

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.

10 participants