d6bd43b76e
Three issues from user testing on entech: 1. RPC error: column fp_step_template.triggers_workflow_state_id does not exist Root cause: the field was declared in fusion_plating CORE, but its target model fp.job.workflow.state lives in fusion_plating_jobs. Odoo loads core BEFORE jobs (jobs depends on core), so when core's field declaration runs, the comodel doesn't exist yet — and Odoo silently skips creating the column. Fix: moved the field to fusion_plating_jobs/models/fp_job.py via _inherit. Now the column is added when jobs loads (after core), and the FK target is resolvable. 2. No chatter on the Workflow State form Added _inherit = ['mail.thread', 'mail.activity.mixin'] to fp.job.workflow.state. Tracking enabled on name/code/sequence so admins see who changed the milestone vocabulary. <chatter/> widget added to the form view. 3. Form layout still showed cramped 2-col help text The XML file on disk had my new alert-info card, but Odoo's DB ir_ui_view still held the old arch. The -u didn't refresh it (likely because the file's mtime didn't change between deploys). Fix: bump version + the next deploy will run a SQL DELETE on the ir_ui_view record so Odoo recreates it from XML on -u. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
fusion_plating_jobs
Native plating job bridge — wires fp.job and fp.job.step (defined in
fusion_plating core, Phase 1 of the migration spec dated 2026-04-25)
into the rest of the Fusion Plating module family: configurator, portal,
logistics, quality, certificates, batches, KPI, notifications, reports.
Coexists with fusion_plating_bridge_mrp during the migration period.
The x_fc_use_native_jobs settings flag (default: False) toggles the
behaviour. 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 of the implementation plan for phase
breakdown.
Phase 6 — deferred items
Phase 6 originally scoped the full operator UI rewrite. With Tailscale SSH to entech currently unavailable we cannot live-test OWL/JS in the browser, so Phase 6 ships a lean version: the data-layer endpoints land now, the rendering UI lands later.
Deferred to post-cutover hardening:
- Plant Overview kanban over
fp.job.step— replacesfusion_plating_shopfloor'smrp.workorderkanban. - Tablet Station UI rewrite over
fp.job/fp.job.step. - Manager Dashboard rewrite.
- Process Tree OWL component — currently a stub:
/fp/jobs/process_treereturns the serialized recipe tree as JSON, but the OWL component to render it is not built.
Rationale: these are large OWL/JS components that need live in-browser
verification on entech. Under the migration's parallel-coexistence
strategy, operators continue using the existing shopfloor UI (bound to
mrp.workorder) until cutover. After cutover, the operator UI rewrite
becomes its own focused project — the data layer (fp.job,
fp.job.step, time logs, timestamps) is fully in place from
Phase 1–5.
Phase 6 — what shipped
/fp/job/<id>— scan-redirect controller. The fp.job sticker QR encodes this URL. Routes managers to thefp.jobform; routes operators to the same form for now (will swap to the process tree client action once the OWL component lands)./fp/jobs/process_tree— JSON-RPC endpoint that returns the recipe tree for a job, with each node tagged by its matchingfp.job.stepstate, ready for an OWL component to consume.