Files
Odoo-Modules/fusion_plating/fusion_plating_quality/security/fp_quality_security.xml
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

31 lines
1.1 KiB
XML

<?xml version="1.0" encoding="utf-8"?>
<!--
Copyright 2026 Nexa Systems Inc.
License OPL-1 (Odoo Proprietary License v1.0)
Part of the Fusion Plating product family.
-->
<odoo>
<!--
This module reuses the core groups from fusion_plating:
fusion_plating.group_fusion_plating_operator
fusion_plating.group_fusion_plating_supervisor
fusion_plating.group_fusion_plating_manager
fusion_plating.group_fusion_plating_admin
No new res.groups records are introduced here. All access control
is expressed in security/ir.model.access.csv via those existing
groups, so a single user role works across the core and the QMS.
-->
<!-- Multi-company rule for Contract Reviews (Sub 4). -->
<record id="fp_contract_review_company_rule" model="ir.rule">
<field name="name">Fusion Plating: Contract Review - multi-company</field>
<field name="model_id" ref="model_fp_contract_review"/>
<field name="global" eval="True"/>
<field name="domain_force">[('company_id', 'in', company_ids)]</field>
</record>
</odoo>