Skip to content

Logistics Workspace Wiki

The single runtime authority for the operator user manual is T_WIKI_PAGE. Page UUID, Client scope, slug, title, menu binding, body, metadata and audit timestamps are all managed in the same row. Screen images live in the WIKI_ASSET relation of T_FILE and in the existing file object store, and Markdown references only wiki-asset://<UUID>.

The METADATA JSON groups only these display attributes:

  • schemaVersion, category, audience, summary
  • access, sortOrder, published

UUID, Client, slug, title, menu binding, body and the audit columns are used for lookup, constraints and concurrency control, so they stay as ordinary columns. The former URL column was removed because it was a duplicate value derived from the slug.

The operator manual is edited in the Wiki editing screen; after saving, reopen the same UUID to confirm. A specific company name is not used in the title, body, category, audience or slug. Tenant or parameter differences are expressed as the page's Client scope, its menu binding and a neutral procedure description, never as a company name.

The development specifications are generated from the nine system specifications and their detail sources and displayed read-only. The operator manual database and the generated specification copy never overwrite each other.

For the current document roles see the documentation map. For why the Workspace Wiki runtime is separated and what the historical baseline is replaced by, see Decision 0022.

Wiki Structure Design

The Wiki home separates the operator user manual from the read-only development specifications. The operator manual is grouped by category and each page opens at /wiki/<slug>. The Booking procedure is not a separate duplicate manual: it is managed on a single page, Shipping and documents → Booking List. The overall UAT linkage is shown in Order-to-Billing Process Flow, which links on to the Basic and Booking pages for detail.

Verification

  • DB: per-Client UUID/slug uniqueness, JSON_VALID(METADATA), and the relation between asset UUIDs in the body and T_FILE.
  • API: the catalogue does not carry bodies; Markdown/HTML is returned only for the selected page.
  • Screen: title, steps and image loading are confirmed with a real logged-in Client and role.
  • Git, deployment and Production application are separate results from local DB and screen verification.

Source: new-system/docs/wiki/README.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.