Antylogic
DemoApp login

399 operational guides

Docs sections
DocsDocumentation
Device

Open A Legacy Help Article Link In The App

Open an older in-app documentation link that uses an articleId query parameter. In an authenticated session, Antylogic loads the current documentation index, resolves the legacy id in the current language, rewrites the route to the canonical section and article, and shows the normal read-only article view.

In this article

Use this guide when support, customer success, or operators need to confirm that an older in-app help link still opens the right Documentation article after help content has moved to canonical section and article slugs.

In the GB English demo session, antylogic://docs?articleId=en-access-users-create-location-internal resolves to the Access article Create an Internal Location User.

Before you start

  • The operator is signed in to the Antylogic app, for example as Harbor Demo User in the GB English demo session.
  • The account is active and is not blocked by pending deletion.
  • The link includes a non-empty articleId query parameter, such as antylogic://docs?articleId=en-access-users-create-location-internal.
  • The app can load the authenticated documentation index for the current language, screen size, and theme.
  • The target article exists in the loaded locale index with a matching article slug or slugified article id.

Instructions

  1. 1.

    Open the legacy help link

    Open the query-string link antylogic://docs?articleId=en-access-users-create-location-internal from an authenticated app session. Use articleId as a query parameter; a path such as antylogic://docs/en-access-users-create-location-internal is not the legacy article-id format.

  2. 2.

    Let Documentation resolve the article

    The Documentation screen loads the authenticated docs index for the current language, platform, and theme. It trims and normalises the legacy articleId, then compares it locally with the loaded article summaries.

  3. 3.

    Confirm the resolved article

    When a matching summary is found, the app opens the canonical article detail. In the GB English demo, the Access section opens and the article title Create an Internal Location User is visible.

  4. 4.

    Handle links that do not resolve

    If the index is loading, wait for Documentation to finish. If the index fails, use the docs loading error. If the legacy id does not match the current locale index, no detail article is loaded and the article area asks the operator to select an article.

Validations and limits

  • The app stays in the authenticated App area instead of showing Login.
  • articleId is resolved locally from the loaded index and is not sent to the backend.
  • Matching is limited to the article summary slug or the slugified article summary id.
  • The detail request uses the canonical path /api/app/docs/access/en-access-users-create-location-internal.
  • After a match, navigation state is normalised to sectionSlug and articleSlug and articleId is cleared.
  • A canonical sectionSlug and articleSlug pair takes priority over articleId, even when the pair is invalid.
  • An English legacy id may not resolve while the app is using the Spanish docs index.
  • Unmatched legacy ids currently show the generic select-article state rather than a dedicated not-found message.

Expected result

The older help link opens the normal read-only Documentation article for the current locale. The route is rewritten to the canonical section and article slugs, and no support ticket, article edit, or operational domain data is created.

Related articles