[18.0][MIG] edi_oca #115

Currently translated at 56.5% (78 of 138 strings) Translation: edi-14.0/edi-14.0-edi_oca Translate-URL: https://translation.odoo-community.org/projects/edi-14-0/edi-14-0-edi_oca/fr/

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: edi-14.0/edi-14.0-edi_oca Translate-URL: https://translation.odoo-community.org/projects/edi-14-0/edi-14-0-edi_oca/

use `_notify_*` methods when processing a exchange record. This will allow the use of listeners based on this events.

This action allows to re-schedule the record for the action that failed depending on its current state and direction.

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: edi-14.0/edi-14.0-edi_oca Translate-URL: https://translation.odoo-community.org/projects/edi-14-0/edi-14-0-edi_oca/

Without this check you get 2 overlapping bars till you select an exc type.

Exchange type has no display_name

It might be possible to have the same external_identifier for different backends and types.

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: edi-14.0/edi-14.0-edi_oca Translate-URL: https://translation.odoo-community.org/projects/edi-14-0/edi-14-0-edi_oca/

You can now provide additional env context from type settings.

The filename is redundant there. It's pointless to see it every time in the chatter. If you want to see the details, you go to the exchange record.

Linking via 'oe' attrs seems not to work. Having a real URL also allows to open the record in a new tab.

This makes the state more prominent and clear.

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: edi-14.0/edi-14.0-edi_oca Translate-URL: https://translation.odoo-community.org/projects/edi-14-0/edi-14-0-edi_oca/

By adding the span element, the navigation is not performed correctly and the anchor just redirects to blank '#'. Just remove the span.

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: edi-15.0/edi-15.0-edi_oca Translate-URL: https://translation.odoo-community.org/projects/edi-15-0/edi-15-0-edi_oca/

No more ugly names in the form view till you populate all fields.

* add quick filters * add quick menu items

Name contained redundant information like type name and related record. On for and tree view is totally useless. To still provide information on linked resource name the 'related_name' field has been added.

Prior to this change jobs were tied to the backend. The backend must be responsible for processing records and this is why the logic has been implemented there and it's kept there with this change too. However, it's way better if the job is tied to its record directly because it makes more sense and it helps jumping to the record w/ the 'related' btn on the job.

Makes little sense to show backends first when you enter the EDI menu. Ongoing exchanges are the most important thing.

We want to keep functionality on the same version. It is marked to remove for 16

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: edi-15.0/edi-15.0-edi_oca Translate-URL: https://translation.odoo-community.org/projects/edi-15-0/edi-15-0-edi_oca/

By setting specific timezone and datetime format on exchange type advanced settings, we can easily override the datetime used for generation of exchange record filename.

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: edi-15.0/edi-15.0-edi_oca Translate-URL: https://translation.odoo-community.org/projects/edi-15-0/edi-15-0-edi_oca/

Co-authored-by: etobella

Co-authored-by: Núria Sancho <[email protected]>

Not all components might be bound to an exchange record.

* auto btns on/off flag per exchange type * offer hook to customize how btns are rendered * improve UI

Raise specific error when exchange type is not found.

To be used to track references on exchanged related records.

Handy method to validate core actions of the edi framework.

Kewyord params were not propagated.

Propagate custom kw args to event handlers.

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: edi-15.0/edi-15.0-edi_oca Translate-URL: https://translation.odoo-community.org/projects/edi-15-0/edi-15-0-edi_oca/

You can now track the original exchange record that originated the document in the 1st place.

Ease finding which type the current one is an ack for.

You can produce or receive more than one ack for a given exchange. If that's the case, make sure only the newest is considered.

In case exchange_on is the same, use ID to get the latest on top.

Skip 'output_sent' records by default. Reason: most of the times when a message is sent out you don't care about its state anymore. Any subsequent update from outside should come with a new input record instead. Yet, if for any reason this feature is required you can still enable it by passing 'skip_sent=False'.

In this commit OCA/edi@0a9b6d5 I unified the way these kind of methods were used. Was breaking older implementations where the method was called directly.

As we are reusing the existing window action we must remove default filters otherwise some related exchange records will be hidden by default.

Accept `record_ids` to work w/ specific records.

Allow scheduling jobs immediately based on type configuration. Very often you want an action to be executed right away. You still get a job, meaning that the action is not sync but the job will be scheduled immediately instead of waiting for the cron to run.

Creating the ack was kind of... an hack :) When I added this behavior we didn't have yet the storage machinery that looks automatically for a new file. Also for webservices seems not relevant since we can configure endpoints that can create the ack when needed. All in all, I don't think this feature is needed. Worse, it adds some overhead when a record gets created and can generate write conflicts when exchanges are processed immediately overlapping with the creation of the ack record.

The env_ctx that might come from a exchange type settings was not propagated to the exchange record which is made directly available to the work ctx of the component. Before this change, if you had any method on the exchange record or on the related record relying on a ctx key, the ctx key was not propagated to all records' context.

When sending the file data, we might want to use its bytes version. This new flag gives an option for it.

Now all main framework actions call the same notification method when complete.

Motivation: you end up using sudo on every call because you don't know if the current user will have perm. Yet, we don't care for such operatation.

* filter by default on the last 15 days w/ 'Recent' menu item * filter by default on today on all menu items * allow to browse them all w/ 'All' at the bottom

Before this change, when a related record was deleted you could not access anymore any exchange record (tree or form) due to the permission check. Now: * the check is bypassed * related record buttons are hidden * an informative message is displayed in the form

Long awaited improvement. Allows to decouple rules by model giving much more flexibility. Migration steps included.

You can now customize and translate labels and tooltips for EDI automatic buttons.

Having the same name for different classes prevents selection of specific test cases when running single test suites.

TypeError: not all arguments converted during string formatting

AccessError core messages were modified

Select main only as they can be nested into field custom forms. I'm looking at you on v16 :S

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: edi-framework-16.0/edi-framework-16.0-edi_oca Translate-URL: https://translation.odoo-community.org/projects/edi-framework-16-0/edi-framework-16-0-edi_oca/

…e record

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: edi-framework-16.0/edi-framework-16.0-edi_oca Translate-URL: https://translation.odoo-community.org/projects/edi-framework-16-0/edi-framework-16-0-edi_oca/

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: edi-framework-17.0/edi-framework-17.0-edi_oca Translate-URL: https://translation.odoo-community.org/projects/edi-framework-17-0/edi-framework-17-0-edi_oca/

Currently translated at 100.0% (202 of 202 strings) Translation: edi-framework-17.0/edi-framework-17.0-edi_oca Translate-URL: https://translation.odoo-community.org/projects/edi-framework-17-0/edi-framework-17-0-edi_oca/it/

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: edi-framework-17.0/edi-framework-17.0-edi_oca Translate-URL: https://translation.odoo-community.org/projects/edi-framework-17-0/edi-framework-17-0-edi_oca/

Currently translated at 100.0% (204 of 204 strings) Translation: edi-framework-17.0/edi-framework-17.0-edi_oca Translate-URL: https://translation.odoo-community.org/projects/edi-framework-17-0/edi-framework-17-0-edi_oca/it/

Avoid warning because of duplicated Model field name while installing this module

Archived rules were not visible on the exc type form.

You can now toggle archived/unarchived directly from exc type form

Send jobs might fail due to an external service being not responsive. If the job is simply failed, a new one will be spawned and might encour in the same error again, possibly leading to an high number of duplicated jobs for the same record. Yet, when a RetryableJobError is raised, the job will be set back into pending state and will be nicely retried based on jobs configuration.

When actions are automated, is nice to see that data has been generated for an exchange on the related record.

The recommended way to execute actions on records is to call `action_exchange_*` on

Instead of waiting for the cron to pass again and send the file chain the 2 jobs so that it gets sent right after generation.

* catch OSError * add debug log

Prevents having duplicated jobs for the same record as far as possible.

Try to send out the file as fast as possible once the content is ready.

The origin record should never been copied. Its values should always be set specifically by a framework action.

this field can be used in backend views to show/hide configuration elements depending on the backend type

Currently when we receive an empty file: - Receive step doesn't end up in state error_on_receive : that's because we just ignore the content here - But the process step will raise an error - So this commit goal tries to improve that - By default, this option is disabled so we still consider that an empty file is an error case

…_error records

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[18.0][MIG] edi_oca #115

[18.0][MIG] edi_oca #115

Commits on Oct 24, 2024

Commits on Nov 13, 2024

[18.0][MIG] edi_oca #115

Are you sure you want to change the base?

[18.0][MIG] edi_oca #115

Commits on Oct 24, 2024

Commits on Nov 13, 2024