9794a98de9
Two coherent feature drops shipping together because their fp_job_step
edits overlap. Both target operator workflow correctness.
## Sub 13 — Sequential step enforcement (recipe + per-step)
Background:
Investigation on WH/JOB/00339 showed operators starting Incoming
Inspection while Contract Review was still in_progress. Audit:
98.7% of recipe operations system-wide had requires_predecessor_done
= false (the legacy per-step opt-in defaults off, recipe authors
rarely tick the box).
Architecture:
Recipe-level toggle + per-step opt-out (Option A from /investigate).
* fusion.plating.process.node.enforce_sequential — Boolean on the
recipe root. Default True. When True, every operation under this
recipe waits for earlier-sequence steps to finish before it can
start.
* fusion.plating.process.node.parallel_start — Boolean on operation
nodes. When True, this step bypasses the sequential gate (e.g.
paperwork or QA review that runs alongside production).
* Mirrored on fp.step.template (parallel_start) so library steps
carry the flag into snapshots.
* fp.job.enforce_sequential — related from recipe_id. Snapshotted
at job creation so a recipe author flipping the recipe's flag
AFTER job generation does NOT change behaviour mid-run.
* fp.job.step.parallel_start — related from recipe_node_id.
* Decision matrix (encapsulated in
fp.job.step._fp_should_block_predecessors):
recipe.enforce_sequential | step.parallel_start | step.req_pred_done | block?
--------------------------|---------------------|--------------------|------
True | False | any | YES
True | True | any | no
False | any | True | YES
False | any | False | no
* Manager bypass via context fp_skip_predecessor_check=True (existing).
Runtime gates:
* fp.job.step.button_start — calls _fp_should_block_predecessors;
raises UserError naming the blocking earlier step(s).
* fp.job.step.can_start — computed Boolean for view-side disable.
* Move wizard predecessor check
(fusion_plating_shopfloor/controllers/move_controller.py) — uses
the same helper so tablet + backend behave identically.
UI surface:
* Recipe form (fp_process_node_views.xml) — enforce_sequential
toggle on recipe root, parallel_start checkbox on operations.
* Step template form — parallel_start checkbox.
* Simple Recipe Editor (inline library form) — Parallel Start
checkbox + legacy flag demoted with muted styling + supervisor
group gate.
* Recipe Tree Editor (properties panel) — both flags exposed,
only-show on the right node_type.
* Controllers updated to allowlist + payload the new fields.
Migration:
fusion_plating/migrations/19.0.18.12.0/post-migrate.py — sets
enforce_sequential = TRUE on every existing recipe-root node.
Idempotent. User confirmed dev-stage data, so retroactive flip
is safe (no production jobs to disrupt).
Tests:
TestSequentialEnforcement (10 tests) covering:
* sequential mode blocks out-of-order start
* first step always startable
* predecessor finish/skip unlocks next
* parallel_start opts out of gate
* free-flow mode bypasses gate
* legacy requires_predecessor_done still honoured in free-flow
* manager bypass via context
* can_start compute reflects state correctly
* library template parallel_start snapshots into recipe-node
## Sub 12e — Record Inputs Wizard v3 (card layout, dark-mode aware)
Background:
v2 wizard was a 17-column wide editable table. Operators got lost
finding which value column applied to their row's type, horizontal
scroll required on tablets, composite types crammed into one row.
New layout:
* Each measurement renders as a stacked card (CSS Grid + display
transformation on the existing list widget — preserves inline
editing, no JS rewrite).
* Card header: prompt name (large, bold) + type/unit pills.
* Card body: ONLY the value widget for this row's type
(number / boolean / date / text / photo / multi-point / panel).
* Composite types (multi-point thickness 5x reading + avg, bath
panel 4 fields) get inline sub-grid inside the card.
* Empty state ("no measurement prompts") with friendly CTA.
Dark mode:
* SCSS branches at compile time on $o-webclient-color-scheme
(per fusion-plating/CLAUDE.md note).
* Tokens: 7 surface colours + 4 ink levels with light/dark hex
pairs, all behind var(--fp-*) custom properties for per-deploy
override.
* Registered in BOTH web.assets_backend AND web.assets_web_dark
so each bundle compiles its own palette.
Tablet polish:
@media (max-width: 900px) — collapse meta below prompt + bump
numeric input min-height to 56px.
Defensive:
* v2 view kept in the XML file (instant rollback by changing one
view_id ref).
* `:has(.o_invisible_modifier)` rule drops empty cells out of the
grid so Odoo's invisible="..." doesn't punch holes in layout.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
93 lines
4.2 KiB
Python
93 lines
4.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.8.16.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, 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',
|
|
'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',
|
|
'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 — Record
|
|
# Inputs Wizard v3 card layout. 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_job_step_input_wizard_v3.scss',
|
|
],
|
|
'web.assets_web_dark': [
|
|
'fusion_plating_jobs/static/src/scss/fp_step_quick_look.scss',
|
|
'fusion_plating_jobs/static/src/scss/fp_job_step_input_wizard_v3.scss',
|
|
],
|
|
},
|
|
'installable': True,
|
|
'application': False,
|
|
'auto_install': False,
|
|
'license': 'OPL-1',
|
|
}
|