Files

gsinghpal f8fc6be370 feat(portal): inject filter+search strip into Odoo /my/orders + docs

- views/fp_sale_order_portal.xml: new template inherit
  portal_my_orders_fp_search on sale.portal_my_orders. Injects the
  fp_portal_list_controls strip before the "no orders" alert. Filter
  pills + sort dropdown are disabled here (we don't own the route,
  Odoo's sortby is preserved separately). The search input is wired
  to .o_portal_my_doc_table tbody (the table class Odoo's
  portal.portal_table emits) so real-time keyword filtering works
  without needing to monkey-patch the stock route or template.

- CLAUDE.md: documents two conventions surfaced by the recent portal
  work:
    Rule 17 — test scaffolding for account.move creation must use
      with_context(fp_from_so_invoice=True) and pass
      invoice_payment_term_id, to satisfy custom gates in
      fusion_plating_jobs and fusion_plating_invoicing.
    Rule 18 — FP portal list pages don't paginate. They load up to
      500 records and rely on fp_portal_list_search.js to filter
      client-side. Hidden <td class="d-none"> cells per row carry
      extra searchable text.

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

2026-05-18 00:06:26 -04:00

controllers

feat(portal): real-time search + filter pills on 4 FP list pages

2026-05-18 00:06:18 -04:00

data

folder rename

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

models

feat(portal): per-stage timestamps on fp.portal.job

2026-05-17 02:47:08 -04:00

security

folder rename

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

static/src

feat(portal): reusable list-search JS + fp_portal_list_controls macro

2026-05-18 00:06:02 -04:00

tests

feat(portal): account_summary controller + 3 unit tests

2026-05-17 14:13:48 -04:00

views

feat(portal): inject filter+search strip into Odoo /my/orders + docs

2026-05-18 00:06:26 -04:00

__init__.py

folder rename

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

__manifest__.py

feat(portal): reusable list-search JS + fp_portal_list_controls macro

2026-05-18 00:06:02 -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