Files
Odoo-Modules/fusion_plating/fusion_plating_quality/views/fp_fair_views.xml
gsinghpal 269f9984ef feat(plating-views): Layer 3 — field/button gates per role
Phase D Task D5 of permissions overhaul. Adds explicit groups= to
form-level elements so non-matching roles don't even SEE the buttons
they can't use:

- SO Confirm button → group_fp_sales_manager (Sales Rep sees the SO
  in draft but no Confirm button — matches model-level gate from Phase G)
- SO pricing fields (price_unit/subtotal/total/untaxed/tax) →
  group_fp_sales_rep (Technician/Shop Manager don't see pricing if
  they navigate to an SO)
- Partner Account Hold tab → group_fp_manager (was the fold-in
  group_fp_accounting; the audit-finding-11 _administrator typo lives
  in res_partner.py and is Phase G's fix)
- CAPA Close + all state-transition buttons → group_fp_quality_manager;
  edit fields use readonly="not user_has_groups(...)" so Manager
  retains read+comment per spec section 2.C
- Audit Start/Findings/Close buttons → group_fp_quality_manager
- AVL Approve/Suspend/Reinstate/Remove → group_fp_quality_manager
  (model uses Suspend+Remove instead of spec's literal 'Disqualify';
  both surfaces gated, semantics match)
- Customer Spec edit fields → readonly for non-QM (Manager keeps
  read access per spec; only inputs lock)
- FAIR Approve/Reject buttons → group_fp_quality_manager (Submit-
  for-Review and Reset stay open to whoever created the FAIR)
- Certificate Issue button — Strategy B chosen: single button hidden
  when cert_type=nadcap_cert AND user is not QM. Cleaner than splitting
  into two buttons; no separate action_sign exists on fp.certificate
  (Issue is the sign+publish action). FAIR lives in its own model;
  fp.certificate only has nadcap_cert as a special type. The ir.rule
  from Phase C enforces model-level writes independently.
- CGP form buttons (7 view files: ai, controlled_good, psa,
  receipt_shipment, registration, security_incident, visitor) →
  group_fp_quality_manager on every action button

Defense in depth: ir.rules and ACLs (from Phases B + C) already
restrict model access. These view gates are the UI layer that
matches.

Concerns:
- Spec line 192 names 'sale.order view — x_fc_account_hold_override'
  but no such field exists in the codebase. Closest practical match
  was the partner-side Account Hold management tab, which already had
  a group= attribute. Re-gated there; no SO-side field to gate.
- AVL model has no action_disqualify per spec; uses suspend+remove.
  Both gated to QM.
- fp.certificate has no action_sign (only action_issue). FAIR's
  approve/reject covers the FAIR side; nadcap-cert Issue covers the
  cert side via Strategy B.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-24 01:45:39 -04:00

162 lines
7.7 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>
<record id="view_fp_fair_list" model="ir.ui.view">
<field name="name">fp.fair.list</field>
<field name="model">fusion.plating.fair</field>
<field name="arch" type="xml">
<list string="First Article Inspection Reports"
decoration-success="result == 'pass'"
decoration-warning="result == 'conditional'"
decoration-danger="result == 'fail'">
<field name="name"/>
<field name="part_number"/>
<field name="part_revision"/>
<field name="customer_id"/>
<field name="performed_date"/>
<field name="performed_by_id"/>
<field name="result" widget="badge"
decoration-success="result == 'pass'"
decoration-warning="result == 'conditional'"
decoration-danger="result == 'fail'"/>
<field name="state" widget="badge"
decoration-info="state == 'in_review'"
decoration-success="state == 'approved'"
decoration-danger="state == 'rejected'"/>
</list>
</field>
</record>
<record id="view_fp_fair_form" model="ir.ui.view">
<field name="name">fp.fair.form</field>
<field name="model">fusion.plating.fair</field>
<field name="arch" type="xml">
<form string="First Article Inspection Report">
<header>
<!-- Phase D5 — FAIR Approve/Reject = sign-off equivalent;
QM-only per spec section 2.C (FAIR/Nadcap signing is
restricted to Quality Manager regardless of who can
see / create the FAIR record). Submit-for-review and
reset-to-draft stay open to whoever created the FAIR
(Manager+). -->
<button name="action_submit_for_review" string="Submit for Review" type="object"
class="oe_highlight" invisible="state != 'draft'"/>
<button name="action_approve" string="Approve" type="object"
class="oe_highlight" invisible="state != 'in_review'"
groups="fusion_plating.group_fp_quality_manager"/>
<button name="action_reject" string="Reject" type="object"
invisible="state != 'in_review'"
groups="fusion_plating.group_fp_quality_manager"/>
<button name="action_reset_to_draft" string="Reset" type="object"
invisible="state == 'draft'"/>
<field name="state" widget="statusbar"
statusbar_visible="draft,in_review,approved,rejected"/>
</header>
<sheet>
<div class="oe_title">
<label for="name"/>
<h1><field name="name" readonly="1"/></h1>
</div>
<group>
<group>
<field name="part_number"/>
<field name="part_revision"/>
<field name="customer_id"/>
</group>
<group>
<field name="performed_date"/>
<field name="performed_by_id"/>
<field name="result" widget="badge"
decoration-success="result == 'pass'"
decoration-warning="result == 'conditional'"
decoration-danger="result == 'fail'"/>
</group>
</group>
<group string="Processes">
<field name="process_type_ids" widget="many2many_tags" nolabel="1"/>
</group>
<notebook>
<page string="Notes">
<field name="notes"/>
</page>
</notebook>
</sheet>
<chatter/>
</form>
</field>
</record>
<record id="view_fp_fair_kanban" model="ir.ui.view">
<field name="name">fp.fair.kanban</field>
<field name="model">fusion.plating.fair</field>
<field name="arch" type="xml">
<kanban default_group_by="state">
<field name="id"/>
<field name="name"/>
<field name="part_number"/>
<field name="part_revision"/>
<field name="customer_id"/>
<field name="result"/>
<templates>
<t t-name="card">
<div class="o_fp_card o_fp_fair_card"
t-att-data-result="record.result.raw_value">
<strong class="o_fp_card_title"><field name="name"/></strong>
<div class="small mt-1">
<i class="fa fa-cube me-1 text-muted"/>
<field name="part_number"/>
<span class="text-muted ms-1">Rev <field name="part_revision"/></span>
</div>
<div class="small text-muted">
<i class="fa fa-building me-1"/><field name="customer_id"/>
</div>
<div class="mt-2">
<field name="result"/>
</div>
</div>
</t>
</templates>
</kanban>
</field>
</record>
<record id="view_fp_fair_search" model="ir.ui.view">
<field name="name">fp.fair.search</field>
<field name="model">fusion.plating.fair</field>
<field name="arch" type="xml">
<search string="FAIRs">
<field name="name"/>
<field name="part_number"/>
<field name="customer_id"/>
<separator/>
<filter string="Approved" name="approved" domain="[('state','=','approved')]"/>
<filter string="In Review" name="in_review" domain="[('state','=','in_review')]"/>
<filter string="Rejected" name="rejected" domain="[('state','=','rejected')]"/>
<separator/>
<filter string="Pass" name="pass_filter" domain="[('result','=','pass')]"/>
<filter string="Fail" name="fail" domain="[('result','=','fail')]"/>
<separator/>
<filter string="Archived" name="inactive" domain="[('active','=',False)]"/>
<group>
<filter string="Status" name="group_state" context="{'group_by':'state'}"/>
<filter string="Customer" name="group_customer" context="{'group_by':'customer_id'}"/>
<filter string="Result" name="group_result" context="{'group_by':'result'}"/>
</group>
</search>
</field>
</record>
<record id="action_fp_fair" model="ir.actions.act_window">
<field name="name">First Article Inspection Reports</field>
<field name="res_model">fusion.plating.fair</field>
<field name="view_mode">kanban,list,form</field>
<field name="search_view_id" ref="view_fp_fair_search"/>
</record>
</odoo>