Files
Odoo-Modules/fusion_plating/fusion_plating_bridge_sign
gsinghpal f4e1f9d218 refactor(plating-sec): extend ACL sweep to 13 missed modules
The Phase B plan (commit 8eb2c2de) listed 12 modules to sweep, but the
codebase has 13 more modules with ACL CSVs referencing the old role
group xmlids. Backward-compat (Phase A's implied_ids chains) keeps
these working today, but the old groups will be deleted after the
30-day rollback window — so the sweep must cover ALL modules with
plating-group ACL refs to avoid post-rollback breakage.

Sweeps: batch, bridge_documents, bridge_maintenance, bridge_mrp
(uninstalled but file present), bridge_quality (planned removal),
bridge_sign, compliance, culture (retired), kpi, logistics,
notifications, portal, reports.

Pattern matches the original sweep:
  group_fusion_plating_operator → group_fp_technician
  group_fusion_plating_supervisor → group_fp_shop_manager_v2
  group_fusion_plating_manager → group_fp_manager
  group_fusion_plating_admin → group_fp_owner
  group_fp_accounting → group_fp_manager
  group_fp_receiving → group_fp_shop_manager_v2
  group_fp_estimator → group_fp_sales_rep
  group_fp_shop_manager (legacy) → group_fp_manager
  cgp_officer → group_fp_quality_manager
  cgp_designated_official → group_fp_owner

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-24 01:18:52 -04:00
..
2026-05-21 03:37:25 -04:00
2026-04-16 20:53:53 -04:00
2026-04-16 20:53:53 -04:00
2026-04-16 20:53:53 -04:00
2026-04-16 20:53:53 -04:00

Fusion Plating — E-Sign Bridge (EE)

Enterprise-only bridge module. Wires fusion_plating_quality into Odoo EE sign so customer CoC (Certificate of Conformance) acceptance can be captured as a legally-binding e-signature.

Copyright © 2026 Nexa Systems Inc. License: OPL-1

Behaviour

Trigger Result
Install both fusion_plating_quality and EE sign This bridge auto-installs
Install only the CE stack This module is never discovered — depends: sign hides it
FAIR reaches state approved "Send for Customer Signature" button appears in the header
Customer completes signature in Sign sign.request.state flips; bridge preserves back-reference

What it adds

On fusion.plating.fair:

  • x_fc_sign_request_id — M2o sign.request (the generated signing envelope)
  • x_fc_sign_request_state — related display of signing progress
  • x_fc_signed_date, x_fc_signed_by, x_fc_signed_pdf_id — final artefact
  • Header buttons: Send for Customer Signature / View Sign Request / Download Signed PDF
  • E-Signature notebook page on the FAIR form

What it does NOT do

  • Sync Sign status back into the FAIR automatically on every change. The EE sign module fires its own activities; this bridge only stores the back-reference and lets users navigate. A customer-delivered callback wiring sign.request state changes back onto FAIR is a future enhancement.
  • Work on Community Edition. By design.

Install

When you add EE sign to a site that already runs fusion_plating_quality, the bridge appears with auto_install=True and loads on the next update:

docker exec odoo-dev-app odoo -d fusion-dev -u base --stop-after-init