Files
Odoo-Modules/fusion_plating/fusion_plating_jobs/scripts
gsinghpal 8c76a16366 chore(plating): de-dash shipped code + intake-neutral customer emails
Replace em-dashes and en-dashes with hyphens across 789 shipped source
files (py/xml/js/scss) so the delivered module reads as human-written;
em-dashes had become a recognizable AI-generated tell. Internal .md dev
notes are excluded. The WO-sticker mojibake strippers keep their dash
search targets (now written — / –). No logic changes: comments
and display strings only; validated with py_compile + lxml parse.

Rewrite the 7 customer notification emails to be intake-neutral
(ship-in / drop-off / pickup) and repair-aware, and fix the Shipped
email documents line (packing slip vs bill of lading; certificate only
when issued). Subjects use a hyphen separator.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-05 00:16:19 -04:00
..

Native job migration scripts

migrate_to_fp_jobs.py

Copies live mrp.production / mrp.workorder records into the native fp.job / fp.job.step model. Idempotent — safe to run multiple times.

Usage

Run from the host (e.g. entech) using odoo shell:

ssh pve-worker5 "pct exec 111 -- bash -c 'su - odoo -s /bin/bash -c \"/usr/bin/odoo shell -c /etc/odoo/odoo.conf -d admin\" < /mnt/extra-addons/custom/fusion_plating_jobs/scripts/migrate_to_fp_jobs.py'"

Or interactively from odoo shell (Python exec builtin, not a shell call):

exec(open('/mnt/extra-addons/custom/fusion_plating_jobs/scripts/migrate_to_fp_jobs.py').read())

What it does

  1. For every mrp.production record, creates a parallel fp.job with the same name and fields. Skips MOs that already have a fp.job mirror (fp.job.legacy_mrp_production_id == mo.id).
  2. For every mrp.workorder record, creates a parallel fp.job.step. Skips already-migrated WOs.
  3. Migrates mrp.workorder.time_ids to fp.job.step.timelog.
  4. Rebinds cross-references on dependent models (batches, holds, certs, deliveries, portal jobs, racking inspections).
  5. Audit log written to /tmp/fp_jobs_migration.log and to a chatter post on each migrated job.

Safety

  • Idempotent. Re-running skips already-migrated records.
  • Read-only on legacy MO/WO records. Original data untouched.
  • Cross-reference rebinds add new x_fc_job_id / x_fc_step_id values without removing legacy production_id / workorder_id values. Both stay populated for the 2-week shadow period.
  • Wrap in a transaction (default for odoo shell); if anything fails, rollback.

Pre-migration audit

Run audit_pre_migration.py first to see what's about to happen. The script uses Python's exec builtin to load the file inside the running shell session — no shell exec involved.

Reports counts of MO/WO/dependent records and any data-quality concerns (MOs with no recipe, WOs with no work centre, etc).

Post-migration audit

Run audit_post_migration.py after to verify counts match.

Reports row counts on fp.job, fp.job.step, and confirms all dependent records have new x_fc_*_id values.