- Add @api.model_create_multi hook to MaintenanceEquipment.create()
- Add load() override to handle Excel/CSV import correctly
- Add _create_missing_ows_machines() helper with recursion prevention
- Modify OwsMachine.create() to only create equipment if equipment_id not provided
- Use context flag 'skip_ows_machine_creation' to prevent infinite recursion
- Fixes: Equipment import now auto-creates ows.machine and displays OWS tab
- Migration tested: Compatible with SQL-based post-migration (23/23 machines migrated)
- Check if status 'In Betrieb' exists before setting it
- Add warning if status not found instead of SQL error
- Status records are created automatically via XML data file
- open_workshop_base: Create 4 status records (In Betrieb, Defekt, Wartung, Ausgemustert) via XML data
- open_workshop_dokuwiki: Add smiley field to status model and populate with DokuWiki smileys/emojis
- Use noupdate=1 to prevent overwriting user customizations
- Status data loads automatically during module installation
Fixed DeprecationWarning by updating OwsMachine.create() method:
- Changed from @api.model with single vals parameter
- To @api.model_create_multi with vals_list parameter
- Now supports batch creation of multiple records
- Removed duplicate empty OwsMachineArea class definition
This resolves the Odoo 18 deprecation warning about create method not supporting batch operations.
Added documentation to clarify:
- Why store=True is used for related fields (performance for filtering/searching)
- Why manual synchronization is needed in migration (related fields don't auto-sync during SQL INSERT)
No functional changes, only improved code documentation.
The related fields in maintenance.equipment with store=True were not automatically
synchronized during migration. Added explicit SQL UPDATE statements to copy values:
- ows_area_id from area_id
- ows_category from category
This ensures the maintenance.equipment records have all the OWS-specific data
from the original ows.machine records after migration.
- Extended maintenance.equipment model with Related fields to ows.machine
- ows_machine_id: One2many inverse relation
- ows_category: Related to machine category (editable, stored)
- ows_area_id: Related to machine area (editable, stored)
- ows_product_ids: Related One2many for usage products
- ows_training_ids: Related One2many for training products
- Equipment Form View Extensions:
- Added ows_area_id and ows_category after location field
- New 'Offene Werkstatt (Hobbyhimmel)' notebook page with:
- Security section (category icon, category, area)
- Usage products section (Nutzungsprodukte)
- Training products section (Einweisungsprodukte)
- Page visibility controlled by ows_machine_id existence
- Equipment List/Search View Extensions:
- Added ows_category_icon and ows_area_id columns
- Added OWS search fields (area, category)
- Added category filters (green/yellow/red)
- Added OWS grouping options (by area, by category)
- Menu Structure Migration:
- Removed standalone 'Ausrüstung' top-level menu
- Integrated all OWS config into Maintenance → Configuration:
- Bereiche (Areas)
- Zuordnungen (Assignments) container
- Nutzungsprodukte (Usage Products)
- Einweisungsprodukte (Training Products)
- Created simplified tree views for Equipment context:
- view_ows_machine_product_tree_simple (no machine_id column)
- view_ows_machine_training_tree_simple (no machine_id column)
- Freed location field from automatic area synchronization:
- Removed area → location mapping in create()/write()
- location now available for detailed physical location info
- ows_area_id provides workspace area assignment
BREAKING CHANGE: Standalone OWS menu removed, all features now in Maintenance app
UX IMPROVEMENT: Single Equipment view shows all data, no split views needed
- Add default company_id to equipment records during migration
- Fixes 'Generate Serial Number' button not working for migrated equipment
- Equipment without company_id could not generate serial numbers
- Made location field readonly in maintenance.equipment view
- Hide equipment_id field in machine form (auto-created)
- Name and serial_no now directly editable in machine form
- Area is now required field
- Location automatically synced from area to equipment
- Equipment auto-created on machine save with all fields
- Renamed menu from 'Maschinen' to 'Ausrüstung'
- Improved user flow: No need to switch between views
Changes:
- Added maintenance_equipment_views.xml for readonly location
- Updated create() to always auto-create equipment
- Enhanced write() to sync name/serial_no changes to equipment
- Menu labels updated to 'Ausrüstung'
- Neues Modul open_workshop_pos erstellt
- POS JavaScript, XML Templates und CSS verschoben
- open_workshop_base bereinigt: keine POS-Abhängigkeit mehr
- open_workshop_base Version 18.0.1.0.4
- open_workshop_pos Version 18.0.1.0.0
- Kategorie von 'Point of Sale' zu 'Manufacturing' geändert
- Alle Template-Referenzen aktualisiert (open_workshop_base → open_workshop_pos)
Module getestet und erfolgreich installiert in hh18 Datenbank.
- Modul umbenannt von open_workshop zu open_workshop_base
- Alle Referenzen im Code aktualisiert (Templates, Views, Assets)
- SQL-Migrationsskript für automatische DB-Migration erstellt
- post_init_hook hinzugefügt
- Version auf 18.0.1.0.3 erhöht
- Vorbereitung für modulare Architektur (Base, POS, API)
Fixes für Gitea Action Integration:
- SQL-Skript in open_workshop_base/migrations/
- Alter open_workshop/ Ordner entfernt
- Migrations-Workflow getestet auf hh18
