Files
Odoo-Modules/fusion_repairs/wizard/repair_visit_report_wizard_views.xml
gsinghpal 7727745b73 feat(fusion_repairs): Phase 2 - service catalogue, visit report, warranty, Poynt
Service catalogue
- New fusion.repair.service.catalog model: named service entries per
  equipment category with symptom keywords, estimated hours / cost,
  default parts, auto_schedule flag, optional pricelist override
- find_best_match() scores candidates by symptom-keyword overlap against
  intake text hints (issue summary + category + notes)
- Intake service wires it in: on submit, the matcher sets
  x_fc_service_catalog_id + x_fc_estimated_duration + x_fc_estimated_cost
  and (when auto_schedule=True) creates a draft dispatch task
- Double-task guard: if catalogue match already created a task, the
  urgency-based dispatch skips so we never duplicate

Visit report wizard
- fusion.repair.visit.report.wizard with labour hours + parts lines +
  technician notes + 'found another issue' branch
- Computes actual cost = (labour x service_product.list_price) + parts
- Compares against estimate -> sets requires_requote when variance
  exceeds configured threshold (% or $); shows warning banner inline
- On confirm: writes actuals back to repair, posts notes to chatter,
  optionally spawns a follow-up repair (T5 'found another issue')

Repair warranty
- New fusion.repair.warranty.coverage model (start/expiry, partner,
  product, lot, active flag)
- find_active_for(partner, product, lot) returns the most-recent active
  coverage
- Intake service auto-checks: when a new repair lands on an equipment
  that has active warranty coverage, posts a chatter banner so the
  office knows the work may be free under our 30/90-day re-do policy
  (manager review still required; never auto-zeros pricing)

Repair form
- Header: Visit Report + Collect Payment buttons (gated by group)
- action_collect_payment looks up the linked posted unpaid invoice on
  the repair SO and opens the Poynt wizard (action_open_poynt_payment_wizard)

AI intake summary
- _generate_ai_summary calls self.env['fusion.api.service'].call_openai
  with consumer='fusion_repairs', feature='intake_triage'
- Strict system prompt: no medical advice, no diagnoses, no recommending
  stop equipment use; ~80 words; plain English
- Try/fallback per fusion-api-integration.mdc: if fusion_api not
  installed or call fails -> silently skip; intake never blocked

Verified end-to-end on local westin-v19:
- Stairlift motor intake -> catalogue match -> estimated $500/2h -> auto
  dispatch task (count=1, not duplicated)
- Visit report: 2.5h x $250 + $100 parts = $725 actual vs $500 estimated
  = 45% variance -> requires_requote=True
- Warranty: 30-day coverage on the completed repair; second repair on
  same partner triggers warranty banner in chatter

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-20 21:57:33 -04:00

65 lines
2.8 KiB
XML

<?xml version="1.0" encoding="utf-8"?>
<odoo>
<record id="view_repair_visit_report_wizard_form" model="ir.ui.view">
<field name="name">fusion.repair.visit.report.wizard.form</field>
<field name="model">fusion.repair.visit.report.wizard</field>
<field name="arch" type="xml">
<form string="Visit Report">
<sheet>
<group>
<group>
<field name="repair_id" readonly="1"/>
<field name="technician_id"
options="{'no_create': True}"/>
</group>
<group>
<field name="labour_hours"/>
</group>
</group>
<separator string="Parts Used"/>
<field name="parts_line_ids">
<list editable="bottom">
<field name="product_id"/>
<field name="quantity"/>
<field name="unit_price" widget="monetary"/>
<field name="subtotal" widget="monetary"/>
</list>
</field>
<separator string="Cost Reconciliation"/>
<group>
<group>
<field name="estimated_cost" widget="monetary"/>
<field name="actual_cost" widget="monetary"/>
</group>
<group>
<field name="variance_pct" widget="float" digits="[12,1]"/>
<field name="requires_requote"/>
<field name="company_currency_id" invisible="1"/>
</group>
</group>
<div class="alert alert-warning" role="alert"
invisible="not requires_requote">
Variance exceeds the configured threshold. Saving will
mark the repair as <strong>Requires Re-Quote</strong>;
a manager must review before invoicing.
</div>
<separator string="Outcome"/>
<field name="notes"/>
<field name="found_another_issue"/>
</sheet>
<footer>
<button string="Save Visit Report"
name="action_confirm"
type="object"
class="btn-primary"/>
<button string="Cancel" class="btn-secondary" special="cancel"/>
</footer>
</form>
</field>
</record>
</odoo>