admin/Odoo-Modules
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
f19ca02e05886296488185fd4e8f7cf88593067f
Odoo-Modules/fusion_repairs/data/flowchart_stairlift_not_moving_data.xml
gsinghpal eb186cac3c 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>
2026-05-27 12:50:06 -04:00

252 lines
13 KiB
XML
Raw Blame History

<?xml version="1.0" encoding="utf-8"?>
<!--
Demo flowchart for the user's headline scenario: "Stairlift Not Moving".
Eight nodes covering the most common diagnostic decision points. Westin
can edit / extend this in the Drawflow designer; it's the template they
will fork to build the other six stairlift flowcharts + the other
equipment categories.
Tree shape (single-dash arrows so the ASCII art does not close this XML
comment):
[Start: Power on?]
Yes -> [Seatbelt fastened?]
No -> [Outcome: outlet/breaker]
[Seatbelt fastened?]
No -> [Suggestion: Fasten and retry]
Yes -> [Swivel rotated to forward?]
[Swivel rotated to forward?]
No -> [Suggestion: Rotate and retry]
Yes -> [Outcome: escalate to technician]
-->
<odoo>
<data noupdate="1">
<record id="flowchart_stairlift_not_moving" model="fusion.repair.flowchart">
<field name="name">Stairlift - Not Moving</field>
<field name="category_id" ref="category_stairlift"/>
<field name="symptom_class_id" ref="symptom_stairlift_not_moving"/>
<field name="published" eval="True"/>
<field name="description"><![CDATA[
<p>Standard diagnostic walk-through for a stairlift that is not responding
to its controls. Most common root causes (power, seatbelt, swivel lock)
are checked first; if all clear, dispatch a technician.</p>
]]></field>
</record>
<!-- ===== NODES ===== -->
<record id="flow_sl_nm_node_start" model="fusion.repair.flowchart.node">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="name">Is the power on?</field>
<field name="node_type">question</field>
<field name="is_start" eval="True"/>
<field name="sequence">10</field>
<field name="canvas_x">100</field>
<field name="canvas_y">100</field>
<field name="content_html"><![CDATA[
<p>Ask the client if the stairlift has power. Check:</p>
<ul>
<li>Is the unit plugged into the wall outlet?</li>
<li>Is the master key switch (usually on the carriage) turned ON?</li>
<li>Is the battery indicator LED lit?</li>
</ul>
]]></field>
</record>
<record id="flow_sl_nm_node_outlet" model="fusion.repair.flowchart.node">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="name">No power - check breaker</field>
<field name="node_type">suggestion</field>
<field name="sequence">20</field>
<field name="canvas_x">450</field>
<field name="canvas_y">20</field>
<field name="content_html"><![CDATA[
<p>Ask the client to:</p>
<ol>
<li>Test the wall outlet with a phone charger or lamp.</li>
<li>Check the home's electrical panel for a tripped breaker.</li>
<li>If the breaker is tripped, flip it OFF then ON.</li>
</ol>
]]></field>
</record>
<record id="flow_sl_nm_node_seatbelt" model="fusion.repair.flowchart.node">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="name">Is the seatbelt fastened?</field>
<field name="node_type">question</field>
<field name="sequence">30</field>
<field name="canvas_x">450</field>
<field name="canvas_y">200</field>
<field name="content_html"><![CDATA[
<p>Most stairlifts will not move unless the seatbelt safety
switch is engaged. Confirm the belt is buckled.</p>
]]></field>
</record>
<record id="flow_sl_nm_node_fasten" model="fusion.repair.flowchart.node">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="name">Fasten seatbelt and retry</field>
<field name="node_type">suggestion</field>
<field name="sequence">40</field>
<field name="canvas_x">800</field>
<field name="canvas_y">120</field>
<field name="content_html"><![CDATA[
<p>Have the client buckle the seatbelt and try the controls again.</p>
]]></field>
</record>
<record id="flow_sl_nm_node_swivel" model="fusion.repair.flowchart.node">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="name">Is the seat rotated to the forward (travel) position?</field>
<field name="node_type">question</field>
<field name="sequence">50</field>
<field name="canvas_x">800</field>
<field name="canvas_y">300</field>
<field name="content_html"><![CDATA[
<p>The swivel lock must be engaged in the forward position. If
the seat is partially turned, the stairlift will refuse to move.</p>
]]></field>
</record>
<record id="flow_sl_nm_node_rotate" model="fusion.repair.flowchart.node">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="name">Rotate seat to forward and retry</field>
<field name="node_type">suggestion</field>
<field name="sequence">60</field>
<field name="canvas_x">1150</field>
<field name="canvas_y">220</field>
<field name="content_html"><![CDATA[
<p>Ask the client to rotate the seat back to the forward
travel position until the swivel lock clicks. Then try again.</p>
]]></field>
</record>
<record id="flow_sl_nm_node_resolved" model="fusion.repair.flowchart.node">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="name">Working - resolved on call</field>
<field name="node_type">outcome</field>
<field name="outcome_kind">resolved</field>
<field name="sequence">100</field>
<field name="canvas_x">1500</field>
<field name="canvas_y">150</field>
<field name="content_html"><![CDATA[
<p>Great - the stairlift is moving again. Confirm with the client,
close the repair, and offer to book an annual safety inspection
if they have not had one recently.</p>
]]></field>
</record>
<record id="flow_sl_nm_node_escalate" model="fusion.repair.flowchart.node">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="name">Still not moving - dispatch technician</field>
<field name="node_type">outcome</field>
<field name="outcome_kind">escalate</field>
<field name="sequence">110</field>
<field name="canvas_x">1500</field>
<field name="canvas_y">350</field>
<field name="content_html"><![CDATA[
<p>Common fixes are exhausted. Likely root causes for a tech to investigate:</p>
<ul>
<li>Control board fault (most common - $300-$500 part)</li>
<li>Motor brushes worn</li>
<li>Track end-stop safety switch</li>
</ul>
<p>Escalate and the transcript will be visible to the tech before they arrive.</p>
]]></field>
</record>
<!-- ===== EDGES ===== -->
<record id="flow_sl_nm_edge_start_no" model="fusion.repair.flowchart.edge">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="source_node_id" ref="flow_sl_nm_node_start"/>
<field name="target_node_id" ref="flow_sl_nm_node_outlet"/>
<field name="label">No - no power</field>
<field name="sequence">10</field>
</record>
<record id="flow_sl_nm_edge_start_yes" model="fusion.repair.flowchart.edge">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="source_node_id" ref="flow_sl_nm_node_start"/>
<field name="target_node_id" ref="flow_sl_nm_node_seatbelt"/>
<field name="label">Yes - power is on</field>
<field name="sequence">20</field>
</record>
<record id="flow_sl_nm_edge_outlet_fixed" model="fusion.repair.flowchart.edge">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="source_node_id" ref="flow_sl_nm_node_outlet"/>
<field name="target_node_id" ref="flow_sl_nm_node_resolved"/>
<field name="label">Power restored - works now</field>
<field name="sequence">10</field>
</record>
<record id="flow_sl_nm_edge_outlet_no_fix" model="fusion.repair.flowchart.edge">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="source_node_id" ref="flow_sl_nm_node_outlet"/>
<field name="target_node_id" ref="flow_sl_nm_node_escalate"/>
<field name="label">Still no power</field>
<field name="sequence">20</field>
</record>
<record id="flow_sl_nm_edge_seatbelt_no" model="fusion.repair.flowchart.edge">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="source_node_id" ref="flow_sl_nm_node_seatbelt"/>
<field name="target_node_id" ref="flow_sl_nm_node_fasten"/>
<field name="label">No</field>
<field name="sequence">10</field>
</record>
<record id="flow_sl_nm_edge_seatbelt_yes" model="fusion.repair.flowchart.edge">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="source_node_id" ref="flow_sl_nm_node_seatbelt"/>
<field name="target_node_id" ref="flow_sl_nm_node_swivel"/>
<field name="label">Yes</field>
<field name="sequence">20</field>
</record>
<record id="flow_sl_nm_edge_fasten_works" model="fusion.repair.flowchart.edge">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="source_node_id" ref="flow_sl_nm_node_fasten"/>
<field name="target_node_id" ref="flow_sl_nm_node_resolved"/>
<field name="label">Works now</field>
<field name="sequence">10</field>
</record>
<record id="flow_sl_nm_edge_fasten_no" model="fusion.repair.flowchart.edge">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="source_node_id" ref="flow_sl_nm_node_fasten"/>
<field name="target_node_id" ref="flow_sl_nm_node_swivel"/>
<field name="label">Still not moving - try next check</field>
<field name="sequence">20</field>
</record>
<record id="flow_sl_nm_edge_swivel_no" model="fusion.repair.flowchart.edge">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="source_node_id" ref="flow_sl_nm_node_swivel"/>
<field name="target_node_id" ref="flow_sl_nm_node_rotate"/>
<field name="label">No - seat is turned</field>
<field name="sequence">10</field>
</record>
<record id="flow_sl_nm_edge_swivel_yes" model="fusion.repair.flowchart.edge">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="source_node_id" ref="flow_sl_nm_node_swivel"/>
<field name="target_node_id" ref="flow_sl_nm_node_escalate"/>
<field name="label">Yes - seat is forward</field>
<field name="sequence">20</field>
</record>
<record id="flow_sl_nm_edge_rotate_works" model="fusion.repair.flowchart.edge">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="source_node_id" ref="flow_sl_nm_node_rotate"/>
<field name="target_node_id" ref="flow_sl_nm_node_resolved"/>
<field name="label">Works now</field>
<field name="sequence">10</field>
</record>
<record id="flow_sl_nm_edge_rotate_no" model="fusion.repair.flowchart.edge">
<field name="flowchart_id" ref="flowchart_stairlift_not_moving"/>
<field name="source_node_id" ref="flow_sl_nm_node_rotate"/>
<field name="target_node_id" ref="flow_sl_nm_node_escalate"/>
<field name="label">Still not moving</field>
<field name="sequence">20</field>
</record>
</data>
</odoo>
Reference in New Issue View Git Blame Copy Permalink