@fleetbase/fleetops-engine 0.6.69 → 0.6.71

package/translations/en-us.yaml

@@ -114,6 +114,7 @@ menu:
     maintenances: Maintenances
     orchestrator: Orchestrator
     orchestrator-settings: Orchestrator Settings
+    telematics-settings: Telematics
 
 trailer:
     navigation-description: Manage towed assets, towing connections, equipment, and telematics.
@@ -1255,6 +1256,7 @@ order-config-manager:
         details: Details
         custom-fields: Custom Fields
         activity-flow: Activity Flow
+        lifecycle: Lifecycle
         entities: Entities
     details:
         details: Details
@@ -1271,6 +1273,65 @@ order-config-manager:
             delete-title: Delete this order config?
             delete-body-message: Once this order config is deleted it will not be recoverable and you will lose all configurations.
             confirm-delete: Delete
+    lifecycle:
+        title: Lifecycle
+        description: A configured lifecycle lets this order type start, complete and cancel at its own activities instead of the default dispatch lifecycle (created, dispatched, started, completed, canceled).
+        default-lifecycle: This order type uses the default dispatch lifecycle. Orders start at "created", can be dispatched to drivers and complete or cancel through the standard activities.
+        enable: Use a configured lifecycle
+        enable-help: Orders of this type start at the initial activity you choose and follow the activity flow instead of the dispatch lifecycle.
+        initial: Initial activity
+        initial-help: New orders of this type start here. Must be an activity in the flow.
+        completed: Completed activity
+        completed-help: Reaching this activity completes the order.
+        canceled: Canceled activity
+        canceled-help: Canceling an order moves it to this activity.
+        terminal: Terminal activities
+        terminal-help: No further transition is allowed after these. The completed and canceled activities are always terminal.
+        dispatch: Allow dispatch
+        dispatch-help: When off, orders of this type are never dispatched to drivers and the dispatch actions are refused.
+        strict-transitions: Strict transitions
+        strict-transitions-help: When on, an activity can only move to one of its configured next activities in the flow.
+        select-activity: Select activity
+        select-activities: Select activities
+        problems-title: Fix before saving
+        problem-initial-required: Choose the initial activity.
+        problem-no-activities: Add at least one activity.
+        problem-duplicate-code: 'An activity with the code "{code}" already exists.'
+        activities: Activities
+        activities-help: The statuses an order of this type can be in. Each activity lists the activities it can move to; the graph on the Activity Flow tab shows the same flow. Changes here are saved with the lifecycle.
+        activity-label: Label
+        activity-label-placeholder: e.g. Vehicle Assigned
+        activity-code: Code
+        activity-code-help: Stored status value. Derived from the label when left empty; cannot change once added.
+        activity-code-placeholder: e.g. vehicle_assigned
+        activity-details: Details
+        activity-details-placeholder: Shown with the activity in the timeline
+        activity-color: Colour
+        activity-next: Can move to
+        add-activity: Add activity
+        remove-activity: Remove activity
+        no-activities: No activities yet. Add the first one below; it becomes the initial activity.
+        blank-flow: Start from a blank flow
+        blank-flow-title: Remove all activities?
+        blank-flow-body: The default dispatch activities (created, dispatched, started, …) are removed so you can define your own. Nothing is saved until you click Save changes.
+        blank-flow-confirm: Remove activities
+        initial-short: initial
+        problem-missing-activity: '"{code}" is not an activity in the flow.'
+        summary: Summary
+        summary-initial: Orders start at
+        summary-completed: Completed at
+        summary-canceled: Canceled at
+        summary-terminal: Terminal
+        summary-dispatch: Dispatch
+        summary-strict: Strict transitions
+        'yes': 'Yes'
+        'no': 'No'
+        none: None
+        remove: Remove configured lifecycle
+        remove-title: Remove the configured lifecycle?
+        remove-body: Orders of this type will use the default dispatch lifecycle again. Existing orders keep their current status.
+        remove-confirm: Remove
+        saved: Lifecycle saved for {orderConfigName}.
     activity-flow:
         save-activity-flow: Save Activity Flow
         edit-activity-unique-code-warning: Activity code must be unique!
@@ -2723,6 +2784,53 @@ route-list:
     more-waypoints: more waypoints
 
 settings:
+    telematics:
+        telematics-settings: Telematics Settings
+        intro: Choose how long your organization keeps device events and position history within the limits set by your system administrator.
+        use-system-default: Use system default
+        history-policy-maximum: "Your administrator allows up to {days} days of history. Unlimited retention is not available."
+        history-policy-unlimited: Your administrator allows unlimited history. Set the retention period to 0 to keep history forever.
+        device-events: Device Events Retention
+        event-retention-days: Keep device events for (days)
+        event-retention-days-help: Events older than this are permanently deleted. Applies to telemetry updates and provider alerts alike.
+        event-compact-after-days: Strip raw payloads after (days)
+        event-compact-after-days-help: Events older than this keep their type, severity, location and normalized data, but the raw provider payload is removed. Raw payloads are the bulk of each event's size.
+        compaction-warning: Raw payloads are only stripped from events that are kept. Set this lower than the event retention or set it to 0 to disable compaction.
+        positions: Position History Retention
+        position-retention-days: Keep positions for (days)
+        position-retention-days-help: Vehicle and trailer position history older than this is permanently deleted. Route replay and history views only reach back this far.
+        inbox: Delivery Inbox & Sync Run Retention
+        processed-retention-hours: Keep processed deliveries for (hours)
+        processed-retention-hours-help: Raw provider batches are stored encrypted until processed and kept briefly for replay and diagnostics. Each batch can be close to a megabyte.
+        quarantine-retention-days: Keep quarantined deliveries for (days)
+        quarantine-retention-days-help: Batches that could not be processed stay available for inspection and replay for this long.
+        sync-run-retention-days: Keep sync run diagnostics for (days)
+        sync-run-retention-days-help: One sync run row is recorded per connection per poll. In-flight runs are never removed.
+        activity-logging: Telemetry Activity Logging
+        log-telemetry-activity: Log telemetry activity
+        log-telemetry-activity-help: Write telemetry-driven device, event and vehicle saves to the activity log. Off by default; every poll otherwise adds several activity rows per device.
+        storage-usage: System Telematics Storage Usage
+        table: Table
+        rows: Rows
+        estimated-rows: "{count} (estimated)"
+        estimated-size: Estimated size
+        oldest: Oldest row
+        not-available: n/a
+        raw-payload-rows: "{count} rows still carry raw payloads, {compactable} eligible for compaction now"
+        refresh: Refresh
+        run-cleanup: Run system cleanup
+        run-cleanup-confirm: This queues telematics cleanup across all organizations, using the saved system policy and each organization's effective history preferences. Expired records are permanently deleted and cannot be recovered. Continue?
+        cleanup-queued: Telematics cleanup has been queued across all organizations. Usage refreshes shortly; cleanup may still be running.
+        cleanup-unavailable: System-wide telematics cleanup could not be confirmed. Please try again.
+        usage-unavailable: Storage usage could not be loaded. Select Refresh to try again.
+        space-reclaim-note: Usage includes all telematics data across the system. Row counts marked as estimated use database statistics. Sizes include table data and indexes. Deleting records frees space for reuse within the database; physical disk usage may not decrease immediately.
+        settings-saved: Telematics settings saved.
+        settings-unavailable: Telematics settings could not be loaded. Please try again.
+        tables:
+            device_events: Device events
+            positions: Positions
+            telematic_deliveries: Delivery inbox
+            telematic_sync_runs: Sync runs
     avatar-management: Avatar Management
     custom-fields: Custom Fields
     notifications: