Full end-to-end walk acting as customer, CS rep, dispatcher, technician,
and manager surfaced 6 real bugs (1 critical state-machine, 4 missing UX
wires, 1 docstring). Server endpoints existed for everything but several
were not wired into the templates.
B1 (HIGH) - Visit-report wizard never closed the repair
Tech submitted visit -> state stayed 'draft' -> x_fc_done_at never
stamped -> NPS cron never fired -> the whole post-visit flow died
silently. Customers never got their NPS email.
Fix: action_confirm() now drives the Odoo native state machine
draft -> action_validate (with _action_repair_confirm fallback) ->
action_repair_start -> action_repair_end. Each step guarded by the
current state and exception-logged. Leaves the repair open if:
- requires_requote=True (variance flag - office must re-quote)
- no_show=True (office reschedules)
- x_fc_is_quote_only (still a quote)
- found_another_issue spawned a stub
Posts a clear chatter line on success or failure.
Verified: e2e walk now shows state=done + x_fc_done_at stamped +
NPS cron fires + flags x_fc_nps_email_sent=True.
B2 (HIGH) - /repair/new form never called /repair/self_check
The AI self-check engine was the headline weekend feature but it was
invisible to the client. The endpoint worked server-side, just had
no frontend.
Fix: new portal_client_repair.js (Interaction class, registered on
registry.category('public.interactions')). 'Try 1-3 safe self-check
steps first' button POSTs to /repair/self_check, renders steps via
createElement + textContent (no innerHTML - all server output is
treated as untrusted text). Shows the AI's safety disclaimer on
every result. On escalate_immediately, shows a clear 'submit the
form, we'll come to you' message instead of the steps.
Verified: HTTP POST returns full JSON with instruction +
expected_result + disclaimer; new button + result panel appear in
rendered HTML.
B3 (HIGH) - No phone-lookup UI for returning clients
Same problem - endpoint existed but no UI. Returning clients had to
retype everything from scratch.
Fix:
- lookup_phone now returns a 'partners' array (id, name, email,
street, city) - cap of 3 results, rate-limited, every match logged
at INFO level for audit. Privacy compromise: a phone holder
deserves to see their own pre-fill; rate limit caps harvesting.
- JS lookup widget at the top of the form posts to /repair/lookup_phone
and pre-fills the 5 contact fields + writes the partner_id to a
hidden #fr_known_partner_id input.
- controller /repair/submit now trusts known_partner_id if present
(skips the phone re-match) so we don't create duplicate partners
when the lookup widget already identified the right one.
Verified: HTTP POST returns the 2 partner records we have for
+19055551234 with full id/name/email/street/city.
B4 (MEDIUM) - /repair?sn=<serial> from QR sticker did nothing
Spec: 'Client scans QR sticker - portal pre-fills the unit info.'
Reality: the form had no serial field; ?sn= was ignored.
Fix: new _resolve_serial_info(serial) on the controller resolves
the lot via stock.lot.search([('name','=',sn)]) and returns
{serial, lot_id, product_id, product_name, category_id}. Both
/repair (landing) and /repair/new pass it as serial_info template
context. Templates show 'Recognized X (Serial: Y)' + auto-select
the matching category in the dropdown. Hidden #fr_serial_number
carries it through to /repair/submit, which attaches the lot_id +
uses the QR category as fallback if user didn't pick one.
Verified: ?sn=stella23-20040164 produces 'Pre-filled from QR scan:'
banner + hidden input populated.
B5 (MEDIUM) - No upsell after submit
Spec required an upsell - 'reduce future calls'. Page was a bare
'Got it'.
Fix: /repair/thanks now shows a 2-card layout:
- 'Want to avoid this next time?' with 4 bullets (priority booking,
free inspection cert, discounted parts, annual reminder) +
'See our maintenance plans' CTA to /shop?category=maintenance
- 'What happens next' 4-step bulleted explanation
Verified: both cards render.
B6 (LOW) - SyntaxWarning '\-->' in repair_service_plan.py
Made the module docstring a raw string (r''') so the ASCII flowchart
arrows don't trigger Python's invalid-escape-sequence warning.
Bumped to 19.0.1.8.0.
Co-authored-by: Cursor <cursoragent@cursor.com>
127 lines
4.6 KiB
Python
127 lines
4.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.8.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/ir_cron_data.xml',
|
|
'data/mail_activity_type_data.xml',
|
|
'data/mail_template_data.xml',
|
|
'data/repair_product_category_data.xml',
|
|
'data/intake_template_data.xml',
|
|
'data/self_check_data.xml',
|
|
# Views
|
|
'views/repair_product_category_views.xml',
|
|
'views/intake_template_views.xml',
|
|
'views/service_catalog_views.xml',
|
|
'views/repair_warranty_views.xml',
|
|
'views/maintenance_contract_views.xml',
|
|
'views/repair_dashboard_views.xml',
|
|
'views/repair_inspection_views.xml',
|
|
'views/repair_order_views.xml',
|
|
'views/repair_service_plan_views.xml',
|
|
'views/sale_order_views.xml',
|
|
'views/technician_task_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',
|
|
'views/portal_maintenance_templates.xml',
|
|
# Wizards
|
|
'wizard/repair_intake_wizard_views.xml',
|
|
'wizard/repair_visit_report_wizard_views.xml',
|
|
'wizard/qr_sticker_wizard_views.xml',
|
|
# Reports
|
|
'report/qr_sticker_report.xml',
|
|
'report/inspection_certificate_report.xml',
|
|
# Menus (last, after all referenced actions exist)
|
|
'views/menus.xml',
|
|
],
|
|
'assets': {
|
|
'web.assets_backend': [
|
|
# Tokens MUST load first - dashboard.scss references its variables.
|
|
'fusion_repairs/static/src/scss/_fr_tokens.scss',
|
|
'fusion_repairs/static/src/scss/dashboard.scss',
|
|
'fusion_repairs/static/src/components/dashboard/dashboard.js',
|
|
'fusion_repairs/static/src/components/dashboard/dashboard.xml',
|
|
],
|
|
'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',
|
|
'fusion_repairs/static/src/js/portal_client_repair.js',
|
|
],
|
|
},
|
|
'images': ['static/description/icon.png'],
|
|
'installable': True,
|
|
'application': True,
|
|
'auto_install': False,
|
|
}
|