Friday, August 18, 2023
11 changes · master
Enhancements to existing features
Knowledge template body content is now shown with proper formatting instead of as plain text. This makes template previews easier to read and helps administrators verify Knowledge templates more accurately.
Original PR description
before this commit, in the knowledge template the body field was added with widget="text". settings -> technical -> knowledge -> templates after this commit, the widget will be removed and content will be displayed properly Before:  After: 
Code cleanup and technical improvements
This update standardizes how text is prepared for translation across many Odoo Enterprise screens. It helps ensure labels and titles in the interface are correctly picked up for translation, improving consistency for users working in different languages.
Original PR description
Miscellaneous changes
The tour `helpdesk_insert_kanban_view_link_in_knowledge` finishes in an editable Knowledge Form view, which is susceptible to cause nondeterministic errors. This fix adds `endKnowledgeTour` to return to the modules menu at the end of the tour. task-3345004 Forward-Port-Of: odoo/enterprise#45862
Original PR description
The tour `helpdesk_insert_kanban_view_link_in_knowledge` finishes in an editable Knowledge Form view, which is susceptible to cause nondeterministic errors. This fix adds `endKnowledgeTour` to return to the modules menu at the end of the tour. task-3345004 Forward-Port-Of: odoo/enterprise#45862
In this commit, all usages of env._t() are replaced by _t(). In templates files, env._t() didn't work because terms used in attributes where not extracted into the translation files. Only string are exported from .xml files to translation files. So, to make it works, we set a variable that is then used in attributes. For example : ``` <t t-set="string_to_translate">String to translate</t> <Dialog title="string_to_translate>...</Dialog> ``` task-3292454 PR Community : https://github.com/odoo/odoo/pull/131390
Forward-Port-Of: odoo/enterprise#45806
Original PR description
Forward-Port-Of: odoo/enterprise#45806
Issue: ====== When you select a workspace for a product that has been created by a project it will throws an error showing that it has a refrence for a False Company. Steps to reproduce the error: ============================= 1-Install sales, documents, project 2-Create a project (named test) 3-Go to sales/products create new product 4-Select type as service, create on order : project & task, project template : test, workspace template : projects/test 5- click save and it will show th
Original PR description
Issue: ====== When you select a workspace for a product that has been created by a project it will throws an error showing that it has a refrence for a False Company. Steps to reproduce the error: ============================= 1-Install sales, documents, project 2-Create a project (named test) 3-Go to sales/products create new product 4-Select type as service, create on order : project & task, project template : test, workspace template : projects/test 5- click save and it will show the error Solution: ========= We should check that product has a company_id. opw-3456166 Forward-Port-Of: odoo/enterprise#45724
PR odoo/enterprise#36728 missed adding a markup in a couple of the chatter messages. Let's not show raw html in them anymore ;) Forward-Port-Of: odoo/enterprise#45678
Original PR description
PR odoo/enterprise#36728 missed adding a markup in a couple of the chatter messages. Let's not show raw html in them anymore ;) Forward-Port-Of: odoo/enterprise#45678
task-3470016 Forward-Port-Of: odoo/enterprise#45885
Original PR description
task-3470016 Forward-Port-Of: odoo/enterprise#45885
Validation payment did not set token properly because the _reconcile_after_done is not called for validation transactions. This PR set token for validation transaction outside of the _reconcile_after_done. Forward-Port-Of: odoo/enterprise#45798
Original PR description
Validation payment did not set token properly because the _reconcile_after_done is not called for validation transactions. This PR set token for validation transaction outside of the _reconcile_after_done. Forward-Port-Of: odoo/enterprise#45798
This test was checking for qtys with UoMs activated, but they are not always activate so the test fails in these cases. Therefore let's make the test always have UoMs deactivated + don't check for them since it only cares about the numerical qtys anyways. Forward-Port-Of: odoo/enterprise#45873
Original PR description
This test was checking for qtys with UoMs activated, but they are not always activate so the test fails in these cases. Therefore let's make the test always have UoMs deactivated + don't check for them since it only cares about the numerical qtys anyways. Forward-Port-Of: odoo/enterprise#45873
a) the prefix /A/ (3 letters + 1 space) is legally mandatory in Belgium (since 2007?) to protect wage payments at the entry level (cfr for example https://www.securex.be/fr/lex4you /employer/topics/remunerate/general-rules/protection-of-income-paid-on-a-current-account) b) the SALA purpose code is apparently standard for all SEPA, and guarantees a series of things in instant payment: https://www.sepaforcorporates.com/sepa-payments/sala-sepa-salary-payments. c) the "High" priority l
Original PR description
a) the prefix /A/ (3 letters + 1 space) is legally mandatory in Belgium (since 2007?) to protect wage payments at the entry level (cfr for example https://www.securex.be/fr/lex4you /employer/topics/remunerate/general-rules/protection-of-income-paid-on-a-current-account) b) the SALA purpose code is apparently standard for all SEPA, and guarantees a series of things in instant payment: https://www.sepaforcorporates.com/sepa-payments/sala-sepa-salary-payments. c) the "High" priority level is also missing, and is also an attribute of the <PmtTpInf> that we should be able to specify as well: <InstrPrty>HIGH</InstrPrty> See https://www.febelfin.be/sites/default/files/2019-04/standard-credit_transfer-xml-v32-en_0.pdf section 2.6 TaskID: 3391690 Forward-Port-Of: odoo/enterprise#45880 Forward-Port-Of: odoo/enterprise#43500
When creating a batch payment, we allow to select sent payments, this leads to an error when saving the batch payment. With this commit we filter the sent payment like we do in account.batch.payment. Steps: - With account_sepa_direct_debit installed - create a customer payment, confirm and mark as sent - Go to batch payment, create one and select the payment - Save -> Validation Error opw-3394798 Forward-Port-Of: odoo/enterprise#45875 Forward-Port-Of: odoo/enterprise#45781
Original PR description
When creating a batch payment, we allow to select sent payments, this leads to an error when saving the batch payment. With this commit we filter the sent payment like we do in account.batch.payment. Steps: - With account_sepa_direct_debit installed - create a customer payment, confirm and mark as sent - Go to batch payment, create one and select the payment - Save -> Validation Error opw-3394798 Forward-Port-Of: odoo/enterprise#45875 Forward-Port-Of: odoo/enterprise#45781