feat(fusion_repairs): Bundle 11 - CS guided troubleshooting flowcharts + vendor PO

Two big workflow additions:

1. Visual drag-and-drop flowchart designer (Drawflow) + card-by-card runner
   (with show-whole-tree toggle) so admins build per-(category, symptom)
   decision trees with embedded photos/videos and CS walks callers through
   them on the phone. Resolved-on-call closes the repair; escalated copies
   the full transcript into internal_notes so the dispatched tech sees what
   was already tried before they arrive at the client.

2. Vendor + draft-PO + factory-tracking on the part-order capture. Tech on
   the phone with the factory picks the vendor from contacts, types the OEM
   part #, cost, ETA date (calendar widget), factory ticket #, RA #, ticks
   under_warranty, and the system auto-creates a draft purchase.order with
   the right product (looked up or created from OEM) + activity for the
   office on the ETA day + client email with ETA prominently shown and
   cost intentionally omitted.

NEW MODELS

fusion.repair.symptom.class - lookup table (category + name + code).
  Replaces the flat x_fc_issue_category Char on repair.order. Seeded with
  7 stairlift symptoms + lighter coverage for hospital bed / porch lift /
  lift chair. Equipment Class added to fusion.repair.product.category
  (this carried over from the Bundle 10 plan).

fusion.repair.flowchart + .node + .edge - design-time graph.
  - flowchart has name, category, symptom, version, published flag,
    canvas_layout (Drawflow JSON), node_ids, edge_ids, computed start_node
  - node has node_type (question / suggestion / info / outcome),
    content_html, media_ids (M2M ir.attachment for photos + videos),
    is_start, outcome_kind (resolved / escalate / order_part),
    canvas_x/y for Drawflow round-trip
  - edge has source, target, label, sequence - supports N-ary branching
    (not just Yes/No)
  - designer_load() and designer_save(payload) RPC API the OWL component
    consumes; save is atomic-replace + bumps version + soft-validates

fusion.repair.flowchart.run + .step - runtime sessions.
  - One run per repair, audited; runtime_start_or_resume() returns the
    existing in-progress run or creates a fresh one for the matching chart
  - runtime_choose(edge_id, cs_note) records a step + advances current_node
  - runtime_complete(outcome) snapshots final node + calls _apply_outcome:
      resolved   -> auto-close via action_repair_start + action_repair_end,
                    set x_fc_resolved_on_call, post transcript to chatter
      escalated  -> prepend transcript to repair.internal_notes so the tech
                    sees it first when they open the form
      order_part -> chatter note; tech opens visit-report wizard next
      abandoned  -> just save transcript
  - Each step snapshots node_name + chosen_label at write time so the
    transcript survives later chart edits without breaking.

REPAIR.ORDER EXTENSIONS

- x_fc_symptom_class_id (M2O) - new structured symptom field
- x_fc_resolved_on_call (Boolean, tracked) - true after a resolved outcome
- x_fc_flowchart_run_ids + x_fc_flowchart_run_count
- action_start_troubleshoot() - opens the runner client action, raises a
  helpful UserError if no symptom set or no published chart exists
- action_view_flowchart_runs() smart button
- x_fc_issue_category renamed string to "(legacy)" - kept for back-compat
  + AI prompt context; new intakes set the M2O

DRAWFLOW DESIGNER (OWL)

static/src/lib/drawflow/drawflow.min.{js,css} - vendored Drawflow 0.0.59
  (MIT). Loaded only in web.assets_backend, ~48KB total.

components/flowchart_designer/flowchart_designer.{js,xml,scss}:
  - Client action "fusion_repair_flowchart_designer" with full drag-drop
    canvas + zoom + pan
  - 4 custom node templates color-banded by type (question blue,
    suggestion green, info gray, outcome red/green/amber per outcome_kind)
  - Right-panel editor for selected node: title, type, outcome kind,
    content (HTML), media uploader (drag-drop or click), set-as-start
    toggle, per-outgoing-edge label editor
  - Save serializes Drawflow JSON to canvas_layout + atomic-replaces the
    structured node/edge rows via the designer_save RPC

CARD RUNNER (OWL)

components/flowchart_runner/flowchart_runner.{js,xml,scss}:
  - Client action "fusion_repair_flowchart_runner"
  - DEFAULT MODE: card-by-card. One big card per node, embedded photos +
    inline <video controls>, answer buttons sized for phone use, CS note
    textarea (saved as cs_note on the step), running transcript at the
    bottom
  - TOGGLE: "Show Whole Tree" loads the same Drawflow lib in read-only
    fixed mode, imports the canvas_layout JSON, highlights current node
    yellow / visited green via .fr-current / .fr-visited classes
  - Outcome buttons drive the right runtime_complete() call; success
    notifications + auto-return to the parent repair form
  - "Abandon & Escalate" header button at all times - transcript is saved
    even on bail-out so the dispatched tech still benefits

PART ORDER + VENDOR PO

repair.part.order new fields:
  vendor_partner_id (M2O res.partner, is_company domain), purchase_order_id
  (auto-created draft PO), product_id (auto-resolved or created),
  unit_cost (Monetary) + currency_id, internal_po_ref, factory_ticket_ref,
  factory_ra_number, under_warranty.

action_create_draft_po() - resolves product.product by OEM (default_code)
  or creates a new one in a "Spare Parts" product.category, creates a
  purchase.order in draft state with one line (product + qty + price_unit
  + date_planned from expected_date or +7d), stamps Westin's internal PO
  ref as partner_ref so the factory can find it on return. Office reviews
  and confirms via the normal Odoo flow.

_schedule_eta_activity() - schedules a Repair: Assign Technician activity
  on the parent repair.order due on expected_date, assigned to
  repair.user_id, so the office is reminded to call the client and book
  the return visit on the day parts arrive.

VISIT-REPORT WIZARD PARTLINE EXTENSIONS

Same new fields exposed inline on the partline list so the tech captures
everything on the phone with the factory in one form:
  vendor_partner_id (vendors-only filter), unit_cost + currency,
  expected_date (calendar widget) replacing expected_lead_days as the
  preferred input, under_warranty, internal_po_ref, factory_ticket_ref,
  factory_ra_number, create_draft_po (default True - auto-builds PO on
  submit when vendor + cost are both set).

CLIENT EMAIL TIGHTENED

email_template_parts_ordered:
  - Subject now includes ETA "Parts ordered for your stairlift - expected 2026-06-06"
  - Hero ETA panel: large blue-bordered card with "Expected Arrival" label
    and the date in 24px bold
  - Cost INTENTIONALLY OMITTED - "Our office will call you to confirm a
    return visit time. If you have any questions about pricing or
    scheduling, please reach out to our office directly."
  - "There is nothing for you to do right now." callout

UI

- repair.order form header: new "Start Troubleshooting" button (info
  style, sitemap icon, visible when state in (draft, confirmed,
  under_repair) AND symptom is set)
- repair.order form intake row: x_fc_symptom_class_id picker filtered to
  the category, x_fc_resolved_on_call display when true
- repair.part.order form: header button "Create Draft Purchase Order"
  + new Vendor / Cost / Warranty group + System group with the PO link
- Intake wizard equipment line: symptom_class_id picker
- New menus:
    Configuration > Symptom Classes
    Configuration > Troubleshooting Flowcharts
    Fusion Repairs > Troubleshooting Sessions (run history)

SECURITY

18 new ACL rows for the 6 new models, scoped Manager-full / User-read /
FieldTech-read. Flowchart runs and steps get write access for User so CS
can record steps; Manager owns flowchart + node + edge CRUD.

POST-MIGRATION (19.0.2.2.0)

Existing installs: walks all distinct (category, x_fc_issue_category) text
pairs on repair.order, creates a placeholder fusion.repair.symptom.class
per pair (or reuses an existing match by code/name), back-fills the new
x_fc_symptom_class_id M2O. Idempotent + safe to re-run.

DEPENDENCY

Added 'purchase' to depends (action_create_draft_po needs purchase.order).

VERIFIED END-TO-END on local westin-v19 (Margaret persona, 0 bugs):

  STEP 0 seed: chart v1 8 nodes / 12 edges / published, 7 stairlift
                  symptoms, stairlift class=lift_elevating
  STEP 1 CS creates RO-202605-60 with symptom Not Moving
  STEP 2 Start Troubleshooting -> client action tag returned
  STEP 3 walk run: Power on? Yes -> Seatbelt? Yes -> Swivel? Yes ->
                   outcome 'Still not moving - dispatch technician'
                   (outcome_kind=escalate)
  STEP 4 runtime_complete('escalated') -> internal_notes prepended with
                   CS troubleshooting summary
  STEP 5 visit-report parts_needed with vendor Handicare + cost $425 +
                   warranty + factory refs -> PART-00008 created + draft
                   PO 26690 auto-built with line "Handicare 1100 control
                   board" qty 1 @ $425, partner_ref WH-2026-1042
  STEP 6 mark_ordered -> client email queued (NO cost mentioned, ETA
                   shown prominently) + office activity scheduled for
                   2026-06-06
  STEP 7 fresh resume returns same run; resolved outcome auto-closes the
                   repair (state=done, x_fc_resolved_on_call=True)

Bumped to 19.0.2.2.0.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
gsinghpal
2026-05-27 12:50:06 -04:00
parent 4acf9d7f85
commit eb186cac3c
30 changed files with 3277 additions and 32 deletions

View File

@@ -320,6 +320,7 @@ class RepairIntakeWizard(models.TransientModel):
'urgency': eq.urgency,
'issue_summary': eq.issue_summary or '',
'issue_category': eq.issue_category or '',
'symptom_class_id': eq.symptom_class_id.id or False,
'internal_notes': eq.internal_notes or '',
'schedule_date': eq.scheduled_date or False,
'photo_attachment_ids': eq.photo_ids.ids if eq.photo_ids else [],
@@ -391,8 +392,17 @@ class RepairIntakeWizardEquipment(models.TransientModel):
help='One-line summary of what is wrong (e.g. "stairlift stops halfway up").',
)
issue_category = fields.Char(
string='Symptom Category',
help='Optional symptom tag for catalogue matching (e.g. "battery", "motor").',
string='Symptom Category (legacy text)',
help='Free-text symptom tag - kept for backwards compat. New intakes '
'should pick the structured Symptom M2O below.',
)
# Bundle 11: proper symptom classification - drives flowchart lookup.
symptom_class_id = fields.Many2one(
'fusion.repair.symptom.class',
string='Symptom',
domain="[('category_id', '=', repair_category_id)]",
help='Pick the symptom to enable the Start Troubleshooting button '
'on the resulting repair (if a published flowchart exists).',
)
internal_notes = fields.Text(string='Internal Notes')

View File

@@ -83,8 +83,12 @@
</group>
<field name="issue_summary"
placeholder="One-line summary (e.g. 'stairlift stops halfway up')"/>
<field name="symptom_class_id"
context="{'default_category_id': repair_category_id}"
options="{'no_quick_create': True}"
invisible="not repair_category_id"/>
<field name="issue_category"
placeholder="Symptom tag (e.g. battery, motor, remote)"/>
placeholder="Legacy free-text tag (optional)"/>
<field name="internal_notes" placeholder="Internal notes"/>
<separator string="Photos / Videos"/>
<field name="photo_ids" widget="many2many_binary"/>

View File

@@ -441,6 +441,12 @@ class RepairVisitReportWizard(models.TransientModel):
'mimetype': att.mimetype,
})
photo_ids.append(copied.id)
# Bundle 11: prefer the explicit calendar-picked expected_date,
# fall back to today + expected_lead_days.
expected = line.expected_date or (
fields.Date.context_today(self) + timedelta(days=line.expected_lead_days)
if line.expected_lead_days else False
)
part = PartOrder.create({
'repair_order_id': repair.id,
'description': line.description,
@@ -449,12 +455,33 @@ class RepairVisitReportWizard(models.TransientModel):
'quantity': line.quantity or 1.0,
'notes': line.notes,
'photo_ids': [(6, 0, photo_ids)] if photo_ids else False,
'expected_date': line.expected_lead_days and (
fields.Date.context_today(self)
+ timedelta(days=line.expected_lead_days)
) or False,
'expected_date': expected,
# Bundle 11 vendor / cost / warranty / factory refs
'vendor_partner_id': line.vendor_partner_id.id or False,
'unit_cost': line.unit_cost or 0.0,
'currency_id': line.currency_id.id or False,
'under_warranty': line.under_warranty,
'internal_po_ref': line.internal_po_ref or False,
'factory_ticket_ref': line.factory_ticket_ref or False,
'factory_ra_number': line.factory_ra_number or False,
})
max_lead = max(max_lead, int(line.expected_lead_days or 0))
# Auto-create the draft PO when the tech captured a vendor + cost
# AND opted in (create_draft_po default=True).
if line.create_draft_po and line.vendor_partner_id and line.unit_cost:
try:
part.action_create_draft_po()
except Exception:
_logger.exception(
'Could not auto-create draft PO for part %s on repair %s',
part.name, repair.name,
)
lead_days = (
line.expected_lead_days
if line.expected_lead_days
else (int((expected - fields.Date.context_today(self)).days)
if expected else 0)
)
max_lead = max(max_lead, int(lead_days or 0))
repair.write({
'x_fc_parts_awaiting': True,
'x_fc_parts_eta_date': (
@@ -618,11 +645,16 @@ class RepairVisitReportWizardLine(models.TransientModel):
class RepairVisitReportWizardPartLine(models.TransientModel):
"""Bundle 8: parts the tech needs the office to ORDER from the manufacturer.
"""Bundle 8 + 11: parts the tech needs the office to ORDER from the
manufacturer.
Captured during the visit report when outcome='parts_needed'; one record per
distinct part. On wizard confirm, each line creates a
fusion.repair.part.order which is the procurement-facing record.
Bundle 11 adds: vendor picker (filtered to vendors), unit cost, expected
arrival date (calendar widget), factory ticket/RA refs, and a warranty
flag - everything the tech captures over the phone with the factory.
"""
_name = 'fusion.repair.visit.report.wizard.partline'
_description = 'Visit Report - Part to Order'
@@ -638,17 +670,59 @@ class RepairVisitReportWizardPartLine(models.TransientModel):
help='Plain English (e.g. "Handicare 1100 right armrest").',
)
oem_part_number = fields.Char(string='OEM #')
manufacturer = fields.Char(string='Manufacturer')
manufacturer = fields.Char(string='Manufacturer (free text)')
quantity = fields.Float(default=1.0, required=True)
expected_lead_days = fields.Integer(
string='Lead Time (days)',
default=7,
help='Tech estimate. Office uses this to set client ETA expectations.',
)
expected_date = fields.Date(
string='Expected Arrival',
help='Calendar pick. If the factory confirmed a specific date, use it - '
'otherwise leave blank and the lead-time days will be used.',
)
notes = fields.Text(string='Notes for Procurement')
# Bundle 11: vendor + cost + warranty + factory tracking.
vendor_partner_id = fields.Many2one(
'res.partner',
string='Vendor',
domain="[('is_company', '=', True)]",
help='Pick the vendor from our contacts. Quickly searchable while '
'on the phone with the factory.',
)
unit_cost = fields.Monetary(
string='Unit Cost',
currency_field='currency_id',
)
currency_id = fields.Many2one(
'res.currency',
default=lambda self: self.env.company.currency_id,
)
under_warranty = fields.Boolean(
string='Factory Warranty',
help='Tick if the factory confirmed warranty coverage on the call.',
)
internal_po_ref = fields.Char(
string='PO # read to factory',
help='Westin PO number the tech gave the factory for tracking.',
)
factory_ticket_ref = fields.Char(string='Factory Ticket #')
factory_ra_number = fields.Char(
string='Factory RA #',
help='Return Authorization (when factory issues a warranty replacement).',
)
photo_ids = fields.Many2many(
'ir.attachment',
'fusion_repair_visit_partline_photo_rel',
'partline_id', 'attachment_id',
string='Photos',
)
create_draft_po = fields.Boolean(
string='Create draft PO',
default=True,
help='When ticked AND a vendor + cost are filled in, the wizard '
'auto-creates a draft purchase.order on submit so the office '
'can review and send it.',
)

View File

@@ -60,11 +60,21 @@
<list editable="bottom">
<field name="description"/>
<field name="oem_part_number"/>
<field name="manufacturer"/>
<field name="vendor_partner_id"
options="{'no_quick_create': True}"/>
<field name="quantity"/>
<field name="expected_lead_days"/>
<field name="notes" optional="show"/>
<field name="photo_ids" widget="many2many_binary"/>
<field name="unit_cost" widget="monetary"/>
<field name="currency_id" column_invisible="True"/>
<field name="expected_date" widget="date"/>
<field name="expected_lead_days" optional="hide"/>
<field name="under_warranty" optional="show"/>
<field name="internal_po_ref" optional="hide"/>
<field name="factory_ticket_ref" optional="hide"/>
<field name="factory_ra_number" optional="hide"/>
<field name="create_draft_po" optional="show"/>
<field name="manufacturer" optional="hide"/>
<field name="notes" optional="hide"/>
<field name="photo_ids" widget="many2many_binary" optional="show"/>
</list>
</field>