152ed86c3a
Per client direction: every order is a thickness RANGE (e.g. "0.0005-0.0008 mils" or "5-10 mils"), never a single value. The old picker model (fp.recipe.thickness with a single 'value' Float) was modelling the wrong concept and overcrowding the order entry UI. Replaced with one free-text Char field that auto-fills from last-used or part default. DELETED entirely: - fp.recipe.thickness model (file + view + ACL + manifest entry) - recipe.thickness_option_ids One2many (the picker source) - "Thickness Options" inline list on the recipe form - sale.order.line.x_fc_thickness_id (M2O picker) - account.move.line.x_fc_thickness_id - fp.delivery.x_fc_thickness_id - fp.direct.order.line.thickness_id ADDED: - sale.order.line.x_fc_thickness_range (Char) — operator types range - account.move.line.x_fc_thickness_range — for invoice rendering - fp.delivery.x_fc_thickness_range — for packing slip - fp.direct.order.line.thickness_range — for the wizard - fp.part.catalog.x_fc_default_thickness_range — part default AUTO-FILL CHAIN (sale.order.line + wizard line): 1. Operator already typed → keep 2. Most recent SO line for (this part, this customer) with a non-empty thickness_range → copy that 3. part.x_fc_default_thickness_range → copy 4. Blank — operator types Implemented as both an @api.onchange (interactive) AND a create() override (programmatic — wizard, sale_mrp bridge, imports). Same logic in both paths. WIZARD push-to-defaults: when "Save as Default" toggle is ticked on a wizard line, persist the line's thickness_range to part.x_fc_default_thickness_range so future first-customer orders get a sensible starting point. REPORTS: customer_line_header.xml + report_fp_wo_sticker.xml now print the Char range as-typed (no display_name lookup needed). KEPT (admin documentation only — doesn't affect order entry): - recipe.thickness_min, thickness_max, thickness_uom on the recipe root: documents the recipe's CAPABILITY range. No UI gate; just for spec authors to record what the chemistry can produce. JOB GROUPING: fp.job auto-create groups SO lines by (recipe, part, spec, thickness, serial). Updated to key on the thickness_range Char (stripped) instead of the deleted thickness_id integer. DB cleanup: --update=base ran on the upgrade, dropping the fp_recipe_thickness table + the four x_fc_thickness_id columns. Existing data was already nulled in earlier dev work. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
74 lines
2.4 KiB
Python
74 lines
2.4 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 — Logistics',
|
|
'version': '19.0.3.8.0',
|
|
'category': 'Manufacturing/Plating',
|
|
'summary': (
|
|
'Pickup & delivery for plating shops: vehicle master, driver '
|
|
'tracking, route planning, chain of custody, proof of delivery.'
|
|
),
|
|
'description': """
|
|
Fusion Plating — Logistics
|
|
==========================
|
|
|
|
Part of the Fusion Plating product family by Nexa Systems Inc.
|
|
|
|
Adds pickup & delivery management to the Fusion Plating core:
|
|
|
|
* Vehicle master (with insurance, registration, service, TDG status)
|
|
* Driver tracking (extends hr.employee with licence + TDG fields)
|
|
* Pickup requests — customer-initiated pickup of parts to be processed
|
|
* Deliveries — scheduled delivery of finished parts back to customer
|
|
* Routes — combine multiple pickups + deliveries into a single run
|
|
* Chain of custody — every custody event logged for audit trail
|
|
* Proof of delivery — signature, photos, GPS
|
|
|
|
Depends on the core fusion_plating module. Works on both Odoo Community
|
|
and Enterprise editions.
|
|
|
|
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_configurator',
|
|
'fusion_plating_receiving', # Shared "Shipping & Receiving" menu root
|
|
'hr',
|
|
'mail',
|
|
],
|
|
'data': [
|
|
'security/fp_logistics_security.xml',
|
|
'security/ir.model.access.csv',
|
|
'data/fp_sequence_data.xml',
|
|
'views/fp_vehicle_views.xml',
|
|
'views/fp_pickup_request_views.xml',
|
|
'views/fp_delivery_views.xml',
|
|
'views/fp_route_views.xml',
|
|
'views/fp_chain_of_custody_views.xml',
|
|
'views/fp_proof_of_delivery_views.xml',
|
|
'views/hr_employee_views.xml',
|
|
'views/fp_menu.xml',
|
|
],
|
|
'demo': [
|
|
'data/fp_demo_logistics_data.xml',
|
|
],
|
|
'assets': {
|
|
'web.assets_backend': [
|
|
'fusion_plating_logistics/static/src/scss/fusion_plating_logistics.scss',
|
|
],
|
|
},
|
|
'installable': True,
|
|
'auto_install': False,
|
|
'application': False,
|
|
}
|