Skip to content

Handle POLICYCHANGELOG_ADD_RULE, UPDATE_RULE, REMOVE_RULE report actions - #98689

Draft
luacmartins wants to merge 5 commits into
mainfrom
luacmartins-policyRuleChangelogActions
Draft

Handle POLICYCHANGELOG_ADD_RULE, UPDATE_RULE, REMOVE_RULE report actions#98689
luacmartins wants to merge 5 commits into
mainfrom
luacmartins-policyRuleChangelogActions

Conversation

@luacmartins

Copy link
Copy Markdown
Contributor

Explanation of Change

Adds App-side support for rendering the new POLICYCHANGELOG_ADD_RULE, UPDATE_RULE, and REMOVE_RULE report actions from Web-Expensify#55203, following the existing static-text policy changelog pattern.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/662964
PROPOSAL:

Tests

The backend rules engine that emits these actions isn't fully live yet, so this was verified by forging report actions in Onyx rather than end-to-end.

  1. Forge a report action of type POLICYCHANGELOG_ADD_RULE in Onyx for a report.
  2. Open that report and verify the action renders "added a rule".
  3. Repeat for POLICYCHANGELOG_UPDATE_RULE ("updated a rule") and POLICYCHANGELOG_REMOVE_RULE ("removed a rule").
  4. Verify the LHN preview text for each action matches the report view text.
  5. Switch the app locale to a non-English language and repeat steps 1-4 to verify translations render.
  • Verify that no errors appear in the JS console

Offline tests

Same as Tests.

QA Steps

Not testable on staging yet - the backend rules engine has not shipped. QA coverage will follow once Web-Expensify#55203 is live.

  • 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 followed proper code patterns (see Reviewing the code)
    • 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 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)
  • 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)
  • 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.
  • 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

Not tested - backend feature not fully live yet.

Android: mWeb Chrome

Not tested - backend feature not fully live yet.

iOS: Native

Not tested - backend feature not fully live yet.

iOS: mWeb Safari

Not tested - backend feature not fully live yet.

MacOS: Chrome / Safari

Not tested - backend feature not fully live yet.

Backend added these report action types for the rules engine (see
Web-Expensify PR #55203).
…ctions

Follows the static-string pattern used by other simple policy
changelog actions (e.g. IMPORT_TAGS, CORPORATE_UPGRADE).
@luacmartins luacmartins self-assigned this Aug 14, 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 d0ef4aee..68998cb0 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -8741,9 +8741,9 @@ Fügen Sie weitere Ausgabelimits hinzu, um den Cashflow Ihres Unternehmens zu sc
                 title ? `hat die Agentenregel „${title}“ aktualisiert zu: ${prompt}` : `hat eine Agentenregel aktualisiert zu: ${prompt}`,
             deleted: ({title}: {title: string}) => (title ? `hat die Agentenregel „${title}“ entfernt` : 'hat eine Agentenregel entfernt'),
         },
-        addedRule: 'eine Regel hinzugefügt',
+        addedRule: 'hat eine Regel hinzugefügt',
         updatedRule: 'eine Regel aktualisiert',
-        removedRule: 'eine Regel entfernt',
+        removedRule: 'hat eine Regel entfernt',
         expensifyCardRule: {
             actionVerb: {block: 'blockiert', allow: 'erlaubt'},
             amountOperator: {over: 'über', under: 'unter'},
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index e5d7a087..9f6aff3d 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -8661,9 +8661,9 @@ Dodaj więcej zasad wydatków, żeby chronić płynność finansową firmy.`,
             updated: ({title, prompt}: {title: string; prompt: string}) => (title ? `zaktualizował(a) regułę agenta „${title}” na: ${prompt}` : `zaktualizowano regułę agenta na: ${prompt}`),
             deleted: ({title}: {title: string}) => (title ? `usunął(-ęła) regułę agenta „${title}”` : 'usunięto regułę agenta'),
         },
-        addedRule: 'dodał(-a) regułę',
-        updatedRule: 'zaktualizował(-a) regułę',
-        removedRule: 'usunął(-ęła) regułę',
+        addedRule: 'dodano regułę',
+        updatedRule: 'zaktualizowano regułę',
+        removedRule: 'usunięto regułę',
         expensifyCardRule: {
             actionVerb: {block: 'zablokowane', allow: 'dozwolone'},
             amountOperator: {over: 'ponad', under: 'pod'},
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index cb277a63..36cb06ea 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -8377,9 +8377,9 @@ ${reportName}`,
             updated: ({title, prompt}: {title: string; prompt: string}) => (title ? `已将代理规则“${title}”更新为:${prompt}` : `已将代理规则更新为:${prompt}`),
             deleted: ({title}: {title: string}) => (title ? `已移除代理规则“${title}”` : '已移除代理规则'),
         },
-        addedRule: '已添加规则',
-        updatedRule: '已更新规则',
-        removedRule: '已移除规则',
+        addedRule: '已添加一条规则',
+        updatedRule: '更新了一条规则',
+        removedRule: '已删除一条规则',
         expensifyCardRule: {
             actionVerb: {block: '已阻止', allow: '允许'},
             amountOperator: {over: '结束', under: '在……之下'},

Note

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

View workflow run

@codecov

codecov Bot commented Aug 14, 2026

Copy link
Copy Markdown

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/CONST/index.ts 94.85% <ø> (ø)
...x/report/actionContents/PolicyChangeLogContent.tsx 100.00% <100.00%> (ø)
src/libs/SidebarUtils.ts 80.05% <50.00%> (-0.27%) ⬇️
... and 9 files with indirect coverage changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants