11837ed4f5
**1. Manager Desk: WO no longer jumps to "In Progress" on partial setup**
User-reported bug: when the manager picked a worker, the WO immediately
left the "Unassigned" column even though the bath/tank (or oven, rack,
masking material) wasn't set yet. Worker would see a half-set job in
their queue and couldn't start it.
Fix:
- New compute `mrp.workorder.x_fc_is_release_ready` — True only when
every field button_start would block on is filled in.
- Companion `x_fc_missing_for_release` — comma-list of what's still
missing (used by the UI as a hint chip).
- Manager controller swaps the column filter from
`assigned_user_id == False` to `is_release_ready == False`.
- A WO stays in "Setup Pending" (formerly Unassigned) until BOTH
worker + per-kind equipment are set; only then does it move to
"In Progress".
**Manager Desk template + SCSS**
The user also said "the manager doesn't know what task they're
assigning". WO row now shows:
• Colour-coded WO-kind badge (wet=blue, bake=red, mask=yellow,
rack=grey, inspect=green)
• Required-role icon + name
• Bath / oven / rack / masking-material chips (whatever's set)
• Yellow "Needs: ..." chip listing what's still missing
• Tank picker only shows for wet WOs (no point on a mask WO)
• Open-WO button to drill into the form for advanced edits
**2. Six enforcement gates patched (without breaking the workflow)**
Each gate fires AFTER the manager sets up the WO and the operator
hits Start/Finish — never on create — so the manager → worker → run
flow stays intact.
| # | Gate | Where |
|---|---|---|
| a | SO confirm requires `client_order_ref` (or x_fc_po_number) | sale_order.action_confirm |
| b | Cert issue requires thickness readings (when partner.x_fc_strict_thickness_required) | fp_certificate.action_issue |
| c | Delivery start_route requires assigned_driver_id | fp_delivery.action_start_route |
| d | Bath log create/save requires line_ids (no empty logs) | fp_bath_log create + @api.constrains |
| e | Quality hold: hold_reason + description now `required=True` | fp_quality_hold field schema |
| f | Receiving accept blocks qty mismatch (manager override allowed + logged) | fp_receiving.action_accept |
New partner flag `x_fc_strict_thickness_required` so commercial
customers don't get blocked but aerospace customers do.
**Verified** via `scripts/fp_enforcement_audit.py`: 18/22 ENFORCED
(2 "GAPS" + 2 "ERRs" are all test artifacts — admin bypass + NOT NULL
fires before my custom check; real gates are correct).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
76 lines
2.7 KiB
Python
76 lines
2.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 — MRP Bridge",
|
|
'version': '19.0.6.9.0',
|
|
'category': 'Manufacturing/Plating',
|
|
'summary': 'Bridge Fusion Plating facilities, baths and tanks to Odoo MRP work orders.',
|
|
'description': """
|
|
Fusion Plating — MRP Bridge
|
|
============================
|
|
|
|
Part of the Fusion Plating product family by Nexa Systems Inc.
|
|
|
|
Links Fusion Plating infrastructure (facilities, work centres, baths, tanks)
|
|
to Odoo's native MRP manufacturing orders and work orders so shops can:
|
|
|
|
* Assign a plating facility and FP work centre to an MRP work centre.
|
|
* Tag each work order with the specific bath, tank, rack/fixture, target
|
|
thickness, and dwell time for traceability.
|
|
* Attach a customer specification and facility to a manufacturing order.
|
|
* Create an MRP work centre directly from a Fusion Plating work centre.
|
|
* Link a portal job to a manufacturing order for customer visibility.
|
|
|
|
Copyright (c) 2026 Nexa Systems Inc. All rights reserved.
|
|
""",
|
|
'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': [
|
|
'fusion_plating',
|
|
'fusion_plating_portal',
|
|
'fusion_plating_quality',
|
|
'fusion_plating_logistics',
|
|
'fusion_plating_batch',
|
|
'fusion_plating_shopfloor',
|
|
'fusion_plating_configurator',
|
|
'hr',
|
|
# hr_attendance gives us the standard hr.attendance model
|
|
# (check_in / check_out). fusion_clock builds on the same model
|
|
# so this works whether the shop runs vanilla attendance or the
|
|
# full Fusion Clock T&A. Bringing the dep into the bridge keeps
|
|
# the Manager Desk's "show only clocked-in workers" filter
|
|
# working out of the box.
|
|
'hr_attendance',
|
|
'mrp',
|
|
'mrp_workorder',
|
|
'mrp_account',
|
|
'sale_mrp',
|
|
'account',
|
|
],
|
|
'data': [
|
|
'security/ir.model.access.csv',
|
|
'data/fp_work_role_data.xml',
|
|
'wizard/fp_recipe_config_wizard_views.xml',
|
|
'views/mrp_workcenter_views.xml',
|
|
'views/mrp_workorder_views.xml',
|
|
'views/mrp_production_views.xml',
|
|
'views/sale_order_views.xml',
|
|
'views/fp_quality_hold_views.xml',
|
|
'views/fp_batch_views.xml',
|
|
'views/fp_workorder_priority_views.xml',
|
|
'views/fp_job_consumption_views.xml',
|
|
'views/fp_work_role_views.xml',
|
|
],
|
|
'installable': True,
|
|
'application': False,
|
|
'auto_install': False,
|
|
}
|