65c4d8801c
New fusion.repair.inspection.certificate model for the annual safety inspections required on stairlifts, porch lifts, and power wheelchairs in many jurisdictions. Model - mail.thread chatter-tracked; fields: name (CERT-YYYY-NNNN auto-seq), partner_id, product_id (filtered to safety-critical categories), lot_id, repair_order_id back-link, inspector_user_id (must be field staff), jurisdiction (selection: Ontario / BC / Alberta / Quebec / Other), issued_date, valid_for_months (default 12), expiry_date (computed, stored, uses relativedelta - correct month boundaries), status (non-stored compute: valid / expiring / expired / revoked), revoked, notes, last_reminder_band. - Unique constraint on certificate number (models.Constraint, not _sql_constraints, per project rule). - Sequence 'fusion.repair.inspection.certificate' with use_date_range=True so the counter resets each year (CERT-2026-0001 ... CERT-2027-0001). Visit report integration - New issue_inspection_cert checkbox on fusion.repair.visit.report.wizard. - When ticked AND the repair's category is safety_critical, action_confirm() creates the certificate via _create_inspection_certificate() and redirects to the cert form so the tech can print immediately. - Non-safety-critical equipment quietly skips with a chatter note explaining why. PDF report - web.html_container + web.external_layout, model bound so it appears as a Print action on the certificate form. - 'Certificate of Inspection' / 'Safety Inspected' gold-banner layout with client name, equipment, serial, jurisdiction, issued + expiry dates, inspector signature line, and the certificate number. - Print Certificate button in form header. Daily cron - cron_send_expiry_reminders runs at 09:00, sends two band-tracked reminders (30 days + 7 days before expiry) to the client. - New mail.template email_template_inspection_expiry_reminder with 4px amber accent, certificate ref, equipment, expiry date, and a CTA to call to book the re-inspection visit. - last_reminder_band on the cert prevents re-sending the same band. Backend wiring - New menu entry 'Fusion Repairs > Inspection Certificates'. - ACL: User read, Dispatcher write, Manager unlink. Field technicians can create (they need to issue from the field). - List view with red/amber/green status decoration. - Form with statusbar, header buttons (Print, Revoke with confirm), chatter. Verified end-to-end on local westin-v19: Stairlift repair RO-202605-15 -> visit-report with issue_inspection_cert=True -> CERT-2026-0001 issued (status=valid, expires 2027-05-21) Cert CERT-2026-0002 expiring in 30 days -> cron flagged last_reminder_band='30' (would email client). Bumped to 19.0.1.4.0 (minor bump for the new public-facing capability). Co-authored-by: Cursor <cursoragent@cursor.com>
56 lines
2.7 KiB
XML
56 lines
2.7 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<data noupdate="1">
|
|
<!-- Intake session reference. -->
|
|
<!-- Groups multiple repair.order records created from the same call. -->
|
|
<record id="seq_repair_intake_session" model="ir.sequence">
|
|
<field name="name">Repair Intake Session</field>
|
|
<field name="code">fusion.repair.intake.session</field>
|
|
<field name="prefix">RIS</field>
|
|
<field name="padding">6</field>
|
|
<field name="number_next">1</field>
|
|
<field name="number_increment">1</field>
|
|
<field name="company_id" eval="False"/>
|
|
</record>
|
|
|
|
<!-- Maintenance contract reference -->
|
|
<record id="seq_repair_maintenance_contract" model="ir.sequence">
|
|
<field name="name">Repair Maintenance Contract</field>
|
|
<field name="code">fusion.repair.maintenance.contract</field>
|
|
<field name="prefix">MC/</field>
|
|
<field name="padding">5</field>
|
|
<field name="number_next">1</field>
|
|
<field name="number_increment">1</field>
|
|
<field name="company_id" eval="False"/>
|
|
</record>
|
|
|
|
<!-- Inspection certificate reference: CERT-YYYY-NNNN, yearly reset. -->
|
|
<record id="seq_repair_inspection_certificate" model="ir.sequence">
|
|
<field name="name">Inspection Certificate</field>
|
|
<field name="code">fusion.repair.inspection.certificate</field>
|
|
<field name="prefix">CERT-%(year)s-</field>
|
|
<field name="padding">4</field>
|
|
<field name="number_next">1</field>
|
|
<field name="number_increment">1</field>
|
|
<field name="use_date_range" eval="True"/>
|
|
<field name="company_id" eval="False"/>
|
|
</record>
|
|
|
|
<!-- Date-based repair.order reference: RO-YYYYMM-NN, counter resets monthly.
|
|
use_date_range=True so Odoo creates an ir.sequence.date_range record
|
|
per month with its own number_next, giving each month a fresh -01.
|
|
%(year)s -> 4-digit year, %(month)s -> zero-padded month (per strftime %m). -->
|
|
<record id="seq_repair_order_monthly" model="ir.sequence">
|
|
<field name="name">Repair Order (RO-YYYYMM-NN)</field>
|
|
<field name="code">fusion.repair.order.monthly</field>
|
|
<field name="prefix">RO-%(year)s%(month)s-</field>
|
|
<field name="suffix"/>
|
|
<field name="padding">2</field>
|
|
<field name="number_next">1</field>
|
|
<field name="number_increment">1</field>
|
|
<field name="use_date_range" eval="True"/>
|
|
<field name="company_id" eval="False"/>
|
|
</record>
|
|
</data>
|
|
</odoo>
|