ad553b1082
Both portals share the existing fusion.repair.intake.service so behaviour
stays identical across all three intake surfaces (backend wizard,
sales rep portal, public client portal).
Sales rep portal
- Hard depends on fusion_authorizer_portal (reuses is_sales_rep_portal
flag + group_sales_rep_portal scaffolding)
- /my/repair/new - mobile-friendly intake form with phone-first
partner search (jsonrpc lookup), category select, third-party flag,
urgency, photo capture
- /my/repairs - list of repairs the rep submitted (paginated)
- /my/repair/<id> - read-only detail with status, equipment, scheduled
visit
- Interaction-class JS (Odoo 19 public.interactions), safe DOM construction
- Mobile SCSS with 44px tap targets, sticky CTA on small screens
- Record rule scopes portal users to repairs where
x_fc_intake_user_id = user.id
Public client portal
- auth='public' - voicemail-ready /repair URL
- /repair - landing page with 911 disclaimer and Start CTA
- /repair/new - single-page form: contact, equipment, issue, urgency,
optional photos. QR pre-fill via ?sn=<serial>
- /repair/submit - CSRF + honeypot + per-IP rate limit (configurable);
finds or creates partner; calls intake service with sudo
- /repair/thanks - confirmation with reference number
- /repair/lookup_phone (jsonrpc) - safe partner match returning ONLY
masked name (first + last initial) + city (no other PII leakage)
Security fix: technician record rule on repair.order now uses STORED
fields (technician_id + additional_technician_ids) instead of the
non-stored all_technician_ids compute, which was failing SQL generation.
Verified end-to-end on local westin-v19:
- Sales rep create via intake service with the rep user context creates
the repair with x_fc_intake_source='sales_rep_portal' and proper
activities
- /repair/submit posts urlencoded data -> creates partner + repair
('BR-WA/RO/00010', source='client_portal', urgency='urgent') ->
redirects to /repair/thanks with the reference
Co-authored-by: Cursor <cursoragent@cursor.com>
106 lines
3.6 KiB
Python
106 lines
3.6 KiB
Python
# -*- coding: utf-8 -*-
|
|
# Copyright 2024-2026 Nexa Systems Inc.
|
|
# License OPL-1 (Odoo Proprietary License v1.0)
|
|
|
|
{
|
|
'name': 'Fusion Repairs',
|
|
'version': '19.0.1.0.0',
|
|
'category': 'Inventory/Repairs',
|
|
'summary': 'Guided medical equipment repair intake, dispatch, maintenance, and self-service portal',
|
|
'description': """
|
|
Fusion Repairs
|
|
==============
|
|
|
|
Comprehensive repairs and maintenance management for medical equipment retailers
|
|
and service providers (hospital beds, wheelchairs, stairlifts, porch lifts,
|
|
walkers, mattresses, rollators).
|
|
|
|
Phase 1 - MVP
|
|
-------------
|
|
- Three intake surfaces sharing one service layer:
|
|
* Backend wizard for CS reps on the phone
|
|
* Sales rep portal (/my/repair/new) for reps on the road
|
|
* Public client self-service portal (/repair) - voicemail ready
|
|
- Guided question templates per medical equipment category
|
|
- Phone-first partner lookup with duplicate-call detection
|
|
- Multi-equipment per call (one repair.order per unit)
|
|
- Photo / video capture during intake
|
|
- Third-party equipment support (equipment we didn't sell)
|
|
- Auto warranty detection from original sale order
|
|
- Office notification recipients + 4 follow-up activities
|
|
- repair.order extensions linked to fusion.technician.task
|
|
|
|
Phase 2-4 (roadmap)
|
|
-------------------
|
|
- AI self-check engine with strict medical safety guardrails
|
|
- Upsell engine and direct-buy parts/plans
|
|
- Repair warranty tracking (free re-do window)
|
|
- Visit report wizard with Poynt terminal payment
|
|
- Maintenance contracts with client self-booking
|
|
- Weekend safety on-call paging
|
|
- SMS notifications, compliance certificates, analytics
|
|
|
|
Copyright (C) 2024-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': [
|
|
'base',
|
|
'mail',
|
|
'portal',
|
|
'website',
|
|
'sale_management',
|
|
'stock',
|
|
'repair',
|
|
'maintenance',
|
|
'fusion_tasks',
|
|
'fusion_poynt',
|
|
'fusion_authorizer_portal',
|
|
],
|
|
'data': [
|
|
# Security
|
|
'security/security.xml',
|
|
'security/ir.model.access.csv',
|
|
# Data (must load before views that reference records)
|
|
'data/ir_sequence_data.xml',
|
|
'data/ir_config_parameter_data.xml',
|
|
'data/mail_activity_type_data.xml',
|
|
'data/mail_template_data.xml',
|
|
'data/repair_product_category_data.xml',
|
|
'data/intake_template_data.xml',
|
|
# Views
|
|
'views/repair_product_category_views.xml',
|
|
'views/intake_template_views.xml',
|
|
'views/repair_order_views.xml',
|
|
'views/res_partner_views.xml',
|
|
'views/res_users_views.xml',
|
|
'views/res_config_settings_views.xml',
|
|
# Portal templates
|
|
'views/portal_sales_rep_templates.xml',
|
|
'views/portal_client_repair_templates.xml',
|
|
# Wizard
|
|
'wizard/repair_intake_wizard_views.xml',
|
|
# Menus (last, after all referenced actions exist)
|
|
'views/menus.xml',
|
|
],
|
|
'assets': {
|
|
'web.assets_backend': [
|
|
# Phase 2+: history_sidebar.js, signature_pad.js, etc.
|
|
],
|
|
'web.assets_frontend': [
|
|
'fusion_repairs/static/src/scss/portal_repair_mobile.scss',
|
|
'fusion_repairs/static/src/scss/portal_client_repair.scss',
|
|
'fusion_repairs/static/src/js/portal_repair_intake.js',
|
|
],
|
|
},
|
|
'images': ['static/description/icon.png'],
|
|
'installable': True,
|
|
'application': True,
|
|
'auto_install': False,
|
|
}
|