edi_oca: exchange dependency about edi HOT 3 OPEN

as today before generating payload I'm calling a method such

    def _wait_related_exchange_to_be_sent_and_processed(self):
        if not all(
            self.exchange_record.dependent_exchange_ids.mapped(
                lambda rel_exch: rel_exch.edi_exchange_state
                == "output_sent_and_processed"
            )
        ):
            raise RetryableJobError(
                "Waiting related exchanges to be done before generate...",
            )

from edi.

Hi @petrus-v ,

Regarding job dependencies between actions (eg: generate/send) I've recently drafted this #796

As for dependencies between exchanges, we could have a method that accepts a list of records and chains its jobs.
By default this could come from a field as you mentioned. The issue is: the fact that a job is done does not represent the fact that exchange is done. And what if you set the job as done manually? This will likely trigger the next job in the chain.
Hence, I think you cannot avoid checking the state of the former record in the chain in any case.

As of today, I think it's better to leverage events. You can already use them now.
When a record is successfully transitioned to another state you generate the next one. Easy and clear.

Another approach that I drafted is to automate exchange generation based on some rules.
It depends on #797 and OCA/edi-framework#4.
In my case, for instance, I'm able to generate an order response as an ack to the original exchange record that created a SO when the order gets confirmed.
In your case, you can handle what happens on the invoice and on its related record.

Another point is - and this is something I wanted to do since a long time - we should reflect the state of last related job on the exchange record.

from edi.