Files

gsinghpal b93633d728 fix(shopfloor,reports): make QR scan actually navigate after decode

Two bugs were colluding to make iPhone scans look like "nothing
happens":

1. The in-app scanner was calling action.doAction({res_model: 'fp.job',
   res_id: <decoded-id>}). Old physical stickers (still on every box)
   encode /fp/wo/<mrp.production.id> — that id space doesn't match
   fp.job, so the form opened on a non-existent record and silently
   showed nothing. New /fp/job/<id> stickers happened to work because
   the IDs lined up by coincidence.

2. The /fp/wo/<id> controller redirected to mrp.production / mrp.workorder
   forms, both of which still exist as legacy records but aren't the
   canonical source of truth post-migration.

Fix:
- qr_scanner._handleCode now navigates via window.location.href instead
  of action.doAction. It hands /fp/job/<n> and /fp/wo/<n> URLs straight
  to the existing server-side controllers, which know how to resolve
  the right record. Bare numeric ids pasted manually -> /fp/job/<n>.
  Anything else surfaces the decoded text as an error so the operator
  can see decode worked but the value isn't a sticker.

- Modal now shows "Detected: <value>" the moment a code is decoded
  (before navigation), so even on slow phones the operator sees
  immediate feedback that the camera read the QR.

- wo_scan.py now resolves in this order:
    1. fp.job by legacy_mrp_production_id (migration-aware — old
       stickers route to the new model)
    2. mrp.production direct browse
    3. mrp.workorder direct browse
    4. fall back to /odoo/plating-jobs (or work-orders list)

Versions: shopfloor 19.0.17.0.0 -> 19.0.18.0.0,
          reports   19.0.7.15.0 -> 19.0.7.16.0.

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

2026-04-25 13:14:06 -04:00

controllers

feat(jobs,shopfloor): smart buttons + QR scanner + NFC tank pages

2026-04-25 12:39:37 -04:00

data

folder rename

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

models

feat(plating): wire deferred UoM defaults — bake oven, bake window, coating, tank

2026-04-19 12:11:37 -04:00

security

folder rename

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

static

fix(shopfloor,reports): make QR scan actually navigate after decode

2026-04-25 13:14:06 -04:00

views

feat(jobs,shopfloor): smart buttons + QR scanner + NFC tank pages

2026-04-25 12:39:37 -04:00

__init__.py

folder rename

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

__manifest__.py

fix(shopfloor,reports): make QR scan actually navigate after decode

2026-04-25 13:14:06 -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