Skip to content

[No QA] [HR Import] Show "You must disconnect first" modal #91415

Merged
grgia merged 5 commits into
Expensify:mainfrom
software-mansion-labs:feat/merge-hr-you-must-disconnect-first
May 22, 2026
Merged

[No QA] [HR Import] Show "You must disconnect first" modal #91415
grgia merged 5 commits into
Expensify:mainfrom
software-mansion-labs:feat/merge-hr-you-must-disconnect-first

Conversation

@jmusial
Copy link
Copy Markdown
Contributor

@jmusial jmusial commented May 22, 2026

Explanation of Change

This PR prevents user from entering new connection flow when there is an existing connection, prompting them to disconnect first.

Fixed Issues

$ #91401
PROPOSAL:

Tests

Prerequisites:

  1. Have an existing connection HR connection in a workspace
  2. Open "Other" and click connect on one of the other providers
  3. Verify that informative modal appears.

Offline tests

Same as tests

QA Steps

n/A

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 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 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
amdroid.mov
MacOS: Chrome / Safari
Screen.Recording.2026-05-22.at.15.02.11.mov

@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 22, 2026

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

@jmusial jmusial force-pushed the feat/merge-hr-you-must-disconnect-first branch from 3ac74a9 to c0240f2 Compare May 22, 2026 13:00
@OSBotify

This comment has been minimized.

@jmusial jmusial force-pushed the feat/merge-hr-you-must-disconnect-first branch from c0240f2 to 6d20aaf Compare May 22, 2026 13:04
@jmusial jmusial marked this pull request as ready for review May 22, 2026 13:20
@jmusial jmusial requested review from a team as code owners May 22, 2026 13:20
@melvin-bot melvin-bot Bot requested review from flaviadefaria and nyomanjyotisa and removed request for a team May 22, 2026 13:20
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 22, 2026

@nyomanjyotisa 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
Copy link
Copy Markdown

codecov Bot commented May 22, 2026

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/styles/variables.ts 100.00% <ø> (ø)
...s/workspace/rules/SpendRules/SpendRulesSection.tsx 0.00% <0.00%> (ø)
src/pages/workspace/hr/WorkspaceHRPage.tsx 0.00% <0.00%> (ø)
... and 66 files with indirect coverage changes

dannymcclain
dannymcclain previously approved these changes May 22, 2026
Copy link
Copy Markdown
Contributor

@dannymcclain dannymcclain left a comment

Choose a reason for hiding this comment

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

Video looks good to me 👍 (this is a visual/design review only!)

@grgia grgia requested review from bernhardoj, cristipaval, grgia and twisterdotcom and removed request for flaviadefaria and nyomanjyotisa May 22, 2026 13:43
Comment thread src/styles/variables.ts Outdated
Comment on lines +269 to +272
holdEducationModalWidth: 400,
changePolicyEducationModalWidth: 400,
builtInProtectionModalWidth: 400,
hrAlreadyConnectedModalWidth: 400,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@jmusial all these modals are the same size, maybe time for a standardization

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Well, only the last 2 ones are for confirm modals, others are education, so I would't join them together. Can unify the 2

Comment thread src/languages/en.ts Outdated
disconnect: 'Disconnect',
disconnectTitle: (providerName: string) => `Disconnect ${providerName}`,
disconnectPrompt: (providerName: string) => `Are you sure you want to disconnect ${providerName}?`,
alreadyConnectedTitle: 'Cannot connect to multiple HR platform',
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
alreadyConnectedTitle: 'Cannot connect to multiple HR platform',
alreadyConnectedTitle: 'Cannot connect to multiple HR platforms',

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@jmusial SkRrrRT

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixeeeeed

Copy link
Copy Markdown
Contributor

@grgia grgia left a comment

Choose a reason for hiding this comment

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

code-wise just need the plural typo fixed really

cristipaval
cristipaval previously approved these changes May 22, 2026
@OSBotify
Copy link
Copy Markdown
Contributor

🦜 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 3c6b3837..6538e8fb 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -7188,8 +7188,8 @@ Fügen Sie weitere Ausgabelimits hinzu, um den Cashflow Ihres Unternehmens zu sc
             disconnect: 'Trennen',
             disconnectTitle: (providerName: string) => `${providerName} trennen`,
             disconnectPrompt: (providerName: string) => `Möchten Sie ${providerName} wirklich trennen?`,
-            alreadyConnectedTitle: 'Verbindung mit mehreren HR-Plattformen nicht möglich',
-            alreadyConnectedPrompt: 'Sie müssen Ihre derzeitige HR-Plattform trennen, bevor Sie eine andere verbinden.',
+            alreadyConnectedTitle: 'Es kann keine Verbindung zu mehreren HR-Plattformen hergestellt werden',
+            alreadyConnectedPrompt: 'Sie müssen Ihre aktuelle HR-Plattform trennen, bevor Sie eine andere verbinden.',
             lastSync: (relativeDate: string) => `Zuletzt synchronisiert ${relativeDate}`,
             syncError: (providerName: string) => `Verbindung zu ${providerName} nicht möglich`,
             connectionDescription: (providerName: string) => `Verbinden Sie ${providerName}, um Mitarbeitergenehmigungen mit Ihrem Workspace zu synchronisieren.`,
diff --git a/src/languages/es.ts b/src/languages/es.ts
index 61efb9b2..00433b6a 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -6289,7 +6289,7 @@ ${amount} para ${merchant} - ${date}`,
             disconnect: 'Desconectar',
             disconnectTitle: (providerName: string) => `Desconectar ${providerName}`,
             disconnectPrompt: (providerName: string) => `¿Seguro que quieres desconectar ${providerName}?`,
-            alreadyConnectedTitle: 'No se puede conectar a múltiples plataformas de RR. HH.',
+            alreadyConnectedTitle: 'No se puede conectar a varias plataformas de RR. HH.',
             alreadyConnectedPrompt: 'Debes desconectar tu plataforma de RR. HH. actual antes de conectar otra.',
             lastSync: (relativeDate: string) => `Última sincronización ${relativeDate}`,
             syncError: (providerName: string) => `No se puede conectar con ${providerName}`,
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 683c2304..9b347d41 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -7212,7 +7212,7 @@ Ajoutez davantage de règles de dépenses pour protéger la trésorerie de l’e
             disconnectTitle: (providerName: string) => `Déconnecter ${providerName}`,
             disconnectPrompt: (providerName: string) => `Êtes-vous sûr de vouloir déconnecter ${providerName} ?`,
             alreadyConnectedTitle: 'Impossible de se connecter à plusieurs plateformes RH',
-            alreadyConnectedPrompt: "Vous devez déconnecter votre plateforme RH actuelle avant d'en connecter une autre.",
+            alreadyConnectedPrompt: 'Vous devez déconnecter votre plateforme RH actuelle avant d’en connecter une autre.',
             lastSync: (relativeDate: string) => `Dernière synchronisation ${relativeDate}`,
             syncError: (providerName: string) => `Impossible de se connecter à ${providerName}`,
             connectionDescription: (providerName: string) => `Connectez ${providerName} pour synchroniser les approbations des employés avec votre espace de travail.`,
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 362b3dcd..14af8e03 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -7176,7 +7176,7 @@ Aggiungi altre regole di spesa per proteggere il flusso di cassa aziendale.`,
             disconnectTitle: (providerName: string) => `Disconnetti ${providerName}`,
             disconnectPrompt: (providerName: string) => `Sei sicuro di voler disconnettere ${providerName}?`,
             alreadyConnectedTitle: 'Impossibile connettersi a più piattaforme HR',
-            alreadyConnectedPrompt: "Devi disconnettere la tua piattaforma HR attuale prima di collegarne un'altra.",
+            alreadyConnectedPrompt: 'Devi disconnettere la tua attuale piattaforma HR prima di collegarne un’altra.',
             lastSync: (relativeDate: string) => `Ultima sincronizzazione ${relativeDate}`,
             syncError: (providerName: string) => `Impossibile connettersi a ${providerName}`,
             connectionDescription: (providerName: string) => `Collega ${providerName} per mantenere sincronizzate le approvazioni dei dipendenti con il tuo spazio di lavoro.`,
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 8e432350..7f87aa0e 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -7150,8 +7150,8 @@ er bestedingsregels toe om de kasstroom van het bedrijf te beschermen.`,
             disconnect: 'Ontkoppelen',
             disconnectTitle: (providerName: string) => `${providerName} ontkoppelen`,
             disconnectPrompt: (providerName: string) => `Weet je zeker dat je ${providerName} wilt ontkoppelen?`,
-            alreadyConnectedTitle: 'Kan geen verbinding maken met meerdere HR-platforms',
-            alreadyConnectedPrompt: 'Je moet je huidige HR-platform ontkoppelen voordat je een ander verbindt.',
+            alreadyConnectedTitle: 'Kan niet met meerdere HR-platformen verbinden',
+            alreadyConnectedPrompt: 'Je moet je huidige HR-platform loskoppelen voordat je een ander kunt verbinden.',
             lastSync: (relativeDate: string) => `Laatst gesynchroniseerd ${relativeDate}`,
             syncError: (providerName: string) => `Kan geen verbinding maken met ${providerName}`,
             connectionDescription: (providerName: string) => `Verbind ${providerName} om goedkeuringen van werknemers gesynchroniseerd te houden met je werkruimte.`,
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 712b9e7e..fff51ab9 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -7145,7 +7145,7 @@ Dodaj więcej zasad wydatków, żeby chronić płynność finansową firmy.`,
             disconnect: 'Odłącz',
             disconnectTitle: (providerName: string) => `Odłącz ${providerName}`,
             disconnectPrompt: (providerName: string) => `Czy na pewno chcesz odłączyć ${providerName}?`,
-            alreadyConnectedTitle: 'Nie można połączyć z wieloma platformami HR',
+            alreadyConnectedTitle: 'Nie można połączyć się z wieloma platformami HR',
             alreadyConnectedPrompt: 'Musisz odłączyć swoją obecną platformę HR, zanim podłączysz inną.',
             lastSync: (relativeDate: string) => `Ostatnia synchronizacja ${relativeDate}`,
             syncError: (providerName: string) => `Nie można połączyć z ${providerName}`,
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 2a64c296..76f90cf8 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -6965,8 +6965,8 @@ ${reportName}
             disconnect: '断开连接',
             disconnectTitle: (providerName: string) => `断开 ${providerName}`,
             disconnectPrompt: (providerName: string) => `确定要断开 ${providerName} 吗?`,
-            alreadyConnectedTitle: '无法连接到多个 HR 平台',
-            alreadyConnectedPrompt: '在连接其他人力资源平台之前,必须先断开当前的人力资源平台。',
+            alreadyConnectedTitle: '无法连接到多个人力资源平台',
+            alreadyConnectedPrompt: '在连接其他人力资源平台之前,您必须先断开当前的人力资源平台。',
             lastSync: (relativeDate: string) => `上次同步 ${relativeDate}`,
             syncError: (providerName: string) => `无法连接到 ${providerName}`,
             connectionDescription: (providerName: string) => `连接 ${providerName},以在您的工作区中同步员工审批。`,

Note

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

View workflow run

@github-actions
Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

@bernhardoj
Copy link
Copy Markdown
Contributor

bernhardoj commented May 22, 2026

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
  • 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 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
android.mp4
Android: mWeb Chrome
android.mweb.mp4
iOS: HybridApp
ios.mp4
iOS: mWeb Safari
ios.mweb.mp4
MacOS: Chrome / Safari
b.mp4

Copy link
Copy Markdown
Contributor

@grgia grgia left a comment

Choose a reason for hiding this comment

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

approving, but will wait on @bernhardoj's review

@bernhardoj
Copy link
Copy Markdown
Contributor

bernhardoj commented May 22, 2026

The modal shows, but looks like the animation is missing 🤔

b.mp4

Tested on other centered modals and has the same issue, so unrelated.

@jmusial
Copy link
Copy Markdown
Contributor Author

jmusial commented May 22, 2026

The modal shows, but looks like the animation is missing 🤔

b.mp4
Tested on other centered modals and has the same issue, so unrelated.

Isn't this the case for all confirm modals ?

@dannymcclain
Copy link
Copy Markdown
Contributor

The modal shows, but looks like the animation is missing 🤔
Isn't this the case for all confirm modals ?

Not sure if it is, but could this be related to this issue? (We're planning on adding back a little animation to the confirm dialogs)

@melvin-bot melvin-bot Bot requested a review from grgia May 22, 2026 16:10
@bernhardoj
Copy link
Copy Markdown
Contributor

@dannymcclain yes, that must be it

@bernhardoj
Copy link
Copy Markdown
Contributor

@grgia ready to merge

@grgia grgia merged commit 77fadd8 into Expensify:main May 22, 2026
40 of 41 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

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

@OSBotify
Copy link
Copy Markdown
Contributor

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

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

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

Bundle Size Analysis (Sentry):

@MelvinBot
Copy link
Copy Markdown
Contributor

I reviewed the changes in this PR and found that a help site update is needed.

What changed: This PR adds a modal preventing users from connecting multiple HR platforms simultaneously. When a workspace already has an HR connection and the user tries to connect another provider, they now see a "Cannot connect to multiple HR platforms" message.

Help site impact: The New Expensify TriNet article (docs/articles/new-expensify/connections/TriNet.md) did not document this single-connection limitation. I added a new FAQ entry explaining that only one HR platform can be connected per workspace at a time and that users must disconnect the existing provider before connecting a new one.

Draft PR: #91477 (labeled HelpDot)

Note: There is no New Expensify Gusto help article currently, so only the TriNet article was updated. The Expensify Classic Gusto and TriNet articles were not changed since this code change only affects the New Expensify HR page.

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 9.3.81-2 🚀

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

yusufdeveloper2903 pushed a commit to yusufdeveloper2903/App that referenced this pull request May 29, 2026
The TriNet help article now mentions that only one HR platform
can be connected per workspace at a time, matching the new modal
behavior added in Expensify#91415.

Co-authored-by: Jan Musiał <jmusial@users.noreply.github.com>
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.

7 participants