Phase 6 originally scoped the full operator UI rewrite (Plant Overview, Tablet, Manager Dashboard, Process Tree). Tailscale SSH to entech is currently unavailable, so live in-browser verification of OWL/JS components isn't possible. Shipping a lean Phase 6 with the data-layer pieces: 1. /fp/job/<id> scan controller — when a user scans a fp.job sticker, lands them on the fp.job form (or the process tree action once that's wired). Mirrors fusion_plating_reports' /fp/wo/ pattern. 2. /fp/jobs/process_tree JSON endpoint — returns the recipe tree serialized with each node tagged by its fp.job.step state, ready for an OWL component to render. The component itself is deferred (see README.md). The bigger UI deferrals (kanban, tablet, manager dashboard) are documented in README.md. They get their own focused project after cutover — the data layer is complete, so they can land incrementally without touching fp.job/fp.job.step. Tests verify controller imports + serialization shape (no HTTP because TransactionCase doesn't easily simulate request context). Manifest 19.0.1.8.0 → 19.0.1.9.0. Part of: native job model migration (spec 2026-04-25) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
49 lines
2.2 KiB
Python
49 lines
2.2 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.1.9.0',
|
|
'category': 'Manufacturing/Plating',
|
|
'summary': 'Native plating job model — replaces mrp.production / mrp.workorder bridge.',
|
|
'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.
|
|
|
|
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)
|
|
],
|
|
'data': [
|
|
'security/ir.model.access.csv',
|
|
'views/res_config_settings_views.xml',
|
|
'report/report_fp_job_sticker.xml',
|
|
'report/report_fp_job_traveller.xml',
|
|
],
|
|
'installable': True,
|
|
'application': False,
|
|
'auto_install': False,
|
|
'license': 'OPL-1',
|
|
}
|