Files

gsinghpal cd2584d6ee ui(rename): "Plating Job" -> "Work Order" / display "WO # 01368"

Standardise user-facing terminology across 5 modules (27 files):
  - display_name compute: 'Work Order # 01368' -> 'WO # 01368'
  - _description on 5 models: Plating Job{," Step"," Step Time Log"," Margin Report"," Recipe Node Override"} -> Work Order equivalents
  - field labels (string=...) on 13 Many2one / One2many fields
    across fp.batch, fp.thickness_reading, fp.quality.hold,
    fp.job_consumption, fp.portal.job, fp.certificate, fp.delivery,
    fp.quality.check, fp.racking.inspection, res.partner, sale.order
  - XML view labels: action names, list/form/search strings,
    portal template names, dashboard tile titles

What's deliberately preserved:
  - DB model name 'fp.job' (technical identifier — used by
    sale_order.x_fc_plating_job_ids and all comodel refs)
  - Module name 'fusion_plating_jobs' (directory / import path)
  - Settings -> Apps display label 'Fusion Plating Jobs' (module
    identity for Odoo's app picker)
  - 'Use Native Plating Jobs' migration toggle (internal mechanism
    flag, not user-facing terminology)

Verified on entech: WH/JOB/01368 now displays as 'WO # 01368'
everywhere humans look (form header, breadcrumbs, M2O dropdowns,
error messages, smart-button titles).

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

2026-05-12 08:22:09 -04:00

controllers

folder rename

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

data

folder rename

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

models

ui(rename): "Plating Job" -> "Work Order" / display "WO # 01368"

2026-05-12 08:22:09 -04:00

security

folder rename

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

static/src

folder rename

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

views

ui(rename): "Plating Job" -> "Work Order" / display "WO # 01368"

2026-05-12 08:22:09 -04:00

__init__.py

folder rename

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

__manifest__.py

ui(rename): "Plating Job" -> "Work Order" / display "WO # 01368"

2026-05-12 08:22:09 -04:00

README.md

folder rename

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

README.md

Fusion Plating — Customer Portal

Part of the Fusion Plating product family by Nexa Systems Inc.

Customer-facing portal that extends fusion_plating with a self-service area inside Odoo's standard portal layout. Customers can:

Submit Requests for Quote (RFQ) with drawings, target dates, and notes
Track production jobs through Received → In Progress → QC → Ready → Shipped → Complete
Download Certificates of Conformance (CoC) and packing lists
Reference shipment tracking numbers and invoice references

Models

Model	Purpose
`fusion.plating.quote.request`	Customer-submitted RFQ
`fusion.plating.portal.job`	Lightweight portal-facing job summary
`res.partner` (extended)	Adds portal-enabled flag and counts

Routes

Route	Purpose
`/my/quote_requests`	List quote requests
`/my/quote_requests/<id>`	RFQ detail
`/my/quote_requests/new`	New RFQ form
`/my/quote_requests/submit`	RFQ form submission
`/my/jobs`	List jobs
`/my/jobs/<id>`	Job detail
`/my/jobs/<id>/coc`	Download CoC PDF

Conventions

New res.partner fields prefixed x_fc_*.
All portal pages extend portal.portal_layout.
SCSS theme-aware: uses Bootstrap CSS variables only, no hex values.
Routes are type='http' (not the deprecated type='json').

README.md

Fusion Plating — Customer Portal

Models

Routes

Conventions

License