d891002c84
DELETED entirely (model + view + ACL + data file + menu): - fp.coating.config (configurator) - fp.treatment (configurator + seeded data) - fp.coating.thickness (configurator) — replaced by fp.recipe.thickness in Phase A - fp.customer.price.list (configurator) — coating-keyed, no replacement Field deletions: - sale.order.x_fc_coating_config_id - sale.order.line.x_fc_coating_config_id + x_fc_treatment_ids - account.move.line.x_fc_coating_config_id - fp.part.catalog.x_fc_default_coating_config_id + x_fc_default_treatment_ids - fp.job.coating_config_id - fp.pricing.rule.coating_config_id - fp.quality.point.coating_config_ids - fp.direct.order.line.coating_config_id + treatment_ids - fp.sale.description.template.coating_config_id Refactored: - fp.quote.configurator.coating_config_id → recipe_id (now points at fusion.plating.process.node, the actual recipe). All compute, onchange, and matcher logic updated to use recipe directly. Quality inherit extends matcher with spec-tier scoring. - fp.job._fp_create_certificates now reads spec from job.customer_spec_id and formats spec_reference as "code Rev rev". Same for thickness source — bake fields read from recipe_root (Phase A). - fp.job.step.button_finish bake-window auto-spawn reads bake settings from recipe_root instead of coating. - fp.certificate auto-fill spec_min_mils/max_mils from recipe (Phase A thickness fields) instead of coating. - jobs/sale_order.py: job creation reads x_fc_customer_spec_id from line, drops coating refs and the legacy header-coating fallback. - Wizards drop coating + treatment fields and refs. - Configurator views drop x_fc_coating_config_id + x_fc_treatment_ids fields entirely. Quality inherits re-anchor on stable fields (x_fc_part_catalog_id, x_fc_internal_description, default_process_id, process_variant_id, substrate_material) so they keep working. - Reports drop coating fallback elifs; print recipe / spec. - Tablet payload drops coating_config_id from job.read fields. Skipped (deferred to backlog): - fusion_plating_bridge_mrp — module is uninstalled per Sub 11; source files retain coating refs but no runtime impact. - fusion_plating_portal — circular dep (portal → quality → certs → portal). Customer-facing portal coating picker stays for now; promote-spec polish is a separate sub-project. Verification: grep for "coating_config_id|fp.coating.config| fp.treatment|fp.coating.thickness" in live (non-bridge_mrp, non-portal, non-script, non-test) Python/XML/CSV returns 3 hits, all in module / class docstrings explaining Phase E history. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
104 lines
4.9 KiB
Python
104 lines
4.9 KiB
Python
# -*- coding: utf-8 -*-
|
|
# Copyright 2026 Nexa Systems Inc.
|
|
# License OPL-1 (Odoo Proprietary License v1.0)
|
|
{
|
|
'name': 'Fusion Plating — Native Jobs',
|
|
'version': '19.0.10.0.0',
|
|
'category': 'Manufacturing/Plating',
|
|
'summary': 'Native plating job model — replaces mrp.production / mrp.workorder bridge.',
|
|
'author': 'Nexa Systems Inc.',
|
|
'website': 'https://www.nexasystems.ca',
|
|
'maintainer': 'Nexa Systems Inc.',
|
|
'support': 'support@nexasystems.ca',
|
|
'price': 0.00,
|
|
'currency': 'CAD',
|
|
'description': """
|
|
Native Plating Job Bridge
|
|
=========================
|
|
|
|
Bridges fp.job and fp.job.step (defined in fusion_plating core, Phase 1 of
|
|
the migration spec dated 2026-04-25) to the rest of the Fusion Plating
|
|
module family — configurator, portal, logistics, quality, certificates.
|
|
|
|
Coexists with fusion_plating_bridge_mrp during the migration period.
|
|
Activate native jobs via the x_fc_use_native_jobs settings flag (default:
|
|
False). When False, SO confirm continues to create mrp.production records
|
|
through bridge_mrp. When True, SO confirm creates fp.job records here.
|
|
|
|
19.0.4.0.0 (2026-04-24): Operator UI consolidation. The parallel
|
|
OWL/controller stack (job_process_tree, job_plant_overview,
|
|
job_manager_dashboard, job_tablet) was removed. The canonical
|
|
operator-facing UIs now live in fusion_plating_shopfloor and bind
|
|
directly to fp.job / fp.job.step. This module retains lifecycle hooks,
|
|
SO → fp.job creation, reports, and the QR-scan redirect.
|
|
|
|
See docs/superpowers/specs/2026-04-25-fp-native-job-model-design.md for
|
|
full design rationale and §6.2 of the implementation plan for task list.
|
|
""",
|
|
'depends': [
|
|
'fusion_plating', # fp.job, fp.job.step, fp.work.centre
|
|
'fusion_plating_batch', # fusion.plating.batch (Phase 3)
|
|
'fusion_plating_certificates', # fp.certificate, fp.thickness.reading
|
|
'fusion_plating_configurator', # fp.part.catalog
|
|
'fusion_plating_kpi', # fusion.plating.kpi.value (Phase 4)
|
|
'fusion_plating_logistics', # fusion.plating.delivery
|
|
'fusion_plating_notifications', # fp.notification.template (Phase 4)
|
|
'fusion_plating_portal', # fusion.plating.portal.job
|
|
'fusion_plating_quality', # fusion.plating.customer.spec, fusion.plating.quality.hold
|
|
'fusion_plating_receiving', # fp.racking.inspection (Phase 3)
|
|
'fusion_plating_reports', # paperformat helpers, customer_line_header (Phase 5)
|
|
'fusion_plating_shopfloor', # canonical operator UI consoles
|
|
],
|
|
'data': [
|
|
'security/legacy_groups.xml',
|
|
'security/ir.model.access.csv',
|
|
'data/fp_cron_data.xml',
|
|
# Sub 14 — workflow state catalog (must load before fp_job_form_inherit
|
|
# so the statusbar's m2o has its targets available at view-render time).
|
|
'data/fp_workflow_state_data.xml',
|
|
'views/fp_workflow_state_views.xml',
|
|
'views/res_config_settings_views.xml',
|
|
'views/fp_job_step_quick_look_views.xml',
|
|
'views/fp_job_form_inherit.xml',
|
|
'views/fp_job_quality_buttons.xml',
|
|
'views/sale_order_views.xml',
|
|
'views/fp_certificate_views.xml',
|
|
'views/fp_job_consumption_views.xml',
|
|
'views/fp_step_priority_views.xml',
|
|
'views/jobs_in_shopfloor_menu.xml',
|
|
'views/legacy_menu_hide.xml',
|
|
'views/res_users_views.xml',
|
|
'wizards/fp_job_step_move_wizard_views.xml',
|
|
'wizards/fp_job_step_input_wizard_views.xml',
|
|
'report/report_fp_job_sticker.xml',
|
|
'report/report_fp_job_traveller.xml',
|
|
'report/report_fp_job_wo_detail.xml',
|
|
'report/report_fp_job_margin.xml',
|
|
],
|
|
'assets': {
|
|
# Sub 12d — Step Details quick-look modal styles
|
|
# Sub 12e v4 — Record Inputs OWL Dialog (replaces v2/v3)
|
|
# Both registered in both bundles so light + dark mode each
|
|
# compile correctly ($o-webclient-color-scheme branches at
|
|
# compile time per CLAUDE.md note).
|
|
'web.assets_backend': [
|
|
'fusion_plating_jobs/static/src/scss/fp_step_quick_look.scss',
|
|
'fusion_plating_jobs/static/src/scss/fp_record_inputs_dialog.scss',
|
|
'fusion_plating_jobs/static/src/scss/fp_finish_btn.scss',
|
|
'fusion_plating_jobs/static/src/js/fp_record_inputs_dialog.js',
|
|
'fusion_plating_jobs/static/src/xml/fp_record_inputs_dialog.xml',
|
|
],
|
|
'web.assets_web_dark': [
|
|
'fusion_plating_jobs/static/src/scss/fp_step_quick_look.scss',
|
|
'fusion_plating_jobs/static/src/scss/fp_record_inputs_dialog.scss',
|
|
'fusion_plating_jobs/static/src/scss/fp_finish_btn.scss',
|
|
'fusion_plating_jobs/static/src/js/fp_record_inputs_dialog.js',
|
|
'fusion_plating_jobs/static/src/xml/fp_record_inputs_dialog.xml',
|
|
],
|
|
},
|
|
'installable': True,
|
|
'application': False,
|
|
'auto_install': False,
|
|
'license': 'OPL-1',
|
|
}
|