Skip to content

Release v4.46.0

Choose a tag to compare

@github-actions github-actions released this 16 Oct 05:13
7172b2d

The Inventory and Assets domain blueprint of Part B 3.4 of the screen blueprints specification: a ready-to-use warehouse application on top of the foundation set, with its navigation and a sample-data pack.

Added

  • @cratis/scene.blueprint.inventory, a blueprint package (domain inventory, category Business / Inventory) that depends on the foundation set only through its public templates and components: eight screen templates, three quick-create dialogs and eight ready-to-use screens.
    • InventoryDashboard: low stock count, stock value and movements this week; top movers; recent movements; items to reorder.
    • InventoryItemList (sku, name, category, location, quantity, status; low stock tinted and marked in words; filters; choosing a row opens the item) and InventoryItemGallery (the same items as cards with their picture).
    • InventoryItemPage: key facts, the item's fields and supplier, stock by location and movement history as related lists, cycle counts; Adjust stock and Check out.
    • InventoryLocations: the location tree beside what is stored in the chosen location and beneath it; the choice lives in the address.
    • InventoryMovementList (read only), InventorySupplierList and InventoryCheckInOut, a mobile-first single-column form to scan or search an item and check it in or out.
    • Dialogs InventoryAdjustStock (item, quantity change, reason), InventoryQuickCreateItem and InventoryQuickCreateSupplier.
    • Each template carries its scopes, so a template picker offers it only where it fits and hides the blueprint where nothing applies.
  • Navigation: a topbar naming the inventory module and the module's sidebar (Dashboard, Items with Table and Gallery, Locations, Movements, Suppliers), the application structure and inventoryApplication().
  • Sample-data pack inventory-warehouse (en-GB, GBP): sixteen items, fourteen movements, five suppliers and a three-level tree of locations.
  • Specifications for the definition of done per template and package, the screen set agreeing with the manifest, structure and navigation, applicability by level, every screen previewed with no accessibility violation, every standard state forced, the behaviors of the application, and a Chromium audit of every screen and dialog at desktop, tablet and phone widths in the light and dark themes.
  • Docs: blueprints/inventory-blueprint.md.

Part of #113