Skip to content

[No QA][HR Import] Generalize Workflows page for any HR connection#91324

Open
jmusial wants to merge 9 commits into
Expensify:mainfrom
software-mansion-labs:feat/generalize-workflows-for-any-hr-connection
Open

[No QA][HR Import] Generalize Workflows page for any HR connection#91324
jmusial wants to merge 9 commits into
Expensify:mainfrom
software-mansion-labs:feat/generalize-workflows-for-any-hr-connection

Conversation

@jmusial
Copy link
Copy Markdown
Contributor

@jmusial jmusial commented May 21, 2026

Explanation of Change

This PR safeguards the workflow modification pages when basic or manager approval modes are set and makes sure that the workflow chains display the manager with label when manager workflow is set.

Fixed Issues

$ #90604

PROPOSAL:

Tests

You muse have a workspace with synced merge dev provider.

  1. Open Workspace->HR page
  2. Make sure you have approval mode and Final approver set
  3. Set approval mode to Basic
  4. Go to Workspace->Workflows page
  5. Verify that there is one required approver (and it's a final approver)
  6. Go back to Workspace->HR page
  7. Set approval mode to Manager
  8. Go to Workspace->Workflows page
  9. Verify that there are 2 requred approver (manager and it's a final approver), there may also be more depending on org structure
  10. Go back to Workspace->HR page
  11. Set approval mode to Custom
  12. Go to Workspace->Workflows page
  13. Verify that you can modify the workflow
    1. Go back to Workspace->HR page
  14. Set approval mode to Basic
  15. Go to Workspace->Workflows page
  16. Try to access (ex. paste a link) new workflow page and verify that it cannot be accessed

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

@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 21, 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

@codecov
Copy link
Copy Markdown

codecov Bot commented May 21, 2026

Codecov Report

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

Files with missing lines Coverage Δ
src/libs/PolicyUtils.ts 71.25% <100.00%> (+0.39%) ⬆️
src/libs/WorkflowUtils.ts 87.29% <100.00%> (+0.71%) ⬆️
.../approvals/WorkspaceWorkflowsApprovalsEditPage.tsx 70.00% <100.00%> (ø)
...pprovals/WorkspaceWorkflowsApprovalsCreatePage.tsx 0.00% <0.00%> (ø)
...ges/workspace/workflows/WorkspaceWorkflowsPage.tsx 0.00% <0.00%> (ø)
src/components/ApprovalWorkflowSection.tsx 0.00% <0.00%> (ø)
... and 64 files with indirect coverage changes

@jmusial
Copy link
Copy Markdown
Contributor Author

jmusial commented May 22, 2026

@codex review

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 98dc455df8

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +53 to +56
const isLastApprover = index === approvalWorkflow.approvers.length - 1;
if (isLastApprover) {
return translate('workflowsPage.finalApprover');
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Label last approver as final only when final approver exists

In HR manager mode this unconditionally labels the last row as Final approver, but convertPolicyEmployeesToApprovalWorkflows() only appends a real final approver when mergeConfig.finalApprover is set. During setup/migration states where manager mode is enabled but finalApprover is still null, the chain can end with a manager and this UI will mislabel that manager as the final approver, which is misleading for admins reviewing routing.

Useful? React with 👍 / 👎.

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.

fixed

@jmusial jmusial marked this pull request as ready for review May 22, 2026 15:52
@jmusial jmusial requested review from a team as code owners May 22, 2026 15:52
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 22, 2026

@bernhardoj 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 removed request for a team May 22, 2026 15:52
@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 1c54bf62..6295ac0e 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -2618,7 +2618,7 @@ ${amount} für ${merchant} – ${date}`,
             `Genehmigungen werden über deine ${provider}-Integration verwaltet. Um deinen Genehmigungsworkflow zu aktualisieren, gehe zu deinen ${provider}-Verbindungseinstellungen.`,
         goToHRSettings: ({provider}: {provider: string}) => `Zu den ${provider}-Einstellungen gehen`,
         approverFromProvider: ({provider}: {provider: string}) => `von ${provider}`,
-        finalApprover: 'Endgenehmiger',
+        finalApprover: 'Letzte*r Genehmigende*r',
         manager: 'Manager',
     },
     workflowsDelayedSubmissionPage: {
diff --git a/src/languages/es.ts b/src/languages/es.ts
index 4325d6d8..75ef5fcf 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -2442,7 +2442,7 @@ ${amount} para ${merchant} - ${date}`,
         goToHRSettings: ({provider}: {provider: string}) => `Ir a la configuración de ${provider}`,
         approverFromProvider: ({provider}: {provider: string}) => `de ${provider}`,
         finalApprover: 'Aprobador final',
-        manager: 'Gerente',
+        manager: 'Responsable',
         makeOrTrackPaymentsTitle: 'Realizar o seguir pagos',
         makeOrTrackPaymentsDescription: 'Añade un pagador autorizado para los pagos realizados en Expensify o realiza un seguimiento de los pagos realizados en otro lugar.',
         customApprovalWorkflowEnabled:
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 85a07208..a49db1c9 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -2622,7 +2622,7 @@ ${amount} pour ${merchant} - ${date}`,
         hrApprovalWorkflowLockedPrompt: ({provider}: {provider: string}) =>
             `Les validations sont gérées par votre intégration ${provider}. Pour mettre à jour votre workflow de validation, accédez aux paramètres de connexion ${provider}.`,
         goToHRSettings: ({provider}: {provider: string}) => `Aller aux paramètres ${provider}`,
-        approverFromProvider: ({provider}: {provider: string}) => `de ${provider}`,
+        approverFromProvider: ({provider}: {provider: string}) => `de la part de ${provider}`,
         finalApprover: 'Approbateur final',
         manager: 'Manager',
     },
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 1a323c49..2d1a6233 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -2613,8 +2613,8 @@ ${amount} per ${merchant} - ${date}`,
             `Le approvazioni sono gestite dalla tua integrazione con ${provider}. Per aggiornare il flusso di approvazione, vai alle impostazioni di connessione di ${provider}.`,
         goToHRSettings: ({provider}: {provider: string}) => `Vai alle impostazioni di ${provider}`,
         approverFromProvider: ({provider}: {provider: string}) => `da ${provider}`,
-        finalApprover: 'Approvatore finale',
-        manager: 'Manager',
+        finalApprover: 'Approvazione finale',
+        manager: 'Responsabile',
     },
     workflowsDelayedSubmissionPage: {
         autoReportingFrequencyErrorMessage: 'Impossibile modificare la frequenza di invio. Riprova oppure contatta l’assistenza.',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 8a8d570c..c7070e68 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -2610,7 +2610,7 @@ ${amount} voor ${merchant} - ${date}`,
             `Goedkeuringen worden beheerd door je ${provider}-integratie. Ga naar je ${provider}-verbindingsinstellingen om je goedkeuringsworkflow bij te werken.`,
         goToHRSettings: ({provider}: {provider: string}) => `Ga naar ${provider}-instellingen`,
         approverFromProvider: ({provider}: {provider: string}) => `van ${provider}`,
-        finalApprover: 'Eindgoedkeurder',
+        finalApprover: 'Laatste fiatteur',
         manager: 'Manager',
     },
     workflowsDelayedSubmissionPage: {
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 989b21cb..9e3d09c4 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -2605,9 +2605,9 @@ ${amount} dla ${merchant} - ${date}`,
         hrApprovalWorkflowLockedPrompt: ({provider}: {provider: string}) =>
             `Zatwierdzanie jest zarządzane przez Twoją integrację z ${provider}. Aby zaktualizować swój proces zatwierdzania, przejdź do ustawień połączenia z ${provider}.`,
         goToHRSettings: ({provider}: {provider: string}) => `Przejdź do ustawień ${provider}`,
-        approverFromProvider: ({provider}: {provider: string}) => `z ${provider}`,
-        finalApprover: 'Końcowy zatwierdzający',
-        manager: 'Kierownik',
+        approverFromProvider: ({provider}: {provider: string}) => `od ${provider}`,
+        finalApprover: 'Ostateczny akceptujący',
+        manager: 'Menedżer',
     },
     workflowsDelayedSubmissionPage: {
         autoReportingFrequencyErrorMessage: 'Nie udało się zmienić częstotliwości wysyłania. Spróbuj ponownie lub skontaktuj się z pomocą techniczną.',

Note

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

View workflow run

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 01990a9031

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/libs/WorkflowUtils.ts
function convertPolicyEmployeesToApprovalWorkflows({policy, personalDetails, firstApprover, localeCompare, currentUserLogin}: PolicyConversionParams): PolicyConversionResult {
const employees = policy?.employeeList ?? {};
const defaultApprover = getDefaultApprover(policy);
const defaultApprover = getMergeHRFinalApprover(policy) ?? getDefaultApprover(policy);
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Keep default approver resolvable in Merge HR modes

Using getMergeHRFinalApprover(policy) as defaultApprover can set the default workflow anchor to an email that is not present in employeeList; when that happens, no workflow is created for that approver and the later default-workflow insertion path ends up with calculateApprovers(...) returning an empty approver chain. This produces an empty "Everyone" workflow in read-only HR basic/manager setups instead of showing the required approver, so admins lose the routing visibility this change is trying to provide.

Useful? React with 👍 / 👎.

@bernhardoj
Copy link
Copy Markdown
Contributor

Looks like this requires a synced merge provider, but the sync keeps failing on my side.

When I sync it manually, I get.
"500 Failed to dispatch Merge sync job"

When I let it sync automatically, I get a timed-out error.

Is there something missing to do?


const approverTitle = (index: number) =>
approvalWorkflow.approvers.length > 1 ? `${toLocaleOrdinal(index + 1, true)} ${translate('workflowsPage.approver').toLowerCase()}` : `${translate('workflowsPage.approver')}`;
const fromProviderSuffix = hrProviderName ? ` (${translate('workflowsPage.approverFromProvider', {provider: hrProviderName})})` : '';
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.

I think we should define this right before it's being used here

return translate('workflowsPage.approver');
}
const isLastApprover = index === approvalWorkflow.approvers.length - 1;
if (isLastApprover && approvalWorkflow.approvers.length > 1) {
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.

approvalWorkflow.approvers.length > 1 is always true

Copy link
Copy Markdown
Contributor

@roryabraham roryabraham left a comment

Choose a reason for hiding this comment

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

no blockers from me

Comment thread src/libs/PolicyUtils.ts
}

/** Returns the Merge HR finalApprover when the integration is in "basic" approval mode, or null otherwise. */
function getMergeHRBasicModeFinalApprover(policy: OnyxEntry<Policy>): string | null {
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.

NAB: this file has become so large that syntax highlighting has stopped working. Put Merge.dev / HR sync stuff in a new dedicated file.

Comment thread src/libs/WorkflowUtils.ts
const effectiveSubmitsTo = shouldFilterOutExpensifyTeam ? (findFirstNonExpensifyApprover(employees, submitsTo) ?? submitsTo) : submitsTo;

if (!employees[effectiveSubmitsTo]) {
if (!employees[submitsTo] && !isMergeHRManagerMode) {
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.

NAB: we have two back-to-back if statements that just do continue. Maybe it would be cleaner to combine them.

hrProviderName?: string;

/** When true, uses HR manager mode labels: "Manager (from {provider})" then "Final approver" */
isHRManagerMode?: boolean;
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.

The term "manager mode" is kind of confusing because there are three canonical approval modes in our backend:

  • Basic
  • Advanced (I think this is what we're calling "manager mode")
  • Manual

imo it would be better to use the same terms in the front-end and the back-end in the code, even though the product shows the modes as Basic, Manager, and Custom.

Copy link
Copy Markdown
Contributor

@joekaufmanexpensify joekaufmanexpensify left a comment

Choose a reason for hiding this comment

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

Core sprint issue

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.

5 participants