Skip to content

Add Fwk_0001 help article mapping in helpArticles#138

Draft
Copilot wants to merge 3 commits into
mainfrom
copilot/add-fwk-0001-error-code
Draft

Add Fwk_0001 help article mapping in helpArticles#138
Copilot wants to merge 3 commits into
mainfrom
copilot/add-fwk-0001-error-code

Conversation

Copy link
Copy Markdown

Copilot AI commented May 23, 2026

Adds support for the Fwk_0001 error code in the help article lookup so users can resolve this issue type to the appropriate KB guidance. This follows the existing helpArticles mapping pattern and ordering conventions.

  • Help article mapping update

    • Added Fwk_0001 to src/components/help-articles.ts in alphabetical position within helpArticles.
    • Used the provided ServiceNow URL directly (including #ExtentsVolumeErrors) because the source link is sys_kb_id-based rather than sysparm_article-based.
  • Resulting mapping

    Fwk_0001:
      'https://bentleysystems.service-now.com/community?sys_kb_id=27c6de818730b250c0fa43f6cebb350c&id=kb_article_view&sysparm_rank=40&sysparm_tsqueryId=1b23e0e587963210e25dbb35dabb350d#ExtentsVolumeErrors',
Original prompt

Add the Fwk_0001 error code entry to the helpArticles map in src/components/help-articles.ts.

The KB article URL for this error code is:
https://bentleysystems.service-now.com/community?sys_kb_id=27c6de818730b250c0fa43f6cebb350c&id=kb_article_view&sysparm_rank=40&sysparm_tsqueryId=1b23e0e587963210e25dbb35dabb350d#ExtentsVolumeErrors

Looking at the existing pattern in help-articles.ts, entries use NewKBArticleBaseUrl which is https://bentleysystems.service-now.com/community?id=kb_article_view&sysparm_article=. The fragment for this article is #ExtentsVolumeErrors.

Since the provided URL uses sys_kb_id instead of sysparm_article, you may need to determine the appropriate KB article number (e.g., KB00XXXXX) or use the full URL directly. Look at how other entries are structured and add Fwk_0001 consistently. If the KB article ID cannot be mapped to the NewKBArticleBaseUrl pattern, store the full URL directly as a string value.

Add the entry in alphabetical order among the existing entries in the helpArticles object.

Reference issue: #137

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: Add the following error code and KB article link https://bentleysystems.service-now.com/community?sys_kb_id=27c6de818730b250c0fa43f6cebb350c&id=kb_article_view&sysparm_rank=40&sysparm_tsqueryId=1b23e0e587963210e25dbb35dabb350d#ExtentsVolumeErrors to this repository. Use previously added examples to update the code in all the right places.

Assistant: Now I have the full picture. The issue asks to add the Fwk_0001 error code with the KB article link. Looking at the provided URL:

https://bentleysystems.service-now.com/community?sys_kb_id=27c6de818730b250c0fa43f6cebb350c&id=kb_article_view&sysparm_rank=40&sysparm_tsqueryId=1b23e0e587963210e25dbb35dabb350d#ExtentsVolumeErrors

This follows a different URL pattern than the existing NewKBArticleBaseUrl. Let me check what KB article number this corresponds to and create the PR.

Assistant: I'm waiting for your confirmation to proceed with creating the pull request that will add the Fwk_0001 error code and its KB article link to the repository.

This pull request was created from Copilot chat.

Copilot AI changed the title [WIP] Add Fwk_0001 error code entry to helpArticles map Add Fwk_0001 help article mapping in helpArticles May 23, 2026
Copilot AI requested a review from snehaInmdr May 23, 2026 12:33
@CLAassistant
Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

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.

3 participants