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>
78 lines
2.5 KiB
Python
78 lines
2.5 KiB
Python
# -*- coding: utf-8 -*-
|
|
# Copyright 2026 Nexa Systems Inc.
|
|
# License OPL-1 (Odoo Proprietary License v1.0)
|
|
# Part of the Fusion Plating product family.
|
|
|
|
{
|
|
'name': 'Fusion Plating — Customer Portal',
|
|
'version': '19.0.2.1.1',
|
|
'category': 'Manufacturing/Plating',
|
|
'summary': 'Customer-facing portal for plating shops: online RFQ, job status, '
|
|
'CoC downloads, invoice access.',
|
|
'description': """
|
|
Fusion Plating — Customer Portal
|
|
================================
|
|
|
|
Part of the Fusion Plating product family by Nexa Systems Inc.
|
|
|
|
This module extends the Odoo portal with plating-specific customer-facing
|
|
features so a shop's customers can self-serve common requests:
|
|
|
|
* Online Request for Quote (RFQ) submission with drawing uploads
|
|
* Track production job status (received → in process → quality → shipped)
|
|
* Download Certificates of Conformance (CoC) for completed jobs
|
|
* Reference invoice numbers and tracking shipments
|
|
* Submit complaints and follow up on resolution
|
|
|
|
Design principles
|
|
-----------------
|
|
1. Extends, never modifies, the fusion_plating core.
|
|
2. Reuses Odoo's standard portal layout, breadcrumbs, and pager.
|
|
3. Theme-aware: respects portal light/dark theme via Bootstrap CSS variables.
|
|
4. No client-specific strings; all labels are translatable.
|
|
5. Works on both Odoo Community and Enterprise editions.
|
|
|
|
Copyright (c) 2026 Nexa Systems Inc. All rights reserved.
|
|
""",
|
|
'author': 'Nexa Systems Inc.',
|
|
'website': 'https://www.nexasystems.ca',
|
|
'maintainer': 'Nexa Systems Inc.',
|
|
'support': 'support@nexasystems.ca',
|
|
'license': 'OPL-1',
|
|
'price': 0.00,
|
|
'currency': 'CAD',
|
|
'depends': [
|
|
'fusion_plating',
|
|
'fusion_plating_configurator',
|
|
'portal',
|
|
'website',
|
|
'mail',
|
|
'sale_management',
|
|
'account',
|
|
'stock',
|
|
],
|
|
'data': [
|
|
'security/fp_portal_security.xml',
|
|
'security/ir.model.access.csv',
|
|
'data/fp_sequence_data.xml',
|
|
'views/fp_quote_request_views.xml',
|
|
'views/fp_portal_dashboard.xml',
|
|
'views/fp_portal_templates.xml',
|
|
'views/fp_portal_configurator_templates.xml',
|
|
'views/fp_portal_breadcrumbs.xml',
|
|
'views/fp_menu.xml',
|
|
],
|
|
'assets': {
|
|
'web.assets_frontend': [
|
|
'fusion_plating_portal/static/src/scss/fusion_plating_portal.scss',
|
|
'fusion_plating_portal/static/src/js/fp_rfq_form.js',
|
|
],
|
|
},
|
|
'demo': [
|
|
'data/fp_demo_portal_data.xml',
|
|
],
|
|
'installable': True,
|
|
'application': False,
|
|
'auto_install': False,
|
|
}
|