5df7d5e6cf
Removes the parallel OWL/controller stack I built in fusion_plating_jobs (job_process_tree, job_plant_overview, job_manager_dashboard, job_tablet, job_*.scss, plus parallel controllers and action XML files). Refactors the existing fusion_plating_shopfloor components in place to bind to fp.job / fp.job.step instead of mrp.production / mrp.workorder. End state: - ONE operator UI module (shopfloor) instead of two parallel ones - Existing token system (_fp_shopfloor_tokens.scss) reused as designed - no duplicate jobs tokens - Existing /fp/shopfloor/* RPC URLs preserved (no integration breakage); workorder_id kwargs accepted as legacy aliases for step_id / job_id so older tablet clients keep working - Existing visual designs preserved - only the data layer underneath changed - Process Tree button on fp.job form now points at fusion_plating_shopfloor's fp_process_tree client action - Bake Windows / First-Piece Gates / Bake Oven / Operator Queue models stay where they were - legacy_menu_hide.xml trimmed: only the bridge_mrp Production Priorities entry remains; the 3 shopfloor menus (Manager Desk, Plant Overview, Tablet Station) are now visible (the canonical native consoles) Manifests: - fusion_plating_jobs 19.0.3.1.0 -> 19.0.4.0.0 (consolidation bump, no more bundled JS/SCSS, only job_scan controller retained) - fusion_plating_shopfloor 19.0.14.4.0 -> 19.0.15.0.0 (asset bundle cache-bust + significant controller refactor) Tests pass on entech: 0 failed, 0 errors of 41 tests. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
33 lines
1.7 KiB
XML
33 lines
1.7 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<odoo noupdate="0">
|
|
<!-- After the shopfloor consolidation (2026-04-24) the shopfloor
|
|
operator UIs are the canonical native fp.job / fp.job.step
|
|
consoles. Only bridge_mrp's Production Priorities menu (still
|
|
bound to mrp.workorder) remains legacy.
|
|
|
|
The group_fusion_plating_legacy_menus group is preserved so a
|
|
site that needs to bring legacy menus back can simply add a
|
|
user to the group. -->
|
|
|
|
<!-- Reset group_ids on the 3 shopfloor menus that used to be
|
|
hidden — they are now the canonical UIs and should be visible
|
|
to all users (subject to the original groups= attribute on
|
|
each menuitem in fusion_plating_shopfloor/views/fp_menu.xml). -->
|
|
<record id="fusion_plating_shopfloor.menu_fp_shopfloor_manager" model="ir.ui.menu">
|
|
<field name="group_ids" eval="[(6, 0, [ref('fusion_plating.group_fusion_plating_manager')])]"/>
|
|
</record>
|
|
<record id="fusion_plating_shopfloor.menu_fp_shopfloor_plant_overview" model="ir.ui.menu">
|
|
<field name="group_ids" eval="[(6, 0, [])]"/>
|
|
</record>
|
|
<record id="fusion_plating_shopfloor.menu_fp_shopfloor_tablet" model="ir.ui.menu">
|
|
<field name="group_ids" eval="[(6, 0, [])]"/>
|
|
</record>
|
|
|
|
<!-- bridge_mrp: Production Priorities is mrp.workorder ordering UI;
|
|
fp.job has its own priority field on the header. Hidden from
|
|
operators / supervisors / managers; only the legacy group sees it. -->
|
|
<record id="fusion_plating_bridge_mrp.menu_fp_workorder_priority" model="ir.ui.menu">
|
|
<field name="group_ids" eval="[(6, 0, [ref('fusion_plating_jobs.group_fusion_plating_legacy_menus')])]"/>
|
|
</record>
|
|
</odoo>
|