@fleetbase/fleetops-engine 0.6.69 → 0.6.71

package/addon/templates/management/vendors/index/details.hbs

@@ -1,4 +1,5 @@
 <Layout::Resource::Panel
+    @registry="fleet-ops:vendor:details"
     @resource={{@model}}
     @controller={{this}}
     @headerComponent={{component "vendor/panel-header"}}

package/addon/templates/management/vendors/index.hbs

@@ -1,5 +1,6 @@
 {{#if (eq this.layout "table")}}
     <Layout::Resource::Tabular
+        @registry="fleet-ops:vendor:table"
         @resource="vendor"
         @title={{t "resource.vendors"}}
         @searchQuery={{this.query}}
@@ -34,6 +35,7 @@
 {{else}}
     <Layout::Section::Header @title={{t "resource.vendors"}} @actionsWrapperClass="space-x-1">
         <Layout::Resource::TabularActions
+            @registry="fleet-ops:vendor:table"
             @searchQuery={{this.query}}
             @onSearch={{perform this.vendorActions.controllerSearchTask this}}
             @columns={{this.columns}}

package/addon/templates/management/vendors/integrated.hbs

@@ -1,4 +1,5 @@
 <Layout::Resource::Tabular
+    @registry="fleet-ops:integrated-vendor:table"
     @resource="integrated-vendor"
     @title={{t "resource.integrated-vendors"}}
     @searchQuery={{this.query}}

package/addon/templates/operations/orders/index/details.hbs

@@ -1,4 +1,5 @@
 <Layout::Resource::Panel
+    @registry="fleet-ops:order:details"
     @resource={{@model}}
     @controller={{this}}
     @headerComponent={{component "order/panel-header" resource=@model}}

package/addon/templates/operations/orders/index.hbs

@@ -29,6 +29,7 @@
 
 {{#if (eq this.layout "table")}}
     <Layout::Resource::Tabular
+        @registry="fleet-ops:order:table"
         @resource="order"
         @title={{t "resource.orders"}}
         @searchQuery={{this.query}}

package/addon/templates/operations/service-rates/index/details.hbs

@@ -1,4 +1,5 @@
 <Layout::Resource::Panel
+    @registry="fleet-ops:service-rate:details"
     @resource={{@model}}
     @controller={{this}}
     @headerTitle={{or @model.service_name}}

package/addon/templates/operations/service-rates/index.hbs

@@ -1,4 +1,5 @@
 <Layout::Resource::Tabular
+    @registry="fleet-ops:service-rate:table"
     @resource="service-rate"
     @title={{t "resource.service-rates"}}
     @searchQuery={{this.query}}

package/addon/templates/settings/telematics.hbs

@@ -0,0 +1,70 @@
+<Layout::Section::Header @title={{t "settings.telematics.telematics-settings"}}>
+    <Button
+        @type="primary"
+        @size="sm"
+        @icon="save"
+        @text={{t "common.save-changes"}}
+        @onClick={{perform this.saveSettings}}
+        @disabled={{or this.saveSettings.isRunning this.getSettings.isRunning (not this.settingsLoaded)}}
+        @isLoading={{or this.saveSettings.isRunning this.getSettings.isRunning}}
+        @permission="fleet-ops update telematics-settings"
+    />
+</Layout::Section::Header>
+<Layout::Section::Body class="overflow-y-scroll-i h-full">
+    <div class="container mx-auto">
+        <div class="max-w-3xl my-10 mx-auto space-y-6">
+            <InfoBlock @type="info" @icon="circle-info">
+                {{t "settings.telematics.intro"}}
+            </InfoBlock>
+
+            <ContentPanel @title={{t "settings.telematics.device-events"}} @open={{true}} @wrapperClass="bordered-classic">
+                <InputGroup>
+                    <Toggle
+                        @label={{t "settings.telematics.use-system-default"}}
+                        @isToggled={{this.useDefaultEventRetention}}
+                        @onToggle={{this.setUseDefaultEventRetention}}
+                        @disabled={{not this.settingsLoaded}}
+                    />
+                </InputGroup>
+                <InputGroup @name={{t "settings.telematics.event-retention-days"}} @helpText={{t "settings.telematics.event-retention-days-help"}}>
+                    <Input
+                        @type="number"
+                        @value={{this.eventRetentionDays}}
+                        min={{this.eventRetentionMinimum}}
+                        max={{this.eventRetentionMaximum}}
+                        disabled={{or this.useDefaultEventRetention (not this.settingsLoaded)}}
+                        class="w-full form-input"
+                    />
+                </InputGroup>
+                {{#if this.settingsLoaded}}
+                    <p class="text-xs text-gray-500 dark:text-gray-400">{{this.eventRetentionPolicyHelp}}</p>
+                {{/if}}
+            </ContentPanel>
+
+            <ContentPanel @title={{t "settings.telematics.positions"}} @open={{true}} @wrapperClass="bordered-classic">
+                <InputGroup>
+                    <Toggle
+                        @label={{t "settings.telematics.use-system-default"}}
+                        @isToggled={{this.useDefaultPositionRetention}}
+                        @onToggle={{this.setUseDefaultPositionRetention}}
+                        @disabled={{not this.settingsLoaded}}
+                    />
+                </InputGroup>
+                <InputGroup @name={{t "settings.telematics.position-retention-days"}} @helpText={{t "settings.telematics.position-retention-days-help"}}>
+                    <Input
+                        @type="number"
+                        @value={{this.positionRetentionDays}}
+                        min={{this.positionRetentionMinimum}}
+                        max={{this.positionRetentionMaximum}}
+                        disabled={{or this.useDefaultPositionRetention (not this.settingsLoaded)}}
+                        class="w-full form-input"
+                    />
+                </InputGroup>
+                {{#if this.settingsLoaded}}
+                    <p class="text-xs text-gray-500 dark:text-gray-400">{{this.positionRetentionPolicyHelp}}</p>
+                {{/if}}
+            </ContentPanel>
+        </div>
+    </div>
+    <Spacer @height="200px" />
+</Layout::Section::Body>

package/addon/utils/normalize-order-config-flow.js

@@ -1,6 +1,11 @@
 import { isArray } from '@ember/array';
 
-export function getOrderConfigFlowRootCode(flow = {}) {
+export function getOrderConfigFlowRootCode(flow = {}, initialCode = null) {
+    // A configured lifecycle (`meta.lifecycle.initial`) names its own root activity.
+    if (initialCode && flow[initialCode]) {
+        return initialCode;
+    }
+
     if (flow.created) {
         return 'created';
     }

package/app/components/admin/telematics-settings.js

@@ -0,0 +1 @@
+export { default } from '@fleetbase/fleetops-engine/components/admin/telematics-settings';

package/app/components/map/marker-card/driver.js

@@ -0,0 +1 @@
+export { default } from '@fleetbase/fleetops-engine/components/map/marker-card/driver';

package/app/components/map/marker-card/vehicle.js

@@ -0,0 +1 @@
+export { default } from '@fleetbase/fleetops-engine/components/map/marker-card/vehicle';

package/app/controllers/settings/telematics.js

@@ -0,0 +1 @@
+export { default } from '@fleetbase/fleetops-engine/controllers/settings/telematics';

package/app/routes/settings/telematics.js

@@ -0,0 +1 @@
+export { default } from '@fleetbase/fleetops-engine/routes/settings/telematics';

package/app/services/order-presentation.js

@@ -0,0 +1 @@
+export { default } from '@fleetbase/fleetops-engine/services/order-presentation';

package/app/templates/settings/telematics.js

@@ -0,0 +1 @@
+export { default } from '@fleetbase/fleetops-engine/templates/settings/telematics';

package/composer.json

@@ -1,6 +1,6 @@
 {
     "name": "fleetbase/fleetops-api",
-    "version": "0.6.69",
+    "version": "0.6.71",
     "description": "Fleet & Transport Management Extension for Fleetbase",
     "keywords": [
         "fleetbase-extension",
@@ -25,7 +25,7 @@
         "barryvdh/laravel-dompdf": "^3.1",
         "brick/geo": "0.7.2",
         "cknow/laravel-money": "^7.1",
-        "fleetbase/core-api": "*",
+        "fleetbase/core-api": ">=1.6.65",
         "geocoder-php/google-maps-places-provider": "^1.4",
         "giggsey/libphonenumber-for-php": "^8.13",
         "league/geotools": "^1.1.0",

package/docs/AFAQY.md

@@ -57,7 +57,7 @@ Existing provider interfaces and vehicle/trailer event names remain compatible.
 
 The public receiver remains `POST webhooks/telematics/afaqy?telematic=...&key=...` under the application's API prefix. A new `device.telemetry_updated` broadcast identifies the device; an open device panel reloads its authorized resource and refetches after socket reconnection. Company broadcast identity comes from the persisted asset, not a worker session. Map movement uses the existing vehicle/trailer events, rejects older source timestamps, and reloads visible telemetry assets after socket reconnection with at most five concurrent requests.
 
-Configure shared queues, retention, limits, and freshness under `telematics.telemetry` using `server/config/telemetry.php`. `TELEMATICS_BATCH_SIZE` controls units per ingestion delivery (default 100); `TELEMATICS_REQUEST_TIMEOUT_SECONDS` controls the bounded polling request timeout (default 45 seconds). AFAQY's adapter switches and optional queue overrides remain under `telematics.afaqy` in `server/config/afaqy.php`. Defaults: two MiB per webhook, 10,000 pending deliveries per connection, processed payload retention 24 hours, quarantine retention seven days, stale-position thresholds 120 seconds with ignition on and 600 seconds with ignition off/unknown. Each device's metadata records the effective threshold. Connection status categories remain unchanged.
+Configure shared queues, retention, limits, and freshness under `telematics.telemetry` using `server/config/telemetry.php`. `TELEMATICS_BATCH_SIZE` controls units per ingestion delivery (default 100); `TELEMATICS_REQUEST_TIMEOUT_SECONDS` controls the bounded polling request timeout (default 45 seconds). AFAQY's adapter switches and optional queue overrides remain under `telematics.afaqy` in `server/config/afaqy.php`. Defaults: two MiB per webhook, 10,000 pending deliveries per connection, stale-position thresholds 120 seconds with ignition on and 600 seconds with ignition off/unknown. Retention (processed payloads 24 hours, quarantined deliveries seven days, device events 30 days, positions 90 days) is applied by `fleetops:prune-telematics-data`. Administrators configure retention policy, logging, system storage diagnostics and system cleanup in Admin → Fleet-Ops Config → Telematics. Organizations choose only event and position history preferences within those limits in Fleet-Ops → Settings → Telematics; config values are the fallback. See `docs/TELEMETRY_ARCHITECTURE.md` § Retention. Each device's metadata records the effective threshold. Connection status categories remain unchanged.
 
 ## Incident verification
 

package/docs/TELEMATICS_QUEUES.md

@@ -14,7 +14,7 @@ nothing changes: every job and broadcast stays on the same queue as before.
 | Setting | Default | Work routed |
 | --- | --- | --- |
 | `TELEMATICS_POLL_QUEUE` | `default` | Scheduled and manual polls (`PollTelematicTelemetry`), legacy device discovery (`SyncTelematicDevicesJob`), and queued connection tests (`TestTelematicConnectionJob`). |
-| `TELEMATICS_INGESTION_QUEUE` | `default` | Applying polled or pushed positions (`ProcessTelematicDelivery`), including jobs re-queued by `fleetops:drain-telematic-inbox` and manual replays. |
+| `TELEMATICS_INGESTION_QUEUE` | `default` | Applying polled or pushed positions (`ProcessTelematicDelivery`), including jobs re-queued by `fleetops:drain-telematic-inbox` and manual replays, and on-demand retention runs (`PruneTelematicsDataJob`, queued by "Run system cleanup" in Admin → Fleet-Ops Config → Telematics). |
 | `TELEMATICS_BROADCAST_QUEUE` | unset | Live-map broadcasts created by telematics ingestion: `DeviceTelemetryUpdated`, and `VehicleLocationChanged` / `TrailerLocationChanged` when a device is attached. When unset, broadcasts use the queue connection's default queue. |
 
 `TELEMATICS_BROADCAST_QUEUE` affects only broadcasts that telematics ingestion

package/docs/TELEMETRY_ARCHITECTURE.md

@@ -48,11 +48,82 @@ persistence. The performance requirement did not justify those dependencies.
 ## Tradeoffs
 
 Three shared tables separate run-level diagnostics, high-volume delivery retention,
-and connection-level secrets with different lifetimes. Provider-specific protocol
+and connection-level secrets with different lifetimes (see Retention below). Provider-specific protocol
 classes remain appropriate. Capability opt-in avoids silently changing every
 existing integration's ingestion or webhook behavior. Production throughput and
 real AFAQY payload verification remain separate deployment gates.
 
+## Retention
+
+Every poll writes one `device_events` row, one `positions` row and a delivery
+envelope per batch for each reporting device. Without a ceiling those tables grow
+until the disk fills, so retention is enforced by `fleetops:prune-telematics-data`
+(scheduled every fifteen minutes, `withoutOverlapping(14)`) using a per-company
+policy resolved by `Support\Telematics\Retention\RetentionPolicy`:
+
+| Layer | Source | Where it is edited |
+|---|---|---|
+| Package config | `server/config/telemetry.php` | deployment |
+| System policy | setting `fleet-ops.telematics-settings` | Admin console → Fleet-Ops Config → Telematics |
+| Company history preferences | `company.<uuid>.fleet-ops.telematics-settings` | Fleet-Ops → Settings → Telematics |
+
+Defaults: device events 30 days, raw payload/meta stripped ("compacted") after
+7 days, positions 90 days, processed deliveries 24 hours, quarantined deliveries
+7 days, sync runs 7 days. Organizations can choose only device event and position
+history retention, or inherit the system defaults. Administrators own raw payload,
+delivery, sync-run retention and telemetry activity logging.
+
+`max_event_retention_days` and `max_position_retention_days` constrain every
+organization's history, including inherited defaults. A maximum of `0` allows
+unlimited history; a history preference of `0` keeps records forever only while
+that maximum is unset. Setting a finite maximum replaces saved unlimited or longer
+preferences with that maximum. Missing preferences continue to inherit. Values
+are also clamped to `RetentionPolicy::LIMITS`.
+
+Admin storage diagnostics cover the entire system, including organizations the
+administrator does not belong to. System cleanup queues work for every
+organization plus orphaned records, with each organization's effective policy
+applied independently. Storage sizes include table data and indexes; database row
+estimates are labeled. Cleanup is asynchronous, so refreshing usage does not mean
+all queued work has finished.
+
+Manual system cleanup requires an asynchronous queue connection and a worker for
+`telematics.telemetry.ingestion_queue`. A synchronous or disabled queue is rejected
+instead of running every organization's cleanup inside the HTTP request.
+
+Deploy the frontend and backend together and reload Octane and queue workers after
+updating the backend. In linked development checkouts, Octane's watch paths must
+include `packages/fleetops/server`; watching only the host API directory leaves
+previously loaded controllers and policies running.
+
+Rules the sweep follows:
+
+- Hard deletes only. The models soft-delete, so `delete()` would grow the table;
+  rows already soft-deleted are purged regardless of age.
+- Bounded work: at most `--max-batches` (default 50) statements of `--batch-size`
+  (default 1000) rows per table per company per run. A capped run is normal; the
+  next tick continues. Operators can catch up faster off-peak with
+  `php artisan fleetops:prune-telematics-data --max-batches=500 --no-lock`.
+- Compaction keeps the event (type, severity, location, normalized `data`) and
+  nulls `payload` and `meta`, which hold the bulk of each row.
+- `telematic_deliveries` and `telematic_sync_runs` carry no company; they are
+  resolved through the company's connections (including trashed ones). In-flight
+  sync runs (`fetching`, `ingesting`) are recovered by the drain, never expired.
+- Rows whose company or connection no longer exists are swept with the system
+  defaults.
+- Migrations add `(company_uuid, created_at)` on `device_events` and `positions`
+  and `(telematic_uuid, updated_at)` on `telematic_sync_runs`; on multi-GB tables
+  run them in a maintenance window.
+- Deleting rows frees space inside InnoDB files, not on disk. Run
+  `OPTIMIZE TABLE device_events` (requires `innodb_file_per_table`) off-peak to
+  return it to the operating system.
+
+Two write-amplification fixes accompany the sweep: `device_events.meta` stores only
+the normalized block (the raw unit lives once, in `payload`), and telemetry-driven
+saves run inside `activity()->withoutLogs()` unless the system administrator enables
+"Log telemetry activity". `DrainTelematicInbox` now only recovers deliveries and
+finishes interrupted runs.
+
 ## Adding an adapter
 
 Implement `TelemetryProviderInterface` alongside the existing provider contract.

package/extension.json

@@ -1,6 +1,6 @@
 {
     "name": "Fleet-Ops",
-    "version": "0.6.69",
+    "version": "0.6.71",
     "description": "Fleet & Transport Management Extension for Fleetbase",
     "repository": "https://github.com/fleetbase/fleetops",
     "license": "AGPL-3.0-or-later",

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@fleetbase/fleetops-engine",
-    "version": "0.6.69",
+    "version": "0.6.71",
     "description": "Fleet & Transport Management Extension for Fleetbase",
     "fleetbase": {
         "route": "fleet-ops"
@@ -44,8 +44,8 @@
     },
     "dependencies": {
         "@babel/core": "^7.23.2",
-        "@fleetbase/ember-core": "^0.3.24",
-        "@fleetbase/ember-ui": "^0.4.3",
+        "@fleetbase/ember-core": "^0.3.25",
+        "@fleetbase/ember-ui": "^0.4.5",
         "@fleetbase/fleetops-data": "^0.2.2",
         "@fleetbase/leaflet-routing-machine": "^3.2.17",
         "@fortawesome/ember-fontawesome": "^2.0.0",

package/server/config/telemetry.php

@@ -13,8 +13,20 @@ return [
     'batch_size'                => env('TELEMATICS_BATCH_SIZE', 100),
     'max_payload_bytes'         => 2097152,
     'max_pending_deliveries'    => 10000,
+    // Administrators control infrastructure retention and activity logging.
+    // Companies may choose event/position history retention within the maximums.
+    // A maximum of 0 imposes no cap and permits unlimited history (retention 0).
     'processed_retention_hours' => 24,
     'quarantine_retention_days' => 7,
+    'sync_run_retention_days'   => 7,
+    'event_retention_days'      => 30,
+    'event_compact_after_days'  => 7,
+    'position_retention_days'   => 90,
+    'max_event_retention_days'  => 0,
+    'max_position_retention_days' => 0,
+    'log_telemetry_activity'    => false,
+    'prune_batch_size'          => 1000,
+    'prune_max_batches'         => 50,
     'stale_engine_on_seconds'   => 120,
     'stale_engine_off_seconds'  => 600,
 ];

package/server/migrations/2026_09_23_000001_add_retention_index_to_device_events.php

@@ -0,0 +1,40 @@
+<?php
+
+use Fleetbase\FleetOps\Support\Database\TableIndexes;
+use Illuminate\Database\Migrations\Migration;
+use Illuminate\Database\Schema\Blueprint;
+use Illuminate\Support\Facades\Schema;
+
+/**
+ * Supports the bounded retention sweep in fleetops:prune-telematics-data,
+ * which ranges over these columns for every company on every run.
+ */
+return new class extends Migration {
+    private const TABLE   = 'device_events';
+    private const INDEX   = 'device_events_company_created_at_index';
+    private const COLUMNS = ['company_uuid', 'created_at'];
+
+    public function up(): void
+    {
+        if (!Schema::hasTable(self::TABLE) || !Schema::hasColumns(self::TABLE, self::COLUMNS)) {
+            return;
+        }
+
+        if (TableIndexes::covers(self::TABLE, self::COLUMNS)) {
+            return;
+        }
+
+        Schema::table(self::TABLE, fn (Blueprint $table) => $table->index(self::COLUMNS, self::INDEX));
+    }
+
+    public function down(): void
+    {
+        if (!Schema::hasTable(self::TABLE)) {
+            return;
+        }
+
+        if ((TableIndexes::for(self::TABLE)[self::INDEX] ?? null) === self::COLUMNS) {
+            Schema::table(self::TABLE, fn (Blueprint $table) => $table->dropIndex(self::INDEX));
+        }
+    }
+};

package/server/migrations/2026_09_23_000002_add_retention_index_to_positions.php

@@ -0,0 +1,40 @@
+<?php
+
+use Fleetbase\FleetOps\Support\Database\TableIndexes;
+use Illuminate\Database\Migrations\Migration;
+use Illuminate\Database\Schema\Blueprint;
+use Illuminate\Support\Facades\Schema;
+
+/**
+ * Supports the bounded retention sweep in fleetops:prune-telematics-data,
+ * which ranges over these columns for every company on every run.
+ */
+return new class extends Migration {
+    private const TABLE   = 'positions';
+    private const INDEX   = 'positions_company_created_at_index';
+    private const COLUMNS = ['company_uuid', 'created_at'];
+
+    public function up(): void
+    {
+        if (!Schema::hasTable(self::TABLE) || !Schema::hasColumns(self::TABLE, self::COLUMNS)) {
+            return;
+        }
+
+        if (TableIndexes::covers(self::TABLE, self::COLUMNS)) {
+            return;
+        }
+
+        Schema::table(self::TABLE, fn (Blueprint $table) => $table->index(self::COLUMNS, self::INDEX));
+    }
+
+    public function down(): void
+    {
+        if (!Schema::hasTable(self::TABLE)) {
+            return;
+        }
+
+        if ((TableIndexes::for(self::TABLE)[self::INDEX] ?? null) === self::COLUMNS) {
+            Schema::table(self::TABLE, fn (Blueprint $table) => $table->dropIndex(self::INDEX));
+        }
+    }
+};

package/server/migrations/2026_09_23_000003_add_retention_index_to_telematic_sync_runs.php

@@ -0,0 +1,40 @@
+<?php
+
+use Fleetbase\FleetOps\Support\Database\TableIndexes;
+use Illuminate\Database\Migrations\Migration;
+use Illuminate\Database\Schema\Blueprint;
+use Illuminate\Support\Facades\Schema;
+
+/**
+ * Supports the bounded retention sweep in fleetops:prune-telematics-data,
+ * which ranges over these columns for every company on every run.
+ */
+return new class extends Migration {
+    private const TABLE   = 'telematic_sync_runs';
+    private const INDEX   = 'telematic_sync_runs_telematic_updated_at_index';
+    private const COLUMNS = ['telematic_uuid', 'updated_at'];
+
+    public function up(): void
+    {
+        if (!Schema::hasTable(self::TABLE) || !Schema::hasColumns(self::TABLE, self::COLUMNS)) {
+            return;
+        }
+
+        if (TableIndexes::covers(self::TABLE, self::COLUMNS)) {
+            return;
+        }
+
+        Schema::table(self::TABLE, fn (Blueprint $table) => $table->index(self::COLUMNS, self::INDEX));
+    }
+
+    public function down(): void
+    {
+        if (!Schema::hasTable(self::TABLE)) {
+            return;
+        }
+
+        if ((TableIndexes::for(self::TABLE)[self::INDEX] ?? null) === self::COLUMNS) {
+            Schema::table(self::TABLE, fn (Blueprint $table) => $table->dropIndex(self::INDEX));
+        }
+    }
+};