@meshmakers/octo-meshboard 3.4.1490 → 3.5.0

package/README.md

@@ -278,6 +278,29 @@ interface TableWidgetConfig {
 }
 ```
 
+**Texts (AB#5622).** The list inside the table (`mm-list-view`) takes its texts from
+`MESHBOARD_MESSAGES` — "No records available.", pager texts, toolbar labels — merged over the
+English defaults; the host sets them once (fixed object or a signal for a runtime language switch):
+
+```typescript
+providers: [
+  provideMeshBoard({ messages: { tableList: { noRecords: 'Keine Einträge vorhanden.', pagerItemsPerPage: 'Einträge pro Seite' } } }),
+  // or, when the widgets are registered lazily (no provideMeshBoard()):
+  provideMeshBoardMessages(appMeshBoardMessages),
+]
+```
+
+`tableNotConfigured` translates the placeholder of an unconfigured table.
+
+**Enum labels (AB#5622).** `MESHBOARD_LABEL_RESOLVER` (same pattern as the entity forms'
+`ENTITY_FORM_LABEL_RESOLVER`) translates enum values: `(request) => string | null | undefined`
+with `request = { kind: 'tableCell' | 'chartCategory', ckTypeId?, attribute, value, valueType?,
+defaultText }`; `null` / `undefined` / `''` keep `defaultText` (today's text), a throwing resolver
+is logged once and ignored. Tables offer string cells of text columns (persistent-query columns
+only when their value type is `ENUM`); pie / donut charts offer every category — the resolved text
+is the slice name in data labels, legend and tooltips, the status colour still follows the raw
+value. A resolver that reads a signal re-labels the charts when it changes.
+
 ### Pie Chart Widget
 Displays data as pie or donut chart.
 
@@ -291,9 +314,25 @@ interface PieChartWidgetConfig {
   showLegend?: boolean;
   legendPosition?: 'top' | 'bottom' | 'left' | 'right';
   filters?: WidgetFilterConfig[];
+  categoryColors?: Record<string, string>;            // AB#5622
+  labelPosition?: 'inside' | 'outside' | 'none';      // AB#5622
+  hideLabelsBelowPercent?: number;                    // AB#5622
 }
 ```
 
+Colours and labels (AB#5622): every slice gets an explicit colour — a `categoryColors` entry
+(key = raw category value, case-insensitive, or the displayed label; value = hex / CSS colour,
+custom property `--brand-paid` / `var(--brand-paid, #2fb37a)`, or a status name `success` /
+`warning` / `error` / `info`), else the status colour of a well-known state, else the theme
+palette colour of its position (`chartSeriesColors()`: `--theme-chart-1…12`, then
+`--kendo-chart-series-1…12`, then `--kendo-color-series-a…f`, then a fixed palette; unresolved or
+invalid tokens are skipped, so no slice falls back to black in dark mode). The palette is part of
+the theme signature, so a live theme switch re-colours the chart without a redraw loop.
+`labelPosition` (labels mode only) maps to Kendo `outsideEnd` (theme-coloured connector lines) /
+`insideEnd` / hidden; `hideLabelsBelowPercent` drops the labels of small slices so neighbours do
+not overlap. All three are optional, written to the board JSON only when set, and edited in the
+config dialog (Label Position, Hide labels below, Category Colours).
+
 Display rules (`utils/chart-categories.ts`): enum-style categories read as words (`RESOLVE_FAILED` →
 "Resolve failed"); well-known state categories get the theme status colours (`--theme-status-*`,
 then `--kendo-color-*`; e.g. Resolve failed / Error → error, Available / Online → success,
@@ -420,11 +459,15 @@ providers: [
 
 | Type | Label | Shows | Gate (per check / KPI) | Persisted `config` |
 |------|-------|-------|------------------------|--------------------|
-| `attentionList` | Attention List | Findings, errors first: CK models in ResolveFailed, adapters in error / offline > 10 min, failed pipeline executions in 24 h above a threshold, pools not registered, features enabled but not installed, plus host checks (Refinery Studio: secrets needing re-entry) | each provider: AdminPanelManagement / CommunicationManagement + `System.Communication` / TenantManagement | `{ "providerIds"?: string[], "maxItems"?: number, "showExplain"?: boolean }` — no `providerIds` = all checks, including ones added later |
+| `attentionList` | Attention List | Findings, errors first: CK models in ResolveFailed, adapters in error / offline > 10 min, failed pipeline executions in 24 h above a threshold, deployment sites not registered (provider id `pools-unregistered`, kept stable for persisted `providerIds`), features enabled but not installed, plus host checks (Refinery Studio: secrets needing re-entry) | each provider: AdminPanelManagement / CommunicationManagement + `System.Communication` / TenantManagement | `{ "providerIds"?: string[], "maxItems"?: number, "showExplain"?: boolean }` — no `providerIds` = all checks, including ones added later |
 | `adapterStatus` | Adapter Status | Adapters online / expected to run (shared rule `utils/adapter-online.ts`) | CommunicationManagement + `System.Communication` | `{ "showDetail"?: boolean }` |
 | `ckModelState` | CK Model State | CK models available / all; ResolveFailed = error, importing = warning | AdminPanelManagement | `{ "showDetail"?: boolean }` |
 | `recentItems` | Recent Items | The viewer's recently opened pages, entities and boards (most recent first, glyph, kind, relative time as `<time>`), real links; optional "⌘K shows the same list" | none — per user, from the host's `COCKPIT_RECENT_ITEMS`; without it "Not available" + collapsed | `{ "maxItems"?: number }` (default 8, 1–20) |
 | `pipelineExecutions` | Pipeline Executions 24 h | Executions of all data flows, failed count, hourly sparkline (same counting as the Studio's Data Flows list) | CommunicationManagement + `System.Communication` | `{ "showDetail"?: boolean, "showSparkline"?: boolean }` |
+| `tenantCount` | Tenants | Child tenants of the tenant (on the system tenant: all tenants), first ids; links `tenants` | TenantManagement | `{ "showDetail"?: boolean }` |
+| `blueprintUpdates` | Blueprint Updates | Installed blueprints with a newer catalog version (warning); service-managed `System.*` ones only in the detail; links `blueprints` | AdminPanelManagement | `{ "showDetail"?: boolean }` |
+| `servicesHealth` | Services Healthy | Identity, Asset Repository, Bot, Communication Controller (when installed) healthy / all; unhealthy or silent = error, degraded = warning; links `serviceHealth` of the first problem | none | `{ "showDetail"?: boolean }` |
+| `versionInfo` | Version | The host's versions (`COCKPIT_VERSION_SOURCE` / `provideCockpitWidgetHost({ versions })`), first = value; no link | none — without the source "Not available" + collapsed | `{ "showDetail"?: boolean }` |
 
 - **Role abstraction.** The library never imports the host's auth: `COCKPIT_VIEWER_ACCESS`
   (`isInRole(role)`) answers role checks, `CkModelService.isModelAvailable` the CK models.
@@ -436,8 +479,11 @@ providers: [
   close up, `collapseEmptyRows`). An attention list never claims "All clear" without visible checks.
 - **Errors** never show raw messages: tiles say "The figure could not be loaded." (details in the console).
 - **Links.** Findings and KPI tiles carry semantic `CockpitLinkTarget`s (`adapter`, `adapters`,
-  `pool`, `pools`, `dataFlows`, `ckModels`, `tenantSettings`, `secretsReEntry`); the host's
-  `COCKPIT_LINK_RESOLVER` maps them to URLs, `null` drops the chip. Host providers may also link
+  `deployment-site`, `deployment-sites`, `dataFlows`, `ckModels`, `tenantSettings`, `secretsReEntry`;
+  `pool` / `pools` are the deprecated pre-System.Communication-4.x aliases); the host's
+  `COCKPIT_LINK_RESOLVER` maps them to URLs, `null` drops the chip. When the resolver answers `null`
+  for a deployment-site kind, the context asks once more with the legacy alias
+  (`legacyCockpitLinkTarget`), so hosts that only map `pool` / `pools` keep their links (AB#5842). Host providers may also link
   straight to their own pages (AB#5622): `{ kind: 'route', path, queryParams? }` — `path` is a URL
   path or router commands (`['/', tenantId, 'documents']`), navigated with `routerLink` +
   `queryParams`; relative paths resolve against the route that renders the board. The resolver
@@ -467,6 +513,13 @@ providers: [
   error from `errorFailed` failures (default 1,000) or a failure share of `errorRatio` (default
   0.2); `null` disables an error rule. Override with `{ provide: COCKPIT_FAILED_EXECUTIONS_OPTIONS,
   useValue: { minFailed: 50 } }`. Links to `dataFlows` (the list has no "failed only" filter).
+- **System cockpit checks** (AB#5558). `services-unhealthy` (one finding per platform service
+  that is not Healthy, links `serviceHealth`) and `blueprint-updates` (info, count badge, links
+  `blueprints`; AdminPanelManagement) are visible on the system tenant only
+  (`CockpitContextService.isSystemTenant`, from `systemTenantId` of the platform configuration,
+  `octosystem` without it) — tenant cockpits are unchanged. Texts: `attentionService*`,
+  `attentionBlueprintUpdates*`, `kpiTenants*`, `kpiBlueprints*`, `kpiServices*`, `kpiVersion*`
+  (optional members). Seeded by `System.UI.SystemCockpit` ≥ 1.1.0.
 - **Data.** Lean documents with explicit fields in `graphQL/cockpit*.graphql`; the adapter states
   and the data flow executions are shared per tenant for 10 s between the KPI and the attention
   list (`CockpitAdapterStatesService`, `CockpitDataFlowExecutionsService`).