3d1b6e7ec5
Reported 2026-05-20: the receiving state machine had four states (draft → counted → staged → closed) where the middle pair was pure ceremony. Real-usage data on entech: state distribution: 14 draft, 4 closed (zero `staged` records) median dwell counted → staged: 11 seconds median dwell staged → closed: 4 minutes `staged` captured no fields, fired no gates, mapped to the same SO `x_fc_receiving_status='partial'` as `counted`. Pure click-through. Cleanup: - State Selection retains `staged` as `Staged (legacy)` so historical records remain readable; new transitions never write it. - statusbar_visible drops it from the chevron header. - action_mark_staged becomes a thin shim that advances counted → closed directly (any old button binding still works). - action_close now accepts `counted` as a valid source state (was previously only `staged` / legacy `accepted` / `resolved`). - View: "Stage for Racking" button removed. "Close" button renamed to "Close — Racking Confirmed" so the racking-crew confirmation meaning stays obvious. - _update_so_receiving_status mapping unchanged for legacy `staged` (still maps to partial) — only the comment block updated to describe the new canonical flow. Migration 19.0.3.20.0 advances any `staged` records to `closed` and syncs the linked SO's x_fc_receiving_status to `received` so downstream gates (job step start, mark_done qty check, cert creation) don't see a stale "partial" status. Module: fusion_plating_receiving 19.0.3.19.0 → 19.0.3.20.0. Tests: TestQtyReceivedPropagation updated — 5 tests dropped the action_mark_staged() call, walk draft → counted → closed directly. All 11 tests green (carrier 6 + propagation 5). Verified on entech: existing 14 draft + 4 closed records untouched. Direct draft → counted → closed transition works end-to-end on RCV-30041 (was the test target). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
54 lines
1.7 KiB
Python
54 lines
1.7 KiB
Python
# -*- coding: utf-8 -*-
|
|
# Copyright 2026 Nexa Systems Inc.
|
|
# License OPL-1 (Odoo Proprietary License v1.0)
|
|
# Part of the Fusion Plating product family.
|
|
|
|
{
|
|
'name': 'Fusion Plating — Receiving & Inspection',
|
|
'version': '19.0.3.20.0',
|
|
'category': 'Manufacturing/Plating',
|
|
'summary': 'Parts receiving, inspection, damage logging, and manufacturing gate.',
|
|
'description': """
|
|
Fusion Plating — Receiving & Inspection
|
|
=========================================
|
|
|
|
Part of the Fusion Plating product family by Nexa Systems Inc.
|
|
|
|
Provides:
|
|
- Parts receiving records linked to sale orders
|
|
- Quantity verification and condition inspection
|
|
- Damage logging with photos and severity tracking
|
|
- Auto-creation of receiving records on SO confirmation
|
|
- Soft manufacturing gate (warns if parts not received)
|
|
""",
|
|
'author': 'Nexa Systems Inc.',
|
|
'website': 'https://www.nexasystems.ca',
|
|
'maintainer': 'Nexa Systems Inc.',
|
|
'support': 'support@nexasystems.ca',
|
|
'license': 'OPL-1',
|
|
'price': 0.00,
|
|
'currency': 'CAD',
|
|
'depends': [
|
|
'delivery',
|
|
'fusion_plating_configurator',
|
|
'fusion_shipping',
|
|
'sale_management',
|
|
'stock',
|
|
],
|
|
'data': [
|
|
'security/fp_receiving_security.xml',
|
|
'security/ir.model.access.csv',
|
|
'data/fp_receiving_sequence_data.xml',
|
|
'data/delivery_carrier_seed_data.xml',
|
|
'views/fp_receiving_views.xml',
|
|
'views/fp_racking_inspection_views.xml',
|
|
'views/sale_order_views.xml',
|
|
'views/fp_receiving_menu.xml',
|
|
'views/fusion_shipment_inherit_views.xml',
|
|
'wizards/fp_label_manual_wizard_views.xml',
|
|
],
|
|
'installable': True,
|
|
'application': False,
|
|
'auto_install': False,
|
|
}
|