f4e1f9d218
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>
66 lines
2.4 KiB
Python
66 lines
2.4 KiB
Python
# -*- coding: utf-8 -*-
|
|
# Copyright 2026 Nexa Systems Inc.
|
|
# License OPL-1 (Odoo Proprietary License v1.0)
|
|
# Part of the Fusion Plating product family.
|
|
|
|
{
|
|
'name': 'Fusion Plating — Quality Bridge (EE)',
|
|
'version': '19.0.1.0.1',
|
|
'category': 'Manufacturing/Plating',
|
|
'summary': 'Enterprise bridge: mirrors Fusion Plating NCRs into Odoo EE '
|
|
'quality.alert for native dashboard integration. Auto-installs '
|
|
'when EE quality and fusion_plating_quality are both present.',
|
|
'description': """
|
|
Fusion Plating — Quality Bridge (Enterprise)
|
|
============================================
|
|
|
|
Part of the Fusion Plating product family by Nexa Systems Inc.
|
|
|
|
One-way sync from Fusion Plating NCRs to Odoo EE quality.alert records.
|
|
|
|
Shops on Odoo Enterprise running both modules continue to work primarily
|
|
in Fusion Plating's QMS (which is CE + EE compatible), while getting the
|
|
benefit of EE's native quality dashboards on the same data.
|
|
|
|
How it works
|
|
------------
|
|
* When a Fusion Plating NCR is created or updated, a mirrored
|
|
``quality.alert`` record is created (or updated) automatically.
|
|
* The sync is ONE-WAY — NCR is the source of truth. Changes made
|
|
directly to the EE quality.alert are NOT pushed back into the NCR.
|
|
* A dedicated "Plating Quality" team is created in the EE quality
|
|
module so mirrored alerts land in their own distinct team and do
|
|
not pollute the default quality dashboards.
|
|
* Per-NCR opt-out is available via the ``x_fc_auto_sync`` field.
|
|
|
|
Installation
|
|
------------
|
|
This module has ``auto_install = True``: it installs itself automatically
|
|
as soon as both ``fusion_plating_quality`` and ``quality`` (EE) are
|
|
present in the database. Community Edition users who do not have the EE
|
|
``quality`` module will never see this bridge — the Fusion Plating QMS
|
|
remains fully self-contained.
|
|
|
|
Copyright (c) 2026 Nexa Systems Inc. All rights reserved.
|
|
""",
|
|
'author': 'Nexa Systems Inc.',
|
|
'website': 'https://www.nexasystems.ca',
|
|
'maintainer': 'Nexa Systems Inc.',
|
|
'support': 'support@nexasystems.ca',
|
|
'license': 'OPL-1',
|
|
'price': 0.00,
|
|
'currency': 'CAD',
|
|
'depends': [
|
|
'fusion_plating_quality',
|
|
'quality',
|
|
],
|
|
'data': [
|
|
'security/ir.model.access.csv',
|
|
'data/quality_alert_team_data.xml',
|
|
'views/fp_ncr_views.xml',
|
|
],
|
|
'installable': True,
|
|
'application': False,
|
|
'auto_install': True,
|
|
}
|