SIGNALS Docs
Exit Reader View
100%
Theme

Reader View

Flightcases & Kits

Barcoded flightcase pack/seal/dispatch/return lifecycle, gate surface, itinerary spine, and warehouse UI.

Overview

Flightcases group barcoded assets into dispatchable units — lighting kits, road cases, hybrid kits, and transport boxes. The lifecycle covers configuration, pack/unpack, seal/unseal, dissolve, dispatch, return, and repack.

Warehouse UI routes:

Route Purpose
/flightcases Flightcase index
/flightcases/{flightcase} Detail and status
`/flightcases/{flightcase}?register={manifest holding
/flightcases/{flightcase}/tabs/{pluginTab} Native plugin tab host
/flightcases/{flightcase}/pack Pack UI
/flightcases/{flightcase}/repack/{rental} Repack-on-return for a rental

Catalogue item-level flightcase templates configure default pack lists and policies at /catalogue-items/{catalogue_item} (flightcase config tab) and via GET/PUT /api/v1/catalogue_items/{catalogue_item}/flightcase_template.

Flightcase modes

Mode Behaviour
Kit Contents held from individual availability as a unit
Hybrid Mixed fixed/variable contents
Transport Road case / flight case; supports dissolve-on-dispatch

Lifecycle

open → sealed → dispatched → returned → (repack) → open
Event Description
Pack / unpack Add or remove barcoded items while open
Seal / unseal Lock flightcase with compliance manifest
Dissolve Manual dissolve with warn-and-resolve for nested packing
Dissolve-on-dispatch Transport mode — flightcase dissolves when dispatched
Dispatch / return Kit dispatch and kit return tie flightcase to a rental
Repack-on-return Editable scan mode repack after return

Temporary flightcases can be created ad hoc for one-off jobs (POST /api/v1/flightcases/temporary).

Compliance manifest

Sealed flightcases carry a compliance manifest listing packed serial numbers. Retrieve via GET /api/v1/flightcases/{flightcase}/compliance.

Dissolve-on-dispatch

Transport flightcases configured for dissolve-on-dispatch unpack their contents into the dispatch workflow automatically — the flightcase record completes while assets move to the rental.

Repack-on-return

After kit return, repack-on-return lets operators scan items back into the flightcase (POST /api/v1/flightcases/repack/start and per-item repack). UI trigger at /flightcases/{flightcase}/repack/{rental}.

Plugin and webhook seams

Flightcase pack, seal, dissolve, dispatch, return, and repack events appear in the webhook catalogue for integrations (barcode scanners, WMS, etc.).

Using it in the app

Screen Route Nav Gate
Flightcases index /flightcases Warehouse → Flightcases ("Cases, flightcases & kits") flightcases.view
Flightcase show /flightcases/{flightcase} — flightcases.view + warehouse
Pack /flightcases/{flightcase}/pack — flightcases.pack
Repack /flightcases/{flightcase}/repack/{rental} — flightcases.create + rentals.edit
Catalogue item flightcase config /catalogue-items/{catalogue_item}/flightcase-config Catalogue item tab (barcoded catalogue items) View all; save needs flightcases.manage_templates

Catalogue item flightcase config tab

Tab: Flightcase Config (barcoded catalogue items only)

Field Purpose
Flightcaseable Whether the catalogue item can act as a flightcase
Availability Mode Kit / Hybrid / Transport behaviour
Check-in Mode How returns are processed
Max Nesting Depth Nested flightcase limit
Repack on Return Enable repack workflow after kit return
Warehouse Addable at Dispatch Allow adds during dispatch
Warehouse Add Default Charge Default charge for warehouse adds
Template Slots Catalogue item, quantity, binding for default pack list

Save Flightcase Config requires flightcases.manage_templates. Without it the form is view-only with a warning banner.

Flightcases index

Scan barcode field resolves an existing flightcase or housing — may navigate to show, open pack, or start repack.

Filters: search, warehouse, mode chips (Transport / Kit / Hybrid), status chips (defaults to Active)

Table: Barcode, Name, Status, Mode, Warehouse, Type (Temporary / Catalogue item-backed), Items

Scan-create and repack-from-return flows require flightcases.create and rentals.edit respectively.

Pack page

Route: /flightcases/{flightcase}/pack

Scan-to-pack workflow while the flightcase is open:

  • Strict checklist vs free list scan modes (configured on the flightcase)
  • Inline conflict dialog when a scan hits an asset already elsewhere — options include transfer, auto-return, and nesting resolution
  • Seal when packing is complete

The pack scan field is wrapped in a visual dock (s-fcbrief-dock s-scan-mod is-docked) that matches the docked scan-module presentation. Pack still uses its own scanItem seam — there is no flightcase_pack scan context, so the committed scan-module partials are not included and no new mutation path is invented.

Flightcase show

Actions are policy- and lifecycle-gated. The identity band keeps one refusal-carrying primary dispatch verb plus Other actions. A compact stage row shows only workflows valid now: Return kit, Mark verified, Flag damage on return, or Transfer item out. Invalid stage verbs stay visible with their reason in Other actions; Dissolve also lives there. Pack, Repack session, Seal/Unseal, Print, and plugin actions remain in the existing header controls. Rental, packed-asset, and target-flightcase choices use entity search rather than raw identifiers.

The Overview is a year-2 operational brief (no stage slider). Three headline cards answer Can it leave?, Manifest packed-of-expected, and Holding stock; each opens an addressable register through ?register=manifest|holding|contents. Registers move focus on open, return it to the originating hero on close, and close with Escape. The ranked four-question briefing uses glyph-and-word CLEAR / WATCH / ACT verdicts, expandable inline evidence, arrow-key movement, and supporting-register handoffs.

The identity band carries sealed-by/at and due-out-to. One primary button uses the gate payload's refusal-carrying label (Dispatch to {rental} or Blocked — …). A four-gate strip (manifest / barcoded / weight / certs) shows localized glyph-and-word verdicts (PASS / WARNS / BLOCKS / DECIDE). Clicking a gate opens its reason and clearing handoffs; gate bands do not duplicate mutating workflows. When the gate has failing manifest rows, it filters to their failing_row_ids.

The manifest register is the full six-column view: Item, glyph-and-word Status, Qty, Value, Weight, and Last scanned. Status is derived from packed against expected (PACKED / MISSING / EXTRA), with a persistent legend and failing-row tones. Value is the catalogue item's replacement value times the packed quantity and appears only with costs.view; it is never presented as insured value. Weight is extended by packed quantity. Last scanned is the time the item was packed or scanned in. The narrower on-page manifest reuses the same presentation facts. The nested contents tree lives only in the Contents register.

The rail keeps its panels drawn even when facts are absent. Bound to lists customer, out, back, warehouse, and vehicle. Physical shows known gross weight (shown as At least when any weight is missing), drawn absence for dimensions, the housing asset, and replacement value behind cost visibility. Holding stock, Template variance, Scan mode, and the existing Lifecycle audit timeline (needs action-log.view) remain open panels with skeleton-backed absent states. Template variance discloses detail when at least five sealed packs share the catalogue item.

Itinerary is a route-backed tab on the same show route (?surface=itinerary). It consumes the six-leg s-brief-tl-* spine (yard sealed → dispatch → on hire → return → check-in → next job) with localized verdict words, next-leg readiness, slack chips, and requirements. It hands off to the Overview Contents register rather than rendering a second tree. A dispatch that needs rental amendments still opens the amendment prompt on this tab — the prompt sits outside the surface conditional so it is never a silent no-op. Overview and Itinerary show manifest-line and itinerary-leg counts; plugins can add true tabs through flightcase.detail.tabs, hosted at the plugin-tab route.

Overview registers: Manifest, Holding stock, Contents tree

Rail panels: Holding stock, Bound to, Physical, Template variance, Scan mode, Lifecycle

Flag damage on return: after kit return, a Flag damage on return panel lists returned assets. Flagging an asset raises a repair for it (reason: Damage) and holds it out of availability. Contents still packed in the kit remain reserved until unpacked; the conflict policy rejects flagging still-packed components.

Dissolve-on-dispatch: transport flightcases configured for this mode dissolve automatically when dispatched from a rental — contents move to the dispatch workflow; the flightcase record completes.

Seal / unseal: sealed flightcases carry a compliance manifest; unseal prompts for a reason.

Flightcase contents overrun scan

The scheduled command signals:scan-flightcase-overruns (daily) detects still-packed sub-hired contents past their virtual-stock return deadline. It is notification-only — it fires a manager notification once per membership via the contents_overrun_notified_at marker and never mutates stock or raises repairs.

Repack-on-return

Route: /flightcases/{flightcase}/repack/{rental}

Editable scan mode after kit return — scan items back into the flightcase with lineage preserved. Also reachable from the index scan box ("start repack from return" modal).

Rental Assets tab

Route: /rentals/{id}/assets (visible for Order or Quote+Held)

Sub-tabs: Functions, Allocate, Prepare, Book out, Check in

Workflow Flightcase behaviour
Dispatch Transport dissolve-on-dispatch; kit dispatch ties flightcase to rental; amendment modal for held items under WarnPartial policy
Verify check-in Post-return verification on kit flightcases
Repack split view Shows repack progress with lineage after return

Set flightcase (bulk Functions menu) assigns flightcases to rental lines. Dispatch and return reuse the same flightcase policies as standalone flightcase pages (flightcases.view plus rentals.edit).

Permissions summary

PermissionLabelDescription
flightcases.createCreate FlightcasesCreate flightcases from flightcaseable barcoded items
flightcases.create_temporaryCreate Temporary FlightcasesCreate barcode-only temporary flightcases
flightcases.dissolveDissolve FlightcasesManually dissolve flightcases
flightcases.manage_templatesManage Flightcase TemplatesEdit flightcase templates and catalogue item flightcase settings
flightcases.nestNest FlightcasesPlace flightcases inside other flightcases
flightcases.packPack FlightcasesPack and unpack items in open flightcases
flightcases.pack_overridePack OverridePack items that are checked out on another rental (auto-return)
flightcases.sealSeal FlightcasesSeal and unseal flightcases
flightcases.transferTransfer Between FlightcasesMove items between active flightcases in one step
flightcases.viewView FlightcasesView flightcase listings and contents

Combined gates: dispatch and return need flightcases.view plus rentals.edit; Assets tab mutations and repack need rentals.edit.