429084e0bf
Scaffolds the fusion_repairs module that extends Odoo 19 repair.order with a guided medical-equipment intake workflow. Models - fusion.repair.product.category (8 medical equipment categories seeded) - fusion.repair.intake.template / .question / .answer (7 templates, 32 questions seeded across hospital bed, stairlift, porch lift, wheelchair, walker/rollator, mattress) - fusion.repair.intake.service (AbstractModel) - single entry point used by backend wizard, sales rep portal, and public client portal so all three surfaces produce identical outcomes - repair.order extensions (x_fc_intake_*, x_fc_third_party_equipment, x_fc_photo_ids, x_fc_urgency, x_fc_estimated/actual_cost, AI summary) - fusion.technician.task back-link (x_fc_repair_order_id) - res.partner service preferences (preferred tech, time window, access notes) - res.users repair extensions (skills, cost rate, on-call rotation fields) - res.config.settings for variance thresholds, portal URL, rate limit UI - Backend intake wizard with multi-equipment loop, third-party flag, photos - repair.order form: Intake tab, Photos, Pricing tab, AI tab, smart buttons (technician tasks, intake answers, original SO) - Kanban + list view urgency badges - Fusion Repairs app menu (New Service Call, Repair Orders, Config) Activities & Email - 4 follow-up activity types (CS callback, tech dispatch, visit follow-up, manager review) with urgency-tiered deadlines - 2 mail templates (client confirmation + office notification) with the same dark/light-safe styling as fusion_claims ADP templates Security - New res.groups.privilege + 3 groups (User, Dispatcher, Manager) - Reuses fusion_tasks.group_field_technician (do NOT recreate) - Reuses fusion_authorizer_portal.group_sales_rep_portal - Multi-company global rule + technician scoping rule on repair.order Verified end-to-end on local westin-v19 dev DB via odoo-shell - creates multiple repairs in one session, auto-creates dispatch task for urgent, attaches 4 activity types correctly per urgency tier and third-party flag. Co-authored-by: Cursor <cursoragent@cursor.com>
43 lines
1.2 KiB
Python
43 lines
1.2 KiB
Python
# -*- coding: utf-8 -*-
|
|
# Copyright 2024-2026 Nexa Systems Inc.
|
|
# License OPL-1 (Odoo Proprietary License v1.0)
|
|
|
|
from odoo import fields, models
|
|
|
|
|
|
class FusionTechnicianTaskRepairs(models.Model):
|
|
"""Adds the back-link from fusion.technician.task to repair.order so
|
|
repairs and tasks share one timeline.
|
|
"""
|
|
|
|
_inherit = 'fusion.technician.task'
|
|
|
|
x_fc_repair_order_id = fields.Many2one(
|
|
'repair.order',
|
|
string='Repair Order',
|
|
ondelete='set null',
|
|
index=True,
|
|
tracking=True,
|
|
help='Repair order this task fulfils. Set automatically when the intake '
|
|
'wizard auto-creates a draft task for urgent / safety calls.',
|
|
)
|
|
|
|
x_fc_repair_intake_session_id = fields.Char(
|
|
related='x_fc_repair_order_id.x_fc_intake_session_id',
|
|
string='Intake Session',
|
|
store=True,
|
|
index=True,
|
|
)
|
|
|
|
def action_view_repair_order(self):
|
|
self.ensure_one()
|
|
if not self.x_fc_repair_order_id:
|
|
return False
|
|
return {
|
|
'type': 'ir.actions.act_window',
|
|
'name': self.x_fc_repair_order_id.name,
|
|
'res_model': 'repair.order',
|
|
'view_mode': 'form',
|
|
'res_id': self.x_fc_repair_order_id.id,
|
|
}
|