Skip to content

[No QA] Docs updates for E/A#103549 Remove read-only vendor list wording, add disable step - #104888

Merged
stephanieelliott merged 1 commit into
mainfrom
claude-vendorEnableDisableDocs
Oct 26, 2026
Merged

stephanieelliott merged 1 commit into
mainfrom
claude-vendorEnableDisableDocs

Conversation

@MelvinBot

Copy link
Copy Markdown
Contributor

Explanation of Change

Add imported vendor enable and disable controls added an Enabled column to Workspaces > [workspace name] > Vendors. Workspace admins can now disable imported vendors so they no longer appear in the Vendor field on expenses.

This made the following sentence incorrect in the vendor matching articles for DualEntry, Campfire, Rillet, and Intuit Enterprise Suite:

Vendors are managed in [integration], so the list is read-only in Expensify and refreshes when the connection syncs.

The list is no longer read-only. Each sentence now says the list refreshes on sync and that admins can disable a vendor in the Enabled column to hide it from the Vendor field.

The Certinia article has the same sentence, but Certinia vendor matching is still behind the vendorMatching beta, so it is left unchanged. The QuickBooks Online, Sage Intacct, and Xero articles don't describe the vendor list as read-only, so they need no change.

The Enabled column label comes from common.enabled in src/languages/en.ts.

@ShridharGoel, please review the files changed and confirm they reflect the current behavior. Then post a new comment saying @MelvinBot mark this PR as ready for review.

Fixed Issues

$ #98355
PROPOSAL:

Tests

// TODO: The human co-author must fill out the tests you ran before marking this PR as "ready for review"
// Please describe what tests you performed that validates your changed worked.

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: The human co-author must fill out the QA tests you ran before marking this PR as "ready for review".
// Please describe what QA needs to do to validate your changes and what areas do they need to test for regressions.

  • 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 any copy / text that was added to the app 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 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 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 the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • 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
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

Co-authored-by: Shridhar Goel <ShridharGoel@users.noreply.github.com>
@MelvinBot
MelvinBot requested a review from a team October 23, 2026 17:26
@MelvinBot MelvinBot added the HelpDot Apply this label if the issue relates to ExpensifyHelp label Oct 23, 2026
@github-actions github-actions Bot changed the title Docs updates for E/A#103549 Remove read-only vendor list wording, add disable step [No QA] Docs updates for E/A#103549 Remove read-only vendor list wording, add disable step Oct 23, 2026
@ShridharGoel

Copy link
Copy Markdown
Contributor

@MelvinBot Mark this as ready

@MelvinBot
MelvinBot marked this pull request as ready for review October 24, 2026 15:15
@MelvinBot

Copy link
Copy Markdown
Contributor Author

I marked this PR as ready for review.


view run

@melvin-bot

melvin-bot Bot commented Oct 24, 2026

Copy link
Copy Markdown

Product reviewer checklist:

  • I have verified the accuracy of the article
    • The article is within a hub that makes sense, and the navigation is correct
    • All processes, screenshots, and examples align with current product behavior.
    • All links within the doc have been verified for correct destination and functionality.
  • I have verified the readability of the article
    • The article's language is clear, concise, and free of jargon.
    • The grammar, spelling, and punctuation are correct.
    • The article contains at least one image, or that an image is not necessary
  • I have verified the formatting of the article
    • The article has consistent formatting (headings, bullet points, etc.) with other HelpDot articles and that aligns with the HelpDot formatting standards.
    • The article has proper text spacing and breaks for readability.
  • I have verified the article has the appropriate tone and style
    • The article's tone is professional, friendly, and suitable for the target audience.
    • The article's tone, terminology, and voice are consistent throughout.
  • I have verified the overall quality of the article
    • The article is not missing any information, nor does it contain redundant information.
    • The article fully addresses user needs.
  • I have verified that all requested improvements have been addressed

For more detailed instructions on completing this checklist, see How do I review a HelpDot PR?

cc @heyjennahay

@melvin-bot
melvin-bot Bot requested review from heyjennahay and removed request for a team October 24, 2026 15:16
@melvin-bot

melvin-bot Bot commented Oct 24, 2026

Copy link
Copy Markdown

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

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 24, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-24T15:18:59.745014Z 793af67 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

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

Copy link
Copy Markdown

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: 793af67e1d

ℹ️ 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".

3. Use **Find vendor** to search the list by name.

Vendors are managed in Campfire, so the list is read-only in Expensify and refreshes when the connection syncs.
Vendors are managed in Campfire, and the list refreshes when the connection syncs. To stop a vendor from appearing in the **Vendor** field on expenses, disable it in the **Enabled** column.

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 Document how to disable a default vendor

When the vendor is currently configured as the workspace's default, this instruction cannot be followed because WorkspaceVendorsPage locks its Enabled toggle and excludes it from bulk disable actions. The same omission appears in all four changed articles, so users must first change or clear the default vendor in the accounting export settings; document that prerequisite rather than directing them to a disabled control.

Useful? React with 👍 / 👎.

@github-actions

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR updates the vendor-matching articles for Campfire, DualEntry, Intuit Enterprise Suite, and Rillet. The same single-sentence change is applied identically to all four files: it removes the outdated "the list is read-only in Expensify" claim and adds guidance that admins can disable an imported vendor in the Enabled column to stop it appearing in the Vendor field. The change is an accuracy fix reflecting PR 103549, and it is small, consistent, and well scoped.

Scores Summary

  • Readability: 9/10 - Two short, clear sentences. States the sync behavior and the disable action concisely with no filler.
  • AI Readiness: 9/10 - The new copy lives inside an existing task-based section heading and uses full feature names and UI-exact labels, which supports retrieval. No metadata or heading changes were introduced (none were needed).
  • Style Compliance: 9/10 - Uses the approved action verb "disable" per the enable/disable toggle rule, bolds the Vendor field and Enabled column as UI labels, and keeps integration names exact. Fully aligned with the naming conventions.

Key Findings

  • Correctly replaces inaccurate "read-only" wording now that the Enabled column allows disabling imported vendors.
  • Consistent wording across all four integrations, which is ideal for parallel articles and retrieval.
  • UI terminology is exact: "disable" (not "turn off"), bold Vendor field, bold Enabled column.
  • Scope is appropriate - Certinia (still behind the vendorMatching beta) and the QBO/Sage Intacct/Xero articles were correctly left untouched, per the PR description.
  • Minor: "disable it in the Enabled column" tells the user where but not the exact control. If the column contains a labeled toggle, naming it explicitly would match the field/toggle referencing guidance even more precisely. Optional.

Recommendations

  • No blocking issues. The change is accurate and compliant and can merge as-is.
  • Optional: confirm the exact control in the Enabled column (toggle vs. checkbox) and name it explicitly for maximum UI precision.

Files Reviewed

  • docs/articles/new-expensify/connections/campfire/Manage-Vendor-Matching-for-Campfire.md - Compliant
  • docs/articles/new-expensify/connections/dualentry/Manage-Vendor-Matching-for-DualEntry.md - Compliant
  • docs/articles/new-expensify/connections/intuit-enterprise-suite/Manage-Vendor-Matching-for-Intuit-Enterprise-Suite.md - Compliant
  • docs/articles/new-expensify/connections/rillet/Manage-Vendor-Matching-for-Rillet.md - Compliant

Note: Detailed line-by-line feedback has been provided as inline comments.

@stephanieelliott
stephanieelliott merged commit ff9e3cb into main Oct 26, 2026
25 of 28 checks passed
@stephanieelliott
stephanieelliott deleted the claude-vendorEnableDisableDocs branch October 26, 2026 20:27
@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.5.21-0 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.5.23-0 🚀

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

HelpDot Apply this label if the issue relates to ExpensifyHelp

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants