Files

gsinghpal 01a46e33e2 fix(process-tree): breadcrumb pile-up + dead "No MO selected" banner

Two issues on the Process Tree client action:

1. Back to Work Order kept growing breadcrumbs (WO -> Tree -> WO ->
   Tree -> ...) because onBack used action.doAction() which PUSHES
   a new act_window onto the stack instead of popping. Fixed by
   trying action.restore() first (pops the Tree off the stack and
   returns to the parent WO/Step controller). Falls through to
   explicit doAction only when there's no parent in the stack
   (direct URL access).

2. The empty-state banner referenced productionId, a dead variable
   from the bridge_mrp era when the tree was tied to mrp.production.
   Since the component now uses jobId (fp.job context key), the
   "No manufacturing order selected" message ALWAYS fired regardless
   of whether a job was loaded. Fixed by using jobId and updating
   the message to "No work order selected".

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-12 09:05:27 -04:00

controllers

feat(jobs): Sub 13 sequential step enforcement + Sub 12e v3 wizard

2026-05-03 21:24:12 -04:00

data

folder rename

2026-04-16 20:53:53 -04:00

models

changes

2026-04-27 00:11:18 -04:00

security

folder rename

2026-04-16 20:53:53 -04:00

static

fix(process-tree): breadcrumb pile-up + dead "No MO selected" banner

2026-05-12 09:05:27 -04:00

views

changes

2026-04-28 19:39:37 -04:00

__init__.py

folder rename

2026-04-16 20:53:53 -04:00

__manifest__.py

fix(process-tree): breadcrumb pile-up + dead "No MO selected" banner

2026-05-12 09:05:27 -04:00

README.md

folder rename

2026-04-16 20:53:53 -04:00

README.md

Fusion Plating — Shop Floor

Tablet / operator ergonomics layer for the fusion_plating core.

What this module adds

Feature	Model
Tablet station registration	`fusion.plating.shopfloor.station`
Bake oven master + chart recorder ref	`fusion.plating.bake.oven`
Hydrogen embrittlement bake-window enforcer	`fusion.plating.bake.window`
First-piece inspection gate	`fusion.plating.first.piece.gate`
Operator next-up queue (transient)	`fusion.plating.operator.queue`

Bake-window enforcer

When a high-strength-steel part exits the plating tank, a clock starts. Customer specification dictates the window (typically 1-4 hours) inside which the relief bake must begin. Missing the window requires scrap or rework — there is no retroactive fix.

The module models this as a first-class entity with:

plate_exit_time — clock start
window_hours — customer spec
bake_required_by — computed deadline
state — awaiting_bake -> bake_in_progress -> baked, with missed_window / scrapped exit paths
A 5-minute cron that flips records past their deadline to missed_window automatically
A kanban board grouped by state with theme-aware status colours

Tablet client

A backend OWL component (Odoo 19 conventions) registered as the fp_shopfloor_tablet client action. It hosts:

QR scan input (wedge scanner or on-screen keyboard friendly)
Live tank / bath / job preview cards
One-tap Start Bake / End Bake buttons
Live operator next-up queue

JSON-RPC endpoints (Odoo 19 type='jsonrpc'):

POST /fp/shopfloor/scan
POST /fp/shopfloor/log_chemistry
POST /fp/shopfloor/start_bake
POST /fp/shopfloor/end_bake
POST /fp/shopfloor/queue

QR code conventions

Prefix	Resolves to
`FP-TANK:<code>`	`fusion.plating.tank`
`FP-BATH:<name>`	`fusion.plating.bath`
`FP-STATION:<code>`	`fusion.plating.shopfloor.station`
`FP-JOB:<name>`	`fusion.plating.bake.window`
`FP-OVEN:<code>`	`fusion.plating.bake.oven`

Security

Reuses the four core Fusion Plating groups (operator, supervisor, manager, admin) defined in fusion_plating. No new groups, no new privilege block. ACLs are graded operator (read/write logs), supervisor (create), manager (full).

Theme

All styling is theme-aware: CSS custom properties + color-mix() against Bootstrap / Odoo tokens. No hex codes, no media queries — works in light and dark mode out of the box.

Install / update

docker exec odoo-dev-app odoo -d fusion-dev -u fusion_plating_shopfloor --stop-after-init