Repository navigation
[No QA] Add INT133 help article for inactive Sage Intacct web services user - #104092
Conversation
Co-authored-by: Akinwale Ariwodola <[email protected]>
This comment has been minimized.
This comment has been minimized.
|
@MelvinBot The navigation path to access Web services users on Sage Intacct is Company > Admin > Web Services users. |
Co-authored-by: Akinwale Ariwodola <[email protected]>
|
Thanks. I updated step 2 to Company > Admin > Web Services users in all four INT133 articles:
I also updated the path in the PR description. |
|
@MelvinBot This is ready for review. |
|
Done. I marked this PR as ready for review. |
Product reviewer checklist:
For more detailed instructions on completing this checklist, see How do I review a HelpDot PR? |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
@joekaufmanexpensify 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] |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
|
||
| --- | ||
|
|
||
| ## Why the INT133 Sync Error Happens in Sage Intacct |
There was a problem hiding this comment.
Heading capitalization: ## headings must use sentence case. Change to ## Why the INT133 sync error happens in Sage Intacct (keep proper nouns). See HELPSITE_NAMING_CONVENTIONS.md "Article Titles and Headings" and HELP_AUTHORING_GUIDELINES.md Section 2.
|
|
||
| --- | ||
|
|
||
| ## How to Fix the INT133 Sync Error |
There was a problem hiding this comment.
Heading capitalization: Use sentence case for ## headings: ## How to fix the INT133 sync error. Per HELP_AUTHORING_GUIDELINES.md Section 2 and HELPSITE_NAMING_CONVENTIONS.md.
|
|
||
| This issue must be resolved in Sage Intacct and then retried in Expensify. | ||
|
|
||
| ### Reactivate the Web Services User in Sage Intacct |
There was a problem hiding this comment.
Forbidden heading level: ### headings are not allowed—only # and ## may be used (HELP_AUTHORING_GUIDELINES.md Section 4 and Pre-Publish Checklist). Demote to a ## heading and use sentence case: ## Reactivate the web services user in Sage Intacct.
| 1. Log in to Sage Intacct as an administrator. | ||
| 2. Go to **Company > Admin > Web Services users**. | ||
| 3. Locate the **xmlgateway_expensify** web services user. | ||
| 4. Click **Edit**. |
There was a problem hiding this comment.
Action verb violation: Use select, never "click" (HELPSITE_NAMING_CONVENTIONS.md "Actions"). Change to Select **Edit**. Same applies to line 41 (Select **Save**).
|
|
||
| --- | ||
|
|
||
| ### Retry the Sync in Expensify |
There was a problem hiding this comment.
Forbidden heading level: ### is not allowed—use only #/##. Demote and use sentence case: ## Retry the sync in Expensify. See HELP_AUTHORING_GUIDELINES.md Section 4.
| ### Retry the Sync in Expensify | ||
|
|
||
| 1. Go to **Settings > Workspaces**. | ||
| 2. Select your Workspace. |
There was a problem hiding this comment.
Terminology: Use lowercase "workspace" in running text unless quoting a UI label (HELPSITE_NAMING_CONVENTIONS.md "Generic Terms"). Also use a bolded navigation path and select rather than naming the Workspace generically, e.g. Select **Settings > Workspaces > [workspace name]**.
|
|
||
| 1. Go to **Settings > Workspaces**. | ||
| 2. Select your Workspace. | ||
| 3. Click **Accounting**. |
There was a problem hiding this comment.
Action verb violation: Use select, not "click" (HELPSITE_NAMING_CONVENTIONS.md "Actions"). Change to Select **Accounting**. Same on line 52 (Select **Sync Now**).
|
|
||
| # FAQ | ||
|
|
||
| ## Do I Need Sage Intacct Admin Access? |
There was a problem hiding this comment.
Heading capitalization: FAQ questions use ## and must be sentence case. Change to ## Do I need Sage Intacct admin access? Per TEMPLATE.md FAQ structure and HELPSITE_NAMING_CONVENTIONS.md. Same for lines 64 and 68.
|
|
||
| - The `xmlgateway_expensify` web services user was deactivated in Sage Intacct. | ||
| - An administrator changed the user's status to **Inactive** during a user cleanup or license review. | ||
| - The web services user that was used to connect the Workspace is no longer in use. |
There was a problem hiding this comment.
Terminology: Use lowercase "workspace" in running text (HELPSITE_NAMING_CONVENTIONS.md "Generic Terms"): "...used to connect the workspace is no longer in use."
| internalScope: Audience is Workspace Admins using the Sage Intacct integration. Covers resolving the INT133 sync error caused by an inactive Sage Intacct web services user. Does not cover incorrect credentials or Sender ID errors (see INT122). | ||
| --- | ||
|
|
||
| # INT133 Sync Error in Sage Intacct Integration |
There was a problem hiding this comment.
Duplicate article / scope: This file is byte-identical to the Sync-Errors/INT133-Sync-Error.md article. Publishing the same INT133 content under two folders creates duplicate articles that dilute retrieval precision (HELP_AUTHORING_GUIDELINES.md Sections 1 & 6). Keep one canonical article and cross-link if needed.
|
|
||
| --- | ||
|
|
||
| ## Why the INT133 Sync Error Happens in Sage Intacct |
There was a problem hiding this comment.
Heading capitalization: Use sentence case for ## headings: ## Why the INT133 sync error happens in Sage Intacct. See HELP_AUTHORING_GUIDELINES.md Section 2.
|
|
||
| This issue must be resolved in Sage Intacct and then retried in Expensify. | ||
|
|
||
| ### Reactivate the Web Services User in Sage Intacct |
There was a problem hiding this comment.
Forbidden heading level: ### is not allowed—only #/## (HELP_AUTHORING_GUIDELINES.md Section 4). Demote and use sentence case: ## Reactivate the web services user in Sage Intacct.
| 1. Log in to Sage Intacct as an administrator. | ||
| 2. Go to **Company > Admin > Web Services users**. | ||
| 3. Locate the **xmlgateway_expensify** web services user. | ||
| 4. Click **Edit**. |
There was a problem hiding this comment.
Action verb violation: Use select, not "click" (HELPSITE_NAMING_CONVENTIONS.md "Actions"): Select **Edit**. Same applies to line 41.
|
|
||
| --- | ||
|
|
||
| ### Retry the Sync in Expensify |
There was a problem hiding this comment.
Forbidden heading level: ### not allowed. Demote and use sentence case: ## Retry the sync in Expensify. See HELP_AUTHORING_GUIDELINES.md Section 4.
| ### Retry the Sync in Expensify | ||
|
|
||
| 1. Go to **Settings > Workspaces**. | ||
| 2. Select your Workspace. |
There was a problem hiding this comment.
Terminology / navigation: Lowercase "workspace" in running text and use a bolded navigation path with select, e.g. Select **Settings > Workspaces > [workspace name]**. See HELPSITE_NAMING_CONVENTIONS.md "Generic Terms" and "Navigation Paths".
|
|
||
| 1. Go to **Settings > Workspaces**. | ||
| 2. Select your Workspace. | ||
| 3. Click **Accounting**. |
There was a problem hiding this comment.
Action verb violation: Use select, not "click": Select **Accounting**. Same on line 52 (Select **Sync Now**). See HELPSITE_NAMING_CONVENTIONS.md "Actions".
|
|
||
| # FAQ | ||
|
|
||
| ## Do I Need Sage Intacct Admin Access? |
There was a problem hiding this comment.
Heading capitalization: FAQ ## questions must be sentence case: ## Do I need Sage Intacct admin access? Same for lines 64 and 68. Per TEMPLATE.md FAQ structure and HELPSITE_NAMING_CONVENTIONS.md.
|
|
||
| --- | ||
|
|
||
| ## Why the INT133 Sync Error Happens in Sage Intacct |
There was a problem hiding this comment.
Heading capitalization: Use sentence case for ## headings: ## Why the INT133 sync error happens in Sage Intacct. See HELP_AUTHORING_GUIDELINES.md Section 2.
|
|
||
| --- | ||
|
|
||
| ## How to Fix the INT133 Sync Error |
There was a problem hiding this comment.
Heading capitalization: Use sentence case: ## How to fix the INT133 sync error. Per HELP_AUTHORING_GUIDELINES.md Section 2.
|
|
||
| --- | ||
|
|
||
| ## Reactivate the Web Services User in Sage Intacct |
There was a problem hiding this comment.
Heading rules: Use sentence case and start with an action verb/question word (HELP_AUTHORING_GUIDELINES.md Section 2): ## How to reactivate the web services user in Sage Intacct.
| 1. Log in to Sage Intacct as an administrator. | ||
| 2. Go to **Company > Admin > Web Services users**. | ||
| 3. Locate the **xmlgateway_expensify** web services user. | ||
| 4. Click **Edit**. |
There was a problem hiding this comment.
Action verb violation: Use select, not "click" (HELPSITE_NAMING_CONVENTIONS.md "Actions"): Select **Edit**. Same applies to line 45 (Select **Save**).
|
|
||
| --- | ||
|
|
||
| ## Retry the Sync |
There was a problem hiding this comment.
Heading rules: ## Retry the Sync is a bare topic label in title case. Use a sentence-case, task-based heading: ## How to retry the sync in Expensify. See HELP_AUTHORING_GUIDELINES.md Section 2.
|
|
||
| After reactivating the web services user: | ||
|
|
||
| 1. Go to **Workspaces > [Workspace Name] > Accounting**. |
There was a problem hiding this comment.
Navigation path placeholder: Use a lowercase bracketed placeholder and select: Select **Workspaces > [workspace name] > Accounting**. Per HELPSITE_NAMING_CONVENTIONS.md "Navigation Paths" (placeholders must be lowercase, e.g. [workspace name], not [Workspace Name]).
|
|
||
| # FAQ | ||
|
|
||
| ## Do I Need Sage Intacct Admin Access to Fix This? |
There was a problem hiding this comment.
Heading capitalization: FAQ ## questions must be sentence case: ## Do I need Sage Intacct admin access to fix this? Same for lines 69 and 73. Per TEMPLATE.md FAQ structure and HELPSITE_NAMING_CONVENTIONS.md.
| internalScope: Audience is Workspace Admins managing the Sage Intacct integration. Covers resolving the INT133 sync error caused by an inactive Sage Intacct web services user. Does not cover incorrect credentials or Sender ID errors (see INT122). | ||
| --- | ||
|
|
||
| # INT133 Sync Error in Sage Intacct Integration |
There was a problem hiding this comment.
Duplicate article / scope: This file is identical to the new-expensify Authentication-and-Login-errors/INT133-Sync-Error.md. Duplicate articles under two folders dilute retrieval precision (HELP_AUTHORING_GUIDELINES.md Sections 1 & 6). Keep one canonical article.
|
|
||
| --- | ||
|
|
||
| ## Why the INT133 Sync Error Happens in Sage Intacct |
There was a problem hiding this comment.
Heading capitalization: Use sentence case for ## headings: ## Why the INT133 sync error happens in Sage Intacct. See HELP_AUTHORING_GUIDELINES.md Section 2.
|
|
||
| --- | ||
|
|
||
| ## How to Fix the INT133 Sync Error |
There was a problem hiding this comment.
Heading capitalization: Use sentence case: ## How to fix the INT133 sync error. Per HELP_AUTHORING_GUIDELINES.md Section 2.
|
|
||
| --- | ||
|
|
||
| ## Reactivate the Web Services User in Sage Intacct |
There was a problem hiding this comment.
Heading rules: Use sentence case and a task-based phrase: ## How to reactivate the web services user in Sage Intacct. See HELP_AUTHORING_GUIDELINES.md Section 2.
| 1. Log in to Sage Intacct as an administrator. | ||
| 2. Go to **Company > Admin > Web Services users**. | ||
| 3. Locate the **xmlgateway_expensify** web services user. | ||
| 4. Click **Edit**. |
There was a problem hiding this comment.
Action verb violation: Use select, not "click" (HELPSITE_NAMING_CONVENTIONS.md "Actions"): Select **Edit**. Same applies to line 45.
|
|
||
| --- | ||
|
|
||
| ## Retry the Sync |
There was a problem hiding this comment.
Heading rules: ## Retry the Sync is a bare title-case topic label. Use a sentence-case, task-based heading: ## How to retry the sync in Expensify. See HELP_AUTHORING_GUIDELINES.md Section 2.
|
|
||
| After reactivating the web services user: | ||
|
|
||
| 1. Go to **Workspaces > [Workspace Name] > Accounting**. |
There was a problem hiding this comment.
Navigation path placeholder: Placeholders must be lowercase and use select: Select **Workspaces > [workspace name] > Accounting**. Per HELPSITE_NAMING_CONVENTIONS.md "Navigation Paths" ([workspace name], not [Workspace Name]).
|
|
||
| # FAQ | ||
|
|
||
| ## Do I Need Sage Intacct Admin Access to Fix This? |
There was a problem hiding this comment.
Heading capitalization: FAQ ## questions must be sentence case: ## Do I need Sage Intacct admin access to fix this? Same for lines 69 and 73. Per TEMPLATE.md FAQ structure.
| internalScope: Audience is Workspace Admins managing the Sage Intacct integration. Covers resolving the INT133 sync error caused by an inactive Sage Intacct web services user. Does not cover incorrect credentials or Sender ID errors (see INT122). | ||
| --- | ||
|
|
||
| # INT133 Sync Error in Sage Intacct Integration |
There was a problem hiding this comment.
Duplicate article / scope: This file is identical to the new-expensify Sync-Errors/INT133-Sync-Error.md article. Publishing the same content in two folders dilutes retrieval precision (HELP_AUTHORING_GUIDELINES.md Sections 1 & 6). Keep one canonical article.
|
HelpDot Documentation Review Overall Assessment Scores Summary
Key Findings
Recommendations
Files Reviewed
Note: Detailed line-by-line feedback has been provided as inline comments. |
|
No fix is needed. The only failing check is That check fails until someone other than the PR author approves the PR. Every other check passed or was skipped. Once a reviewer approves, the check will pass. |
|
🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.5.13-0 🚀
|
|
🚀 Deployed to production by https://github.com/grgia in version: 9.5.13-6 🚀
Bundle Size Analysis (Sentry): |
Explanation of Change
Adds a new help article for the INT133 Sage Intacct sync error. Sage Intacct returns
PL04000076("This user is in the INACTIVE state") when the web services user that connects the Workspace is inactive. Today that case shows a generic message, which suggests Sage Intacct is temporarily down. A dedicated INT133 error and article will tell admins the real fix: reactivate the web services user in Sage Intacct.The article is added for both New Expensify and Expensify Classic. Each copy lives in both
Authentication-and-Login-errors/andSync-Errors/, the same way the INT122 article does. Sync error links point to theSync-Errors/path, so that copy is the one the in-product link will open.The article quotes this error message, which the backend change for INT133 should match:
The navigation path for the web services user is Company > Admin > Web Services users.
Fixed Issues
$ https://github.com/Expensify/Expensify/issues/689645
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.
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.
PR Author Checklist
### Fixed Issuessection aboveTestssectionOffline stepssectionQA stepssectionAvatar, I verified the components usingAvatarare working as expected)npm run compress-svg)Avataris modified, I verified thatAvataris working as expected in all cases)Designlabel and/or tagged@Expensify/designso the design team can review the changes.mainbranch was merged into this PR after a review, I tested again and verified the outcome was still expected according to theTeststeps.Screenshots/Videos
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari