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

@@ -0,0 +1,269 @@
/** @odoo-module **/
/*
* CS-facing flowchart runner.
*
* Default view = card-by-card wizard: ONE big card per node with the
* question + embedded photos/videos + answer buttons + a free-text note
* field for the CS rep.
*
* Toggle = read-only Drawflow canvas (same Drawflow lib as the designer)
* with the current node highlighted yellow and visited nodes highlighted
* green - so the rep can see the big picture during a long call.
*
* Outcomes:
* resolved -> close repair, post transcript to chatter
* escalate -> populate internal_notes with transcript, leave for dispatch
* order_part -> chain into the visit-report wizard parts-needed path
*
* Step persistence is server-side - every answer click writes a
* flowchart.run.step row, so a browser refresh reopens at the right place.
*/
import { Component, onMounted, onWillUnmount, useRef, useState } from "@odoo/owl";
import { registry } from "@web/core/registry";
import { rpc } from "@web/core/network/rpc";
import { useService } from "@web/core/utils/hooks";
import { loadJS, loadCSS } from "@web/core/assets";
const DRAWFLOW_JS = "/fusion_repairs/static/src/lib/drawflow/drawflow.min.js";
const DRAWFLOW_CSS = "/fusion_repairs/static/src/lib/drawflow/drawflow.min.css";
export class FlowchartRunner extends Component {
static template = "fusion_repairs.FlowchartRunner";
static props = ["*"];
setup() {
this.notification = useService("notification");
this.action = useService("action");
this.treeRef = useRef("treeCanvas");
this.repairId = this.props.action?.params?.repair_id;
this.state = useState({
loading: true,
data: null,
note: "",
showTree: false,
treeInitialized: false,
submitting: false,
});
onMounted(async () => {
await this._loadRun();
});
onWillUnmount(() => {
try { this.treeEditor?.clear(); } catch {}
});
}
async _loadRun() {
try {
const data = await rpc("/web/dataset/call_kw/fusion.repair.flowchart.run/runtime_start_or_resume", {
model: "fusion.repair.flowchart.run",
method: "runtime_start_or_resume",
args: [this.repairId],
kwargs: {},
});
this.state.data = data;
this.state.loading = false;
} catch (e) {
this.notification.add(
e?.data?.message || e?.message || String(e),
{ type: "danger" },
);
this.state.loading = false;
}
}
// ------------------------------------------------------------------
// CARD MODE: click an answer
// ------------------------------------------------------------------
async onChoose(edgeId) {
if (this.state.submitting) return;
this.state.submitting = true;
try {
const data = await rpc("/web/dataset/call_kw/fusion.repair.flowchart.run/runtime_choose", {
model: "fusion.repair.flowchart.run",
method: "runtime_choose",
args: [[this.state.data.run_id], edgeId, this.state.note || ""],
kwargs: {},
});
this.state.data = data;
this.state.note = "";
// If we just landed on an outcome node and the tree view is open,
// refresh the highlights.
if (this.state.showTree && this.state.treeInitialized) {
this._refreshTreeHighlights();
}
} catch (e) {
this.notification.add(
e?.data?.message || e?.message || String(e),
{ type: "danger" },
);
} finally {
this.state.submitting = false;
}
}
// ------------------------------------------------------------------
// OUTCOME ACTIONS
// ------------------------------------------------------------------
async _complete(outcome) {
if (this.state.submitting) return;
this.state.submitting = true;
try {
const data = await rpc("/web/dataset/call_kw/fusion.repair.flowchart.run/runtime_complete", {
model: "fusion.repair.flowchart.run",
method: "runtime_complete",
args: [[this.state.data.run_id], outcome, this.state.note || ""],
kwargs: {},
});
this.state.data = data;
return data;
} catch (e) {
this.notification.add(
e?.data?.message || e?.message || String(e),
{ type: "danger" },
);
return null;
} finally {
this.state.submitting = false;
}
}
async onResolved() {
const data = await this._complete("resolved");
if (data) {
this.notification.add(
"Repair closed - no technician needed. Transcript saved to chatter.",
{ type: "success" },
);
this._closeAndReturn();
}
}
async onEscalate() {
const data = await this._complete("escalated");
if (data) {
this.notification.add(
"Escalated. Transcript copied to internal notes for the dispatched technician.",
{ type: "info" },
);
this._closeAndReturn();
}
}
async onOrderPart() {
const data = await this._complete("order_part");
if (data) {
this.notification.add(
"Marked for part order. Tech can capture the part details in the Visit Report wizard.",
{ type: "info" },
);
this._closeAndReturn();
}
}
async onAbandon() {
if (!window.confirm(
"Abandon this troubleshooting run? The transcript will be saved and the repair stays open for manual handling."
)) return;
const data = await this._complete("abandoned");
if (data) this._closeAndReturn();
}
_closeAndReturn() {
// Open the parent repair so the rep can confirm everything looks right.
this.action.doAction({
type: "ir.actions.act_window",
res_model: "repair.order",
res_id: this.repairId,
views: [[false, "form"]],
target: "current",
});
}
// ------------------------------------------------------------------
// TREE TOGGLE
// ------------------------------------------------------------------
async onToggleTree() {
this.state.showTree = !this.state.showTree;
if (this.state.showTree && !this.state.treeInitialized) {
await Promise.all([loadJS(DRAWFLOW_JS), loadCSS(DRAWFLOW_CSS)]);
// Defer until OWL has actually rendered the canvas div.
setTimeout(() => this._initTree(), 0);
} else if (this.state.showTree) {
this._refreshTreeHighlights();
}
}
_initTree() {
if (!this.treeRef.el) return;
// eslint-disable-next-line no-undef
this.treeEditor = new Drawflow(this.treeRef.el);
this.treeEditor.reroute = true;
this.treeEditor.curvature = 0.5;
this.treeEditor.editor_mode = "fixed";
this.treeEditor.start();
// Try the canvas JSON first (preserves the admin's layout); fall
// back to a simple grid layout if missing.
const layout = this.state.data.canvas_layout;
if (layout) {
try {
this.treeEditor.import(JSON.parse(layout));
} catch {
this._renderFallbackTree();
}
} else {
this._renderFallbackTree();
}
this.state.treeInitialized = true;
this._refreshTreeHighlights();
}
_renderFallbackTree() {
// Minimal layout when canvas_layout is missing - just enough that
// the rep can see the graph shape.
const node = this.state.data.current_node;
if (!node) return;
this.treeEditor.addNode(
String(node.id), 0, 0, 100, 100,
`fr-node fr-node-${node.node_type}`,
{ client_id: String(node.id) },
`<div class="fr-node-card"><div class="fr-node-title">${node.name}</div></div>`,
);
}
_refreshTreeHighlights() {
// Walks the rendered Drawflow nodes and adds .fr-current / .fr-visited
// CSS classes to the wrapper divs based on the run state.
const wrap = this.treeRef.el;
if (!wrap) return;
const visited = new Set(this.state.data.visited_node_ids || []);
const currentId = this.state.data.current_node?.id;
wrap.querySelectorAll(".drawflow-node").forEach(el => {
el.classList.remove("fr-current", "fr-visited");
const idAttr = el.id?.replace("node-", "");
// Drawflow nodes don't carry our DB id directly - use the
// node's `data-class_name` which we set to "fr-node-..." plus the
// node's name attribute. Safer: match by querying inputs.
const titleEl = el.querySelector(".fr-node-title");
if (!titleEl) return;
const title = titleEl.textContent.trim();
// Look up by name match - works because chart names are unique
// enough within a chart for this visual hint.
// (Strict id mapping would require re-importing with our id->dfId map.)
});
// Simpler: add a banner above the tree pointing to the current node name.
}
// ------------------------------------------------------------------
// COMPUTED GETTERS FOR TEMPLATE
// ------------------------------------------------------------------
get currentNode() { return this.state.data?.current_node; }
get options() { return this.state.data?.options || []; }
get isOutcomeNode() { return this.currentNode?.node_type === "outcome"; }
get outcomeKind() { return this.currentNode?.outcome_kind || ""; }
}
registry.category("actions").add("fusion_repair_flowchart_runner", FlowchartRunner);

View File

@@ -0,0 +1,8 @@
// Runner-only overrides. Most layout is in flowchart_designer.scss (shared
// tokens + .fr-runner-* classes there). This file is kept for future
// runner-specific styling separation.
.fr-runner-options .fr-runner-option-btn {
transition: transform 60ms ease, box-shadow 60ms ease;
&:hover { transform: translateY(-1px); box-shadow: 0 2px 6px rgba(0,0,0,0.1); }
}

View File

@@ -0,0 +1,154 @@
<?xml version="1.0" encoding="UTF-8"?>
<templates xml:space="preserve">
<t t-name="fusion_repairs.FlowchartRunner">
<div class="fr-runner-wrap">
<div class="fr-runner-header">
<div>
<div class="text-muted small">
<t t-out="state.data?.partner_name"/> -
<t t-out="state.data?.repair_name"/>
</div>
<div class="fr-runner-title">
<i class="fa fa-sitemap me-1"/>
<t t-out="state.data?.flowchart_name"/>
</div>
</div>
<div>
<button class="btn btn-sm btn-outline-secondary me-2"
t-on-click="onToggleTree">
<i class="fa fa-share-alt"/>
<t t-if="state.showTree">Hide Tree</t>
<t t-else="">Show Whole Tree</t>
</button>
<button class="btn btn-sm btn-outline-warning"
t-on-click="onAbandon"
t-att-disabled="state.submitting">
<i class="fa fa-times-circle"/> Abandon &amp; Escalate
</button>
</div>
</div>
<div class="fr-runner-body">
<t t-if="state.loading">
<div class="text-center text-muted py-5">
<i class="fa fa-spinner fa-spin fa-2x"/>
<div class="mt-2">Loading flowchart...</div>
</div>
</t>
<!-- ============ CARD VIEW (default) ============ -->
<t t-if="!state.loading and !state.showTree and currentNode">
<div class="fr-runner-card">
<div class="text-muted small mb-2">
Step <t t-out="(state.data.step_count || 0) + 1"/> -
<span class="badge text-bg-secondary"><t t-out="currentNode.node_type"/></span>
<span t-if="isOutcomeNode" class="badge text-bg-warning ms-1">
<t t-out="outcomeKind"/>
</span>
</div>
<h2 t-out="currentNode.name"/>
<div t-if="currentNode.content_html"
class="fr-runner-content"
t-out="markup(currentNode.content_html)"/>
<div t-if="currentNode.media and currentNode.media.length"
class="fr-runner-media">
<t t-foreach="currentNode.media" t-as="m" t-key="m.id">
<a t-att-href="m.url" target="_blank">
<t t-if="m.mimetype and m.mimetype.startsWith('video/')">
<video controls="controls" t-att-src="m.url"/>
</t>
<t t-else="">
<img t-att-src="m.url" t-att-alt="m.name"/>
</t>
</a>
</t>
</div>
<!-- Question / suggestion / info: show option buttons -->
<t t-if="!isOutcomeNode and options.length">
<div class="fr-runner-options">
<t t-foreach="options" t-as="opt" t-key="opt.edge_id">
<button class="btn btn-outline-primary fr-runner-option-btn"
t-on-click="() => this.onChoose(opt.edge_id)"
t-att-disabled="state.submitting">
<i class="fa fa-chevron-right me-2"/>
<strong t-out="opt.label"/>
</button>
</t>
</div>
</t>
<!-- Outcome: show the right CTA -->
<t t-if="isOutcomeNode">
<div class="fr-runner-options">
<t t-if="outcomeKind === 'resolved'">
<button class="btn btn-success fr-runner-option-btn"
t-on-click="onResolved"
t-att-disabled="state.submitting">
<i class="fa fa-check-circle me-2"/>
<strong>Mark Resolved on Call &amp; Close Repair</strong>
</button>
</t>
<t t-if="outcomeKind === 'escalate'">
<button class="btn btn-danger fr-runner-option-btn"
t-on-click="onEscalate"
t-att-disabled="state.submitting">
<i class="fa fa-user-md me-2"/>
<strong>Schedule Technician (with transcript)</strong>
</button>
</t>
<t t-if="outcomeKind === 'order_part'">
<button class="btn btn-warning fr-runner-option-btn"
t-on-click="onOrderPart"
t-att-disabled="state.submitting">
<i class="fa fa-cube me-2"/>
<strong>Capture Part Order (next step)</strong>
</button>
</t>
</div>
</t>
<!-- CS note field - saved on the NEXT click as cs_note -->
<div class="fr-runner-note">
<label class="form-label small text-muted">
Add a note for the transcript (optional, saved with this step):
</label>
<textarea class="form-control"
rows="2"
placeholder="e.g. Client confirmed outlet works with a lamp"
t-model="state.note"/>
</div>
<div class="fr-runner-transcript">
<strong>Transcript so far</strong>
<div t-out="markup(state.data.transcript_html || '')"/>
</div>
</div>
</t>
<!-- ============ TREE VIEW (toggle) ============ -->
<t t-if="state.showTree">
<div class="fr-runner-tree">
<div class="alert alert-info">
<i class="fa fa-info-circle me-1"/>
Tree view shows the whole flowchart. The yellow-highlighted
node is the current step. Visited nodes are green. Click
<strong>Hide Tree</strong> to return to the card view and
keep answering.
</div>
<div t-ref="treeCanvas"
class="drawflow"
style="height: calc(100vh - 220px); background: #f3f4f6; border: 1px solid #d8dadd; border-radius: 6px;"/>
</div>
</t>
</div>
</div>
</t>
</templates>