OdooWiki OCA HUB

EDI Storage integration with Queue

edi_storage_queue_oca folder_open OCA/edi-framework open_in_new
Uncategorised License: LGPL-3

Integrates EDI Storage with Queue Job.

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

This module makes the creation of missing EDI storage records run as a background job instead of blocking the user. It adds a dedicated job channel and job function so these operations are processed asynchronously.

When Odoo needs to create a missing record in EDI storage, this module changes that step so it is handled by the queue job system instead of being done immediately during the user's action. The method _storage_create_record_if_missing on the edi.backend model is patched so that it is automatically delayed and executed as a background job.

  • A new job channel named edi_storage is created, placed under the existing EDI root channel.
  • A job function is registered for the edi.backend model and the _storage_create_record_if_missing method, linked to that new channel.

Because of this, users do not have to wait for storage record creation to finish; the work is queued and processed by the job runner. This module does not add menus, screens, buttons, reports, or business rules of its own. It only affects the edi.backend model and relies on the EDI storage and EDI queue modules. The change is technical and automatic, with no visible configuration required from the user.

Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 1 confirmed, 8 with no information of 9 versions.

Sources · Odoo 18.0

Confirmed on 2026-11-03 in branch 18.0 of OCA/edi-framework.

terminal Installation and usage

No verified information

Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.

info

Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.