edi_core_oca

Purpose

Provide the core Odoo EDI backend that centralizes configuration, execution, and monitoring of document exchanges between systems.

Features

edi.backend: Centralizes backend-specific settings and orchestrates exchange record creation, generation, validation, sending, receiving, and cron-driven synchronization with robust error handling and retries.
edi.exchange.record: Stores each exchange payload with unique identifiers, binary content, checksum, state machine, acknowledgment tracking, related record links, quick execution hooks, and retry or regenerate actions.
edi.exchange.type: Defines each exchange’s backend type, direction, filename pattern, extension, acknowledgment relationships, handler models, advanced YAML settings, partner restrictions, encoding rules, and quick execution behavior.
edi.backend.type: Classifies backends with normalized unique codes so flows can be grouped and validated by type.
edi.exchange.type.rule: Lets administrators add domain/snippet-driven rules that inject form buttons or custom behaviors per model to trigger manual exchanges.
edi.exchange.consumer.mixin: Gives business documents origin-tracking fields, related-record counters, UI buttons rendered via an OWL widget, access bridging, acknowledgment generation logic, wizard fallbacks, and helper methods to send via EDI or email.
edi.exchange.related.record: Maintains the many-to-many link between exchanges and business records, enforces uniqueness, and posts chatter notifications with contextual templates.
edi.configuration: Provides configurable Python snippets executed before and during triggers, filtering by backend/type/model and exposing time utilities so flows can be automated without code changes.
edi.configuration.trigger: Catalogs reusable trigger definitions with codes, descriptions, and optional model scoping that EDI configurations reference.
edi.exchange.record.create.wiz: Offers a transient wizard to manually create an exchange record for a chosen model, type, and backend, notifying the source document afterwards.
ir.model: Adds boolean flags that mark models capable of generating, validating, sending, receiving, processing, or checking EDI data so exchange types can reference only eligible handlers.
edi.oca.handler.*: Supplies abstract handler models for generate, send, receive, process, check, and validate actions that implementers extend to plug in backend-specific logic.
automation: Schedules hourly server actions that call backend methods to detect pending output/input records, generate missing payloads, send files, receive incoming data, and process inputs.
security: Delivers EDI Manager and Advanced Settings groups plus tailored access rules and multi-company domains guarding backends, exchange records, rules, configurations, and related wizards.
web.assets_backend: Loads an OWL field widget and warning banner template that list rule-driven EDI actions and open manual creation flows directly from business forms.