chore(menu): promote Specifications + clarify misleading menu names
Specifications menu (urgent — workflow blocker for estimators): - Moved from Configuration → Quality & Documents (manager-only) up to Plating → Quality (sequence 70). Now visible to estimator, supervisor, and manager. - Renamed "Customer Specs" → "Specifications" — the seeded library includes industry standards (AMS, MIL, ASTM, BAC) not just customer-private specs. - Action display name updated: "Customer Specifications" → "Specifications". - Added action.help HTML so the empty-state placeholder explains the Specifications library purpose to first-time users. - Old xmlid (menu_fp_config_customer_spec) preserved so existing links / breadcrumbs / search references continue to resolve. Other clarifying renames: - Safety: "JHSC" / "JHSC Meetings" → "H&S Committee (JHSC)" / "H&S Committee Meetings" — acronym was opaque to non-Canadian H&S folks. - Operations: "Move Log" → "Parts & Rack Move Log" — generic name could be confused with chatter messages or stock moves. - Configuration → Recipes & Steps: "Workflow States" → "Job Workflow Stages" — generic name; clarifies these are job state milestones (passed-stage tracking), not generic workflow. - Compliance → General: child folder "Configuration" → "Reference Data" — three levels of "Configuration" nesting (Plating>Config vs Plating>Compliance>General>Config) was confusing. No model / data changes. Pure menu metadata. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -3,7 +3,7 @@
|
||||
# License OPL-1 (Odoo Proprietary License v1.0)
|
||||
{
|
||||
'name': 'Fusion Plating - Compliance (Framework)',
|
||||
'version': '19.0.1.2.0',
|
||||
'version': '19.0.1.3.0',
|
||||
'category': 'Manufacturing/Plating',
|
||||
'summary': 'Jurisdiction-agnostic compliance framework: permits, discharge monitoring, waste manifests, pollutant inventory, compliance calendar, spill register.',
|
||||
'description': 'Generic compliance framework. Region packs load jurisdiction-specific data.',
|
||||
|
||||
@@ -11,7 +11,7 @@
|
||||
<menuitem id="menu_fp_compliance_calendar" name="Compliance Calendar" parent="menu_fp_compliance_root" action="action_fp_compliance_event" sequence="40"/>
|
||||
<menuitem id="menu_fp_compliance_spill_register" name="Spill Register" parent="menu_fp_compliance_root" action="action_fp_spill_register" sequence="50"/>
|
||||
|
||||
<menuitem id="menu_fp_compliance_config" name="Configuration" parent="menu_fp_compliance_root" sequence="100"/>
|
||||
<menuitem id="menu_fp_compliance_config" name="Reference Data" parent="menu_fp_compliance_root" sequence="100"/>
|
||||
<menuitem id="menu_fp_compliance_jurisdiction" name="Jurisdictions" parent="menu_fp_compliance_config" action="action_fp_jurisdiction" sequence="10"/>
|
||||
<menuitem id="menu_fp_compliance_regulator" name="Regulators" parent="menu_fp_compliance_config" action="action_fp_regulator" sequence="20"/>
|
||||
<menuitem id="menu_fp_compliance_discharge_limit" name="Discharge Limits" parent="menu_fp_compliance_config" action="action_fp_discharge_limit" sequence="30"/>
|
||||
|
||||
Reference in New Issue
Block a user