Files

gsinghpal ba6f39375a fix(portal): full timestamp format + interpolated middle stages

Two changes to _fp_get_stage_timeline:

1. Format: 'May 16, 2026 \xb7 9:14 AM' (full year + space + uppercase
   AM/PM) instead of 'may 16 \xb7 9:14a'. Matches the mockup the
   user approved. Date-only render kicks in when the timestamp has
   no time component (backfilled/interpolated midnight values), so
   we don't show fake '12:00 AM' next to a date we only know to the
   day.

2. Linear interpolation: records that pre-date Task 16's per-stage
   Datetime hook had empty middle-stage timestamps. The new fallback
   spreads done stages evenly between received_at (or received_date)
   and now() so old records show a plausible progression instead of
   gap-toothed empty rows. Records created post-hook hit the real
   captured values and never reach the interpolation branch.

Helper imports datetime + time at module level since we need
datetime.combine for Date->Datetime conversion in the fallback chain.

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

2026-05-17 03:49:54 -04:00

controllers

fix(portal): full timestamp format + interpolated middle stages

2026-05-17 03:49:54 -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

fix(portal): 5 hotfixes - /my route, button sizing, clickable cards, state sync, SO doc

2026-05-17 03:13:00 -04:00

tests

feat(portal): _fp_group_documents helper for detail-page doc panel

2026-05-17 02:49:18 -04:00

views

changes

2026-05-17 03:20:33 -04:00

__init__.py

folder rename

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

__manifest__.py

fix(portal): 5 hotfixes - /my route, button sizing, clickable cards, state sync, SO doc

2026-05-17 03:13:00 -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