cd2584d6ee
Standardise user-facing terminology across 5 modules (27 files):
- display_name compute: 'Work Order # 01368' -> 'WO # 01368'
- _description on 5 models: Plating Job{," Step"," Step Time Log"," Margin Report"," Recipe Node Override"} -> Work Order equivalents
- field labels (string=...) on 13 Many2one / One2many fields
across fp.batch, fp.thickness_reading, fp.quality.hold,
fp.job_consumption, fp.portal.job, fp.certificate, fp.delivery,
fp.quality.check, fp.racking.inspection, res.partner, sale.order
- XML view labels: action names, list/form/search strings,
portal template names, dashboard tile titles
What's deliberately preserved:
- DB model name 'fp.job' (technical identifier — used by
sale_order.x_fc_plating_job_ids and all comodel refs)
- Module name 'fusion_plating_jobs' (directory / import path)
- Settings -> Apps display label 'Fusion Plating Jobs' (module
identity for Odoo's app picker)
- 'Use Native Plating Jobs' migration toggle (internal mechanism
flag, not user-facing terminology)
Verified on entech: WH/JOB/01368 now displays as 'WO # 01368'
everywhere humans look (form header, breadcrumbs, M2O dropdowns,
error messages, smart-button titles).
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.8.21.1',
|
|
'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, fp.coating.config
|
|
'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',
|
|
}
|