Syncing from upstream OCA/edi-framework (18-edi_purchase)

README.md

@@ -24,15 +24,17 @@ addon | version | maintainers | summary
 --- | --- | --- | ---
 [edi_account_core_oca](edi_account_core_oca/) | 18.0.1.1.1 | <a href='https://github.com/etobella'><img src='https://github.com/etobella.png' width='32' height='32' style='border-radius:50%;' alt='etobella'/></a> | Define EDI Configuration for Account Moves
 [edi_account_oca](edi_account_oca/) | 18.0.1.1.1 | <a href='https://github.com/etobella'><img src='https://github.com/etobella.png' width='32' height='32' style='border-radius:50%;' alt='etobella'/></a> | Define some component listeners for Account Moves
-[edi_component_oca](edi_component_oca/) | 18.0.1.0.3 | <a href='https://github.com/simahawk'><img src='https://github.com/simahawk.png' width='32' height='32' style='border-radius:50%;' alt='simahawk'/></a> <a href='https://github.com/etobella'><img src='https://github.com/etobella.png' width='32' height='32' style='border-radius:50%;' alt='etobella'/></a> | Allow to use Connector as a source in EDI
-[edi_core_oca](edi_core_oca/) | 18.0.1.6.6 | <a href='https://github.com/simahawk'><img src='https://github.com/simahawk.png' width='32' height='32' style='border-radius:50%;' alt='simahawk'/></a> <a href='https://github.com/etobella'><img src='https://github.com/etobella.png' width='32' height='32' style='border-radius:50%;' alt='etobella'/></a> | Define backends, exchange types, exchange records, basic automation and views for handling EDI exchanges.
+[edi_component_oca](edi_component_oca/) | 18.0.1.1.0 | <a href='https://github.com/simahawk'><img src='https://github.com/simahawk.png' width='32' height='32' style='border-radius:50%;' alt='simahawk'/></a> <a href='https://github.com/etobella'><img src='https://github.com/etobella.png' width='32' height='32' style='border-radius:50%;' alt='etobella'/></a> | Allow to use Connector as a source in EDI
+[edi_core_oca](edi_core_oca/) | 18.0.1.7.0 | <a href='https://github.com/simahawk'><img src='https://github.com/simahawk.png' width='32' height='32' style='border-radius:50%;' alt='simahawk'/></a> <a href='https://github.com/etobella'><img src='https://github.com/etobella.png' width='32' height='32' style='border-radius:50%;' alt='etobella'/></a> | Define backends, exchange types, exchange records, basic automation and views for handling EDI exchanges.
 [edi_endpoint_oca](edi_endpoint_oca/) | 18.0.1.0.3 |  | Base module allowing configuration of custom endpoints for EDI framework.
 [edi_exchange_template_oca](edi_exchange_template_oca/) | 18.0.1.3.3 | <a href='https://github.com/simahawk'><img src='https://github.com/simahawk.png' width='32' height='32' style='border-radius:50%;' alt='simahawk'/></a> | Allows definition of exchanges via templates.
 [edi_exchange_template_party_data](edi_exchange_template_party_data/) | 18.0.1.0.1 | <a href='https://github.com/simahawk'><img src='https://github.com/simahawk.png' width='32' height='32' style='border-radius:50%;' alt='simahawk'/></a> | Glue module between edi_exchange_template and edi_party_data
+[edi_notification_oca](edi_notification_oca/) | 18.0.1.0.0 |  | Define notification activities on exchange records.
 [edi_oca](edi_oca/) | 18.0.1.5.2 | <a href='https://github.com/simahawk'><img src='https://github.com/simahawk.png' width='32' height='32' style='border-radius:50%;' alt='simahawk'/></a> <a href='https://github.com/etobella'><img src='https://github.com/etobella.png' width='32' height='32' style='border-radius:50%;' alt='etobella'/></a> | Integrate all EDI modules together
 [edi_party_data_oca](edi_party_data_oca/) | 18.0.1.0.1 | <a href='https://github.com/simahawk'><img src='https://github.com/simahawk.png' width='32' height='32' style='border-radius:50%;' alt='simahawk'/></a> | Allow to configure and retrieve party information for EDI exchanges.
+[edi_product_oca](edi_product_oca/) | 18.0.1.0.0 |  | EDI framework configuration and base logic for products and products packaging
 [edi_queue_oca](edi_queue_oca/) | 18.0.1.0.2 |  | Set Queue Jobs on EDI
-[edi_record_metadata_oca](edi_record_metadata_oca/) | 18.0.1.0.4 | <a href='https://github.com/simahawk'><img src='https://github.com/simahawk.png' width='32' height='32' style='border-radius:50%;' alt='simahawk'/></a> | Allow to store metadata for related records.
+[edi_record_metadata_oca](edi_record_metadata_oca/) | 18.0.1.0.5 | <a href='https://github.com/simahawk'><img src='https://github.com/simahawk.png' width='32' height='32' style='border-radius:50%;' alt='simahawk'/></a> | Allow to store metadata for related records.
 [edi_sale_endpoint](edi_sale_endpoint/) | 18.0.1.0.0 | <a href='https://github.com/simahawk'><img src='https://github.com/simahawk.png' width='32' height='32' style='border-radius:50%;' alt='simahawk'/></a> | Glue module between edi_sale_oca and edi_endpoint_oca.
 [edi_sale_input_oca](edi_sale_input_oca/) | 18.0.1.0.2 | <a href='https://github.com/simahawk'><img src='https://github.com/simahawk.png' width='32' height='32' style='border-radius:50%;' alt='simahawk'/></a> | Process incoming sale orders with the EDI framework.
 [edi_sale_oca](edi_sale_oca/) | 18.0.1.0.1 | <a href='https://github.com/simahawk'><img src='https://github.com/simahawk.png' width='32' height='32' style='border-radius:50%;' alt='simahawk'/></a> | Configuration and special behaviors for EDI on sales.

edi_component_oca/README.rst

@@ -11,7 +11,7 @@ Edi Connector Oca
    !! This file is generated by oca-gen-addon-readme !!
    !! changes will be overwritten.                   !!
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-   !! source digest: sha256:81c11c0d670f363513d25e5d2d6cb038f1fc56580f20c837c2d2a7665798018d
+   !! source digest: sha256:6c5e69ae42fdaaaf428ee2b9d0a8e14ba1b5515b6fd5daa7ca926cb5800567b4
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 
 .. |badge1| image:: https://img.shields.io/badge/maturity-Beta-yellow.png

edi_component_oca/__manifest__.py

@@ -4,7 +4,7 @@
 {
     "name": "Edi Connector Oca",
     "summary": """Allow to use Connector as a source in EDI""",
-    "version": "18.0.1.0.3",
+    "version": "18.0.1.1.0",
     "license": "LGPL-3",
     "author": "ACSONE,Dixmit,Camptocamp,Odoo Community Association (OCA)",
     "maintainers": ["simahawk", "etobella"],

edi_component_oca/models/edi_exchange_record.py

@@ -8,15 +8,9 @@
 class EdiExchangeRecord(models.Model):
     _inherit = "edi.exchange.record"
 
-    def _trigger_edi_event_make_name(self, name, suffix=None):
-        return "on_edi_exchange_{name}{suffix}".format(
-            name=name,
-            suffix=("_" + suffix) if suffix else "",
-        )
-
     def _trigger_edi_event(self, name, suffix=None, target=None, **kw):
         """Trigger a component event linked to this backend and edi exchange."""
-        name = self._trigger_edi_event_make_name(name, suffix=suffix)
+        event_name = self._trigger_edi_event_make_name(name, suffix=suffix)
         target = target or self
-        target._event(name).notify(self, **kw)
+        target._event(event_name).notify(self, **kw)
         return super()._trigger_edi_event(name, suffix=suffix, target=target, **kw)

edi_component_oca/static/description/index.html

@@ -372,7 +372,7 @@ <h1>Edi Connector Oca</h1>
 !! This file is generated by oca-gen-addon-readme !!
 !! changes will be overwritten.                   !!
 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-!! source digest: sha256:81c11c0d670f363513d25e5d2d6cb038f1fc56580f20c837c2d2a7665798018d
+!! source digest: sha256:6c5e69ae42fdaaaf428ee2b9d0a8e14ba1b5515b6fd5daa7ca926cb5800567b4
 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
 <p><a class="reference external image-reference" href="https://odoo-community.org/page/development-status"><img alt="Beta" src="https://img.shields.io/badge/maturity-Beta-yellow.png" /></a> <a class="reference external image-reference" href="http://www.gnu.org/licenses/lgpl-3.0-standalone.html"><img alt="License: LGPL-3" src="https://img.shields.io/badge/license-LGPL--3-blue.png" /></a> <a class="reference external image-reference" href="https://github.com/OCA/edi-framework/tree/18.0/edi_component_oca"><img alt="OCA/edi-framework" src="https://img.shields.io/badge/github-OCA%2Fedi--framework-lightgray.png?logo=github" /></a> <a class="reference external image-reference" href="https://translation.odoo-community.org/projects/edi-framework-18-0/edi-framework-18-0-edi_component_oca"><img alt="Translate me on Weblate" src="https://img.shields.io/badge/weblate-Translate%20me-F47D42.png" /></a> <a class="reference external image-reference" href="https://runboat.odoo-community.org/builds?repo=OCA/edi-framework&amp;target_branch=18.0"><img alt="Try me on Runboat" src="https://img.shields.io/badge/runboat-Try%20me-875A7B.png" /></a></p>
 <p>This module allows to use components to handle code to execute on EDI

edi_core_oca/README.rst

@@ -11,7 +11,7 @@ EDI
    !! This file is generated by oca-gen-addon-readme !!
    !! changes will be overwritten.                   !!
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-   !! source digest: sha256:c609033733302fa71a3c01c11e2729fd2b47ccde0b9a1d0619bed03cc26db4fe
+   !! source digest: sha256:27258fb23153f2660be19d7c76b04c4d09d35d1e240b779076c7f4a9fa66d9f2
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 
 .. |badge1| image:: https://img.shields.io/badge/maturity-Beta-yellow.png
@@ -42,7 +42,15 @@ Provides following models:
 3. EDI Exchange Type, to define file types of exchange
 4. EDI Exchange Record, to define a record exchanged between systems
 
-Also define a mixin to be inherited by records that will generate EDIs
+Also define a mixin to be inherited by records that will generate EDIs.
+
+In addition, the module ships an ``edi.configuration`` mechanism that
+lets users react to EDI events declaratively, by writing small Python
+snippets attached to event triggers. This can be used as a lightweight
+alternative to component event listeners: configurations can react
+globally (on any exchange) or be scoped to a specific partner (or any
+related record), exchange type, backend and target model. See
+``CONFIGURE.md`` for details.
 
 **Table of contents**
 
@@ -130,6 +138,104 @@ backend to be used for the exchange.
 In case of "Custom" kind, you'll have to define your own logic to do
 something.
 
+Custom event handlers via ``edi.configuration``
+-----------------------------------------------
+
+The framework can dispatch EDI lifecycle events to user-defined
+configurations, providing a declarative alternative to component events.
+Each ``edi.configuration`` record links a **trigger** (an
+``edi.configuration.trigger`` code) to a **snippet** (``snippet_do``)
+that is executed every time the matching event fires on an exchange
+record.
+
+Built-in events fired by ``EDIExchangeRecord`` include:
+
+- ``on_edi_exchange_done`` — exchange processed successfully
+- ``on_edi_exchange_error`` — exchange ended in error
+- ``on_edi_exchange_done_ack_received`` — ACK file received
+- ``on_edi_exchange_done_ack_missing`` — expected ACK not received
+- ``on_edi_exchange_done_ack_received_error`` — ACK received with errors
+- ``on_edi_exchange_<action>_complete`` — generic action completion
+  (e.g. ``generate_complete``, ``send_complete``), fired once on the
+  exchange record and once on its related record when present
+
+The snippet receives at least two variables in its evaluation context:
+
+- ``conf`` — the current ``edi.configuration`` record
+- ``record`` — the target of the event (either the
+  ``edi.exchange.record`` itself or its related business record)
+
+Plus the standard ``edi_exec_snippet_do`` extras (``operation``,
+``edi_action``, ``old_value``, ``vals``, ...).
+
+Two complementary lookup modes are available, and they can be combined
+freely on the same flow.
+
+Global event configurations
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Use this mode when you want a configuration to react to events on **any
+business record** that travels through EDI, with no per-partner setup.
+
+Tick **Global Configuration** (``is_global``) on the
+``edi.configuration``. When an event fires, the framework calls
+``edi.configuration.edi_get_conf_global(exchange_record, trigger)``
+which selects all active global configurations whose ``trigger`` matches
+the event code, filtered by the originating exchange record:
+
+- **Exchange type** (``type_id``): must match the exchange record's
+  type, or be left empty to apply to every type
+- **Backend** (``backend_id``): must match the exchange record's
+  backend, or be left empty to apply to every backend
+- **Model** (``model_id`` / ``model_name``): must match the related
+  record model (e.g. ``sale.order``, ``account.move``), or be left empty
+  to apply to every model
+
+Empty values mean "applies to all". Inactive configurations and
+non-global configurations are ignored. All matching configurations are
+executed in sequence.
+
+Typical use cases:
+
+- Posting a generic chatter message on every exchange that ends in error
+- Pushing a notification to an external system every time an ACK is
+  received for a given backend
+- Logging extra audit information for every exchange of a given type
+
+Partner-specific (relation-based) event configurations
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Use this mode when the reaction must depend on the partner (or any other
+related record) involved in the exchange.
+
+In this case configurations are **not** marked as global. Instead, the
+business record exposes an ``edi_config_ids`` relation (via
+``edi.exchange.consumer.mixin._edi_config_field_relation``, which by
+default returns ``self.env["edi.configuration"]`` and can be overridden,
+for example to point at ``self.partner_id.edi_config_ids``). When an
+event fires on the business record (e.g. on create, on write, on
+send-via-email/EDI), the framework calls
+``edi_confs.edi_get_conf(trigger)`` on that relation and runs the
+matching snippets.
+
+Compared with global configurations:
+
+- **Discovery** comes from the record's own relation, not from a
+  database-wide search; this is the right place to model "this partner
+  wants this behaviour" rules
+- **Filtering** is reduced to ``trigger`` and (optionally)
+  ``backend_id``, since the recordset is already narrowed by the
+  relation
+- The same ``snippet_do`` API applies, so a snippet can be reused
+  verbatim between global and partner-specific configurations
+
+Typical use cases:
+
+- Sending a specific EDI flow only for a subset of partners
+- Customising the document generation per customer (e.g. different email
+  template, different transport)
+- Switching between EDI and email delivery based on partner preferences
+
 Usage
 =====
 
@@ -182,6 +288,39 @@ Components dependancy has been removed and set on a new dependant module
 ``edi_component_oca``. Module ``edi_oca`` has been_renamed to
 ``edi_core_oca``.
 
+Changelog
+=========
+
+18.0.1.7.0 (2026-05-20)
+-----------------------
+
+Features
+~~~~~~~~
+
+- Introduce a new system for **global EDI events** based on
+  ``edi.configuration`` that can replace the use of component events.
+
+  Any ``edi.configuration`` flagged as ``is_global`` is now picked up by
+  ``EDIExchangeRecord._trigger_edi_event`` and its ``snippet_do`` is
+  executed whenever the matching event fires (``done``, ``error``,
+  ``ack_received``, ``ack_missing``, ``ack_received_error``,
+  ``<action>_complete``, ...).
+
+  Filtering is performed via the new
+  ``edi.configuration.edi_get_conf_global`` model method, which selects
+  active global configurations matching the event trigger code and, when
+  set, the exchange type, the backend and the related record model
+  carried by the exchange record (empty values still mean "applies to
+  all"). This lets integrators subscribe to EDI events declaratively
+  from the UI instead of writing component listeners.
+
+  Full test coverage is included for the dispatch on all ``notify_*``
+  events (both on the exchange record and on the related record target)
+  and for the new filtering rules.
+
+  Last but not lease: add minimal docs for edi.configuration.
+  (`#global-edi-conf-events <https://github.com/OCA/edi-framework/issues/global-edi-conf-events>`__)
+
 Bug Tracker
 ===========
 

edi_core_oca/__manifest__.py

@@ -9,7 +9,7 @@
     Define backends, exchange types, exchange records,
     basic automation and views for handling EDI exchanges.
     """,
-    "version": "18.0.1.6.6",
+    "version": "18.0.1.7.0",
     "website": "https://github.com/OCA/edi-framework",
     "development_status": "Beta",
     "license": "LGPL-3",

edi_core_oca/data/edi_configuration.xml

@@ -15,6 +15,18 @@
         <field name="code">on_record_write</field>
         <field name="description">Trigger when a record is updated</field>
     </record>
+
+    <record id="edi_config_trigger_record_done" model="edi.configuration.trigger">
+        <field name="name">On record exchange done</field>
+        <field name="code">on_edi_exchange_done</field>
+        <field name="description">Trigger when a record exchange is done</field>
+    </record>
+    <record id="edi_config_trigger_record_error" model="edi.configuration.trigger">
+        <field name="name">On record exchange error</field>
+        <field name="code">on_edi_exchange_error</field>
+        <field name="description">Trigger when a record exchange has an error</field>
+    </record>
+
     <!-- TODO: these 2 have to be triggered somehow -->
     <record id="edi_conf_trigger_send_via_email" model="edi.configuration.trigger">
         <field name="name">Send via email</field>

edi_core_oca/i18n/edi_core_oca.pot

@@ -1005,6 +1005,11 @@ msgstr ""
 msgid "Generator"
 msgstr ""
 
+#. module: edi_core_oca
+#: model:ir.model.fields,field_description:edi_core_oca.field_edi_configuration__is_global
+msgid "Global Configuration"
+msgstr ""
+
 #. module: edi_core_oca
 #: model_terms:ir.ui.view,arch_db:edi_core_oca.edi_exchange_record_view_search
 #: model_terms:ir.ui.view,arch_db:edi_core_oca.edi_exchange_type_rule_view_search
@@ -1069,6 +1074,13 @@ msgstr ""
 msgid "If checked, some messages have a delivery error."
 msgstr ""
 
+#. module: edi_core_oca
+#: model:ir.model.fields,help:edi_core_oca.field_edi_configuration__is_global
+msgid ""
+"If checked, this configuration will be executed for all records, regardless "
+"of the partner relation."
+msgstr ""
+
 #. module: edi_core_oca
 #: model:ir.model.fields,help:edi_core_oca.field_edi_exchange_type__exchange_filename_sequence_id
 msgid ""

edi_core_oca/i18n/es.po

@@ -1014,6 +1014,11 @@ msgstr ""
 msgid "Generator"
 msgstr ""
 
+#. module: edi_core_oca
+#: model:ir.model.fields,field_description:edi_core_oca.field_edi_configuration__is_global
+msgid "Global Configuration"
+msgstr ""
+
 #. module: edi_core_oca
 #: model_terms:ir.ui.view,arch_db:edi_core_oca.edi_exchange_record_view_search
 #: model_terms:ir.ui.view,arch_db:edi_core_oca.edi_exchange_type_rule_view_search
@@ -1078,6 +1083,13 @@ msgstr ""
 msgid "If checked, some messages have a delivery error."
 msgstr ""
 
+#. module: edi_core_oca
+#: model:ir.model.fields,help:edi_core_oca.field_edi_configuration__is_global
+msgid ""
+"If checked, this configuration will be executed for all records, regardless "
+"of the partner relation."
+msgstr ""
+
 #. module: edi_core_oca
 #: model:ir.model.fields,help:edi_core_oca.field_edi_exchange_type__exchange_filename_sequence_id
 msgid ""

edi_core_oca/i18n/fr.po

@@ -1026,6 +1026,11 @@ msgstr ""
 msgid "Generator"
 msgstr "Générer"
 
+#. module: edi_core_oca
+#: model:ir.model.fields,field_description:edi_core_oca.field_edi_configuration__is_global
+msgid "Global Configuration"
+msgstr ""
+
 #. module: edi_core_oca
 #: model_terms:ir.ui.view,arch_db:edi_core_oca.edi_exchange_record_view_search
 #: model_terms:ir.ui.view,arch_db:edi_core_oca.edi_exchange_type_rule_view_search
@@ -1092,6 +1097,13 @@ msgstr ""
 msgid "If checked, some messages have a delivery error."
 msgstr ""
 
+#. module: edi_core_oca
+#: model:ir.model.fields,help:edi_core_oca.field_edi_configuration__is_global
+msgid ""
+"If checked, this configuration will be executed for all records, regardless "
+"of the partner relation."
+msgstr ""
+
 #. module: edi_core_oca
 #: model:ir.model.fields,help:edi_core_oca.field_edi_exchange_type__exchange_filename_sequence_id
 msgid ""