[16.0][IMP] edi_oca: Split exchange error and traceback

[HviorForgeFlow]

Having the exception error in the tree view can be very effective to identify error on several exchange records.

This PR aims to manage the exception message and the traceback in different fields in order let the user classify by error messages in the tree view and also take a look on the traceback on the form view.

CC @ForgeFlow

[OCA-git-bot]

Hi @etobella, @simahawk,
some modules you are maintaining are being modified, check this out!

[github-actions]

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

[simahawk]

@HviorForgeFlow question: don't you have the traceback on the job?

[HviorForgeFlow]

Yes I believe that it exists there, but there is no link directly.

Error traceback is already in EDI exchange record, the only change in this PR is that as Traceback is usually big and from an user experience prespective someone asked me if I could put just the exception at tree level view to allow them to quick search common errors or understand better without having to enter to the form or look into the linked job.

[simahawk]

Yes I believe that it exists there, but there is no link directly.

We have now a btn to jump to the jobs linked to the record 😉

Error traceback is already in EDI exchange record, the only change in this PR is that as Traceback is usually big and from an user experience prespective someone asked me if I could put just the exception at tree level view to allow them to quick search common errors or understand better without having to enter to the form or look into the linked job.

Exactly because it's big and very technical, I don't think it's a good idea to store it on the record as well.
Also, on jobs you can already search and group for the exception.

[HviorForgeFlow]

But then since 76938cf we are saving the traceback in the exchange records. Should we revert it and just add a optional column in the tree view?

[simahawk]

Ah, good point! Well, I have no strong opinion. For sure, for how things are today is probably better to go ahead w/ this and separate them. Also, having an exchange on error is not normal and will be fixed manually or by an auto operation which means the tb want be stored for too long.

[simahawk]

Can you please backport to 14.0?

[OCA-git-bot]

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖