Files

gsinghpal a623c6684d fix(fusion_plating): bug review fixes + progress/net-terms invoicing + formal CoC rebuild

Bug review fixes (found by code review + live QWeb error):
- report_fp_sale.xml: product_uom → product_uom_id (Odoo 19 renamed;
  was raising KeyError during PDF render, blocking all sale-order prints)
- mrp_production.button_mark_done: add idempotency guard on delivery
  auto-create (was duplicating on every re-close)
- fp.certificate._compute_batch_ids: use empty recordset instead of
  False for Many2many computed fields
- fp_notification_template._collect_attachments: collapse attach_quotation
  + attach_sale_order into a single render so email doesn't double-attach
  the same PDF
- fp.operator.certification: SQL unique on computed state was unreliable;
  added explicit `revoked` boolean, made state pure-compute, replaced
  SQL constraint with @api.constrains that checks active-only uniqueness;
  has_active_cert now reads revoked + expires_date directly (no stale
  stored state between nightly recomputes)

Two missing invoice strategies implemented + 1 pre-existing deposit bug fix:
- Progress Billing: new x_fc_progress_initial_percent field on sale.order;
  _create_progress_initial_invoice bills the configured % on SO confirm
  via down-payment wizard, _create_final_balance_invoice bills the
  remainder on delivery
- Net Terms: no invoice on confirm; full invoice auto-created when
  fusion.plating.delivery.action_mark_delivered fires
- Fix for deposit (pre-existing, silent): sale.advance.payment.inv
  reads active_ids at wizard-create time, not on create_invoices();
  context was being set on the wrong call, so every deposit attempt
  raised "Expected singleton" and message-posted to chatter instead
  of actually invoicing
- New fusion_plating_invoicing/models/fp_delivery.py hooks
  action_mark_delivered to dispatch final invoice for progress/net_terms
- fp.direct.order.wizard + SO form surface the progress_initial_percent
  field (conditional on strategy)

Report styling cleanup:
- Hide DISCOUNT column from sale + invoice landscape reports unless at
  least one line has a non-zero discount; colspan auto-adjusts
- Replace hardcoded #0066a1 in all reports with company.primary_color
  driven by doc.company_id → company → user.company_id fallback chain,
  with #1d1f1e as ultimate fallback; new .fp-header-primary class
  exposes the colour for inline section headers (CARGO DESCRIPTION,
  PAYMENT DETAILS, OPERATOR SIGN-OFF, etc.) so they retint with the
  company theme without template edits

Certificate of Conformance — formal ENTECH-style rebuild:
- New res.company fields: x_fc_owner_user_id (default signer, sig from
  hr.employee.signature), x_fc_coc_signature_override (manual upload),
  x_fc_{nadcap,as9100,cgp}_logo + _active toggles for accreditation
  badges
- New res.config.settings section "Fusion Plating" exposing the above
  as configurable blocks; manager-only menu under Configuration →
  Fusion Plating Settings
- New fp.certificate fields: nc_quantity, customer_job_no,
  contact_partner_id (child contact for Name / Email / Phone block)
- New report_coc_en + report_coc_fr templates (primary): custom header
  (company contact | accreditations | company logo), bilingual labels
  per variant, customer info block with customer logo, 3-column cert
  info table, 6-column line-item table (Part # | Process | Customer
  PO | Shipped | NC Qty | Customer Job No.), signature image + bordered
  certification statement, footer "Fusion Plating by Nexa Systems"
- Legacy report_coc + report_coc_portrait kept for existing portal-job
  bindings (no behaviour change)

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

2026-04-17 01:18:22 -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

fix(fusion_plating): bug review fixes + progress/net-terms invoicing + formal CoC rebuild

2026-04-17 01:18:22 -04:00

security

feat(fusion_plating): Tier 2 (quality + audit) and Tier 3 (business) features

2026-04-16 23:55:22 -04:00

static

folder rename

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

views

feat(fusion_plating): Tier 2 (quality + audit) and Tier 3 (business) features

2026-04-16 23:55:22 -04:00

__init__.py

folder rename

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

__manifest__.py

feat(fusion_plating): Tier 2 (quality + audit) and Tier 3 (business) features

2026-04-16 23:55:22 -04:00

README.md

folder rename

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

README.md

Fusion Plating

Core module of the Fusion Plating product family. A configurable, multi-tenant capable ERP for plating and metal-finishing shops, built for Odoo 19 Community and Enterprise.

What this module is

fusion_plating is the process-agnostic foundation that every plating or metal-finishing shop needs, regardless of size, jurisdiction, process mix, or industry. It provides:

Facility — physical sites with their own tanks, operators, capabilities
Process Type — extensible taxonomy (filled in by process packs)
Work Center — lines and stations inside a facility
Tank — physical vessel with QR code, state, bath history
Bath — the chemistry currently in a tank, with its own lifecycle
Bath Parameter — schema for chemistry readings
Bath Log — daily/per-shift chemistry readings with pass/warn/fail rollup
Security — Operator / Supervisor / Manager / Administrator roles
Theme-aware UI — respects Odoo light/dark mode with zero duplication

What this module is not

This core intentionally ships with:

No process chemistry — install fusion_plating_process_en, _chrome, _anodize, _black_oxide etc. to get actual process types and their bath parameter schemas.
No regulatory data — install fusion_plating_compliance_<region> to get jurisdiction-specific limits, forms, and reporting workflows.
No industry specialisations — install fusion_plating_aerospace, _nuclear, _cgp etc. for industry-specific QMS overlays.
No client-specific strings — everything is data-driven.

Product family

Module	Purpose	Status
`fusion_plating`	Core (this module)	MVP
`fusion_plating_quality`	QMS: NCR, CAPA, doc control, calibration, CoC	planned
`fusion_plating_compliance`	Generic compliance framework	planned
`fusion_plating_compliance_on`	Ontario regulatory pack	planned
`fusion_plating_compliance_tor`	Toronto Ch. 681 municipal pack	planned
`fusion_plating_safety`	SDS, WHMIS/TDG, JHSC, exposure	planned
`fusion_plating_shopfloor`	Tablet operator stations, QR scanning, bake-window enforcer	planned
`fusion_plating_portal`	Customer portal	planned
`fusion_plating_process_en`	Electroless nickel — low/mid/high phos	planned
`fusion_plating_process_chrome`	Chrome coating (hex & trivalent)	planned
`fusion_plating_process_anodize`	Aluminum anodizing (Type II, III)	planned
`fusion_plating_process_black_oxide`	Black oxidizing	planned
`fusion_plating_aerospace`	AS9100 + Nadcap AC7108	planned
`fusion_plating_nuclear`	CSA N299, CNSC, NQA-1	planned
`fusion_plating_cgp`	Controlled Goods Program	planned
`fusion_plating_logistics`	Pickup & delivery routing	planned
`fusion_plating_culture`	Values / fundamentals framework	planned
`fusion_plating_bridge_sign`	EE bridge: e-sign CoC acceptance	planned
`fusion_plating_bridge_documents`	EE bridge: Documents workspace	planned
`fusion_plating_bridge_quality`	EE bridge: native `quality` module	planned

Installation

# Development
docker exec odoo-dev-app odoo -d fusion-dev -u fusion_plating --stop-after-init

# Production — after rsync to target server
docker exec <odoo-container> odoo -d <db> -u fusion_plating --stop-after-init

No external Python dependencies. Depends only on standard Odoo 19 Community base modules (base, mail, contacts, product, stock, sale_management, purchase, hr, uom).

Design principles

Works on both Odoo Community and Enterprise. Never depends on quality, documents, sign, studio, or mrp_plm. EE-specific integrations live in separate fusion_plating_bridge_* modules.
No client-specific strings in core. Configuration, not code.
Regions are data, not code. Sewer limits, waste classes, reporting forms come from region packs.
Processes are plug-ins. New process (copper, zinc, tin) = new fusion_plating_process_* module, core untouched.
Dashboards are configured, not coded. Shops pick their own headline KPIs.
Theme-aware. Uses Odoo/Bootstrap CSS variables. One source of truth for colours; Odoo's theme engine decides light vs dark.

Security groups

Group	Intended for
Operator	Shop-floor staff. Reads reference data, writes chemistry logs.
Supervisor	Line supervisors. Manages baths, schedules jobs, reviews logs.
Manager	Quality, EHS, plant manager, engineer. Full CRUD on configuration.
Administrator	Owner, system admin. All manager rights + system settings.

Field naming convention

New models use fusion.plating.* namespace.
Fields on our own models use simple names (no prefix).
Fields added to base Odoo models (res.company, res.partner, product.template, etc.) use the x_fc_ prefix per the repo convention.

Developer notes

All models inheriting from mail.thread use the Odoo 19 chatter pattern.
Security follows the Odoo 19 res.groups.privilege pattern (module category → privilege → groups), not the legacy category_id-on-group pattern.
Sequence numbers use ir.sequence seeded in data/fp_sequence_data.xml.
SCSS uses color-mix() against CSS custom properties — never hardcodes hex values. See static/src/scss/fusion_plating.scss for the theming contract.
No group expand="0" in search views (Odoo 19 incompatibility).
No category_id or users field on res.groups (Odoo 19 incompatibility).