[18.0][IMP] edi_core_oca: add backend-controlled auto-cleanup for exchange records#233
Open
Ricardoalso wants to merge 1 commit intoOCA:18.0from
Open
[18.0][IMP] edi_core_oca: add backend-controlled auto-cleanup for exchange records#233Ricardoalso wants to merge 1 commit intoOCA:18.0from
Ricardoalso wants to merge 1 commit intoOCA:18.0from
Conversation
Contributor
Ricardoalso
force-pushed
the
edi_exchange_record_cleaning
branch
from
ca3e2f9 to
90cc5e6
Compare
etobella
requested changes
Feb 13, 2026
Member
etobella
left a comment
etobella
left a comment
There was a problem hiding this comment.
If we want to do that, we need to at least add a way to decide which records can be archived. IMO, we should add a flag on exchange type or backends for that.
Ricardoalso
changed the title
Ricardoalso
force-pushed
the
edi_exchange_record_cleaning
branch
from
e551b22 to
9d3fe03
Compare
Contributor
Author
Hey @etobella, thanks for the early review, you were too fast for me! 😄 Following @simahawk’s suggestion, I added the configuration to the edi.backend model and kept them disabled by default. |
Ricardoalso
changed the title
Ricardoalso
changed the title
Contributor
You can still edit the cron to search for records by specific type. |
simahawk
approved these changes
Feb 26, 2026
…records Add configurable auto-archiving and auto-deletion of EDI exchange records per backend. This backend-specific settings that can be managed individually. Changes: - Add "Auto Cleanup" tab in backend form view for easy configuration - Add archive cron job that respect backend-specific retention policies - Add delete cron job that respect backend-specific retention policies - Add "Archived" filter to exchange record search view Benefits: - Each backend can have different retention policies - Setting fields to 0 (default value) disables the respective cleanup behavior - More flexible data retention management - Better control over storage and performance optimization The cron jobs iterate through backends with configured retention settings, applying appropriate cutoff values. chore(edi_core_oca): update documentation
Ricardoalso
force-pushed
the
edi_exchange_record_cleaning
branch
from
b96888d to
3183ca6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces automated maintenance for EDI exchange records. The most significant changes are the addition of scheduled jobs to archive and delete old EDI records and the introduction of an
activeflag for EDI records.Changes:
Benefits:
The cron jobs iterate through backends with configured retention
settings, applying appropriate cutoff values.