Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

The Edit Article screen is accessible at /lo/knowledge/articles/:articleId/edit and loads an existing article into the knowledge base editor for updating its content, type, category, tags, or publish status.

​
Overview

The KnowledgeArticleEditorPage component is shared for both the new-article and edit-article routes. When the URL contains :articleId (and it is not "new"), isNew is false and the existing article is loaded via useKnowledgeArticle(articleId, orgId). Form fields are initialized from the existing article: title, slug, summary, content, article type, category, and tags. On submit, updateArticle from useKnowledgeArticleMutation is called. The breadcrumb shows "Edit: ${article.title}".

​
Who it’s for

Requires LO_PERMISSIONS.DASHBOARD_VIEW (lo.dashboard.view) via the shared LOViewGuard. Editing articles requires lo.knowledge.create (or a separate edit permission — confirm with SME).

​
Before you start

  • The article identified by :articleId must exist in the active organization.
  • lo.dashboard.view and lo.knowledge.create permissions required.

​
Steps

1

Navigate to Edit Article

Go to /lo/knowledge/articles/:articleId/edit or select “Edit” from an article detail page.
2

Update fields

Modify the title, slug, summary, content, type, category, or tags as needed.
3

Edit content

Use RichContentEditor to update the article body.
4

Save changes

Select the save or publish action to call updateArticle and persist changes.

​
Key concepts

  • Shared editor component: KnowledgeArticleEditorPage handles both creation and editing based on whether articleId is "new" or a real UUID.
  • updateArticle: the mutation used to persist changes to an existing article.
  • Version history: SME should confirm whether edits are versioned.

Leadership

Leadership core overview.

Governance & parity

Documentation coverage and governance.
This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/lo.tsx
  • src/cores/lo/pages/KnowledgeArticleEditorPage.tsx
  • src/cores/lo/hooks/useKnowledgeArticles.ts
  • src/cores/lo/hooks/useKnowledgeCategories.ts