Friday, February 4, 2022
7 changes
Enhancements to existing features
This update simplifies internal handling for Mexican electronic invoicing, stock delivery documents, and accounting reports. It reduces duplicated logic, aligns naming with broader invoice and payment use cases, and improves maintainability without introducing major user-facing changes.
Original PR description
[IMP] l10n_mx_edi, l10n_mx_edi_stock: cleanup methods Due to stable policy, additional methods were introduced to make them resusable by l10n_mx_edi_stock. In master, we can now clean these methods.…
[IMP] l10n_mx_edi, l10n_mx_edi_stock: cleanup methods Due to stable policy, additional methods were introduced to make them resusable by l10n_mx_edi_stock. In master, we can now clean these methods. [IMP] l10n_mx_edi_stock - Cleanup and simplify in master since the attachment is stored in field `l10n_mx_edi_cfdi_file_id`, a method to search `ir.attachment` is not required [IMP] l10n_mx_reports: reuse existing _certify_and_stamp method in l10n_mx_edi clean the reports module and use existing methods in l10n_mx_edi [IMP] l10n_mx_edi: make the _certify_and_stamp method configurable Different CFDI API's require minor changes to the CFDI attributes for example CartaPorte requires attribute NoCertificado while the reporting XSD requires noCertificado. We add a parameter with default value to accommodate these minor inconsistencies [IMP] l10n_mx_edi,l10n_mx_edi_stock,l10n_mx_reports: make methods private Many methods are publicly exposed and don't need to be. Also fix the manifest dependencies for module 10n_mx_reports since it uses a certificate which is defined in l10n_mx_edi [IMP] l10n_mx_edi: rename field from `l10n_mx_edi_cancel_invoice_id` to `l10n_mx_edi_cancel_move_id` since it is used by invoices and payments Task-2722239
Map views now show boolean group labels as "Yes" or "No" instead of "True" or "False". This makes grouped map results easier for users to understand at a glance.
Original PR description
Purpose ======= When we group the record based on a boolean fields, we want to show "Yes/No" instead of "True/False". This has been done for the map view. Task-2648390
Resolved issues and error corrections
Appointment booking and cancellation emails no longer repeat the attendee name in the subject or content. This makes default and customized appointment emails clearer and more professional for recipients.
Original PR description
Current behavior before PR: Email of booking and canceling the appointment has "Meeting with UserName with Username". Desired behavior after PR is merged: We have removed the repeating word "with Username" in the email template and set the "UserName - Let's meet" in the default value. So, every custom appointment email has proper and equivalent content. This is the goal of this commit. PR #23197 Task-2713963 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
An AFIP code can be used for more than one error, the description of the error needs to be read in order to actually know what to do depending on the case. In this case, the error code 10154 has two messages, we update the HINT information with what to do in each case All translations including * Add new terms * Fix misspelling errors of other terms fw-port of https://github.com/odoo/enterprise/pull/23638 Forward-Port-Of: odoo/enterprise#23967
Original PR description
An AFIP code can be used for more than one error, the description of the error needs to be read in order to actually know what to do depending on the case. In this case, the error code 10154 has two messages, we update the HINT information with what to do in each case All translations including * Add new terms * Fix misspelling errors of other terms fw-port of https://github.com/odoo/enterprise/pull/23638 Forward-Port-Of: odoo/enterprise#23967
This fixes duplicated file entries in several app setup lists so installations and updates use a cleaner, more reliable configuration. The change is internal and helps reduce the risk of redundant processing without changing business features.
Original PR description
COM PR: https://github.com/odoo/odoo/pull/83775
Steps : In Field Service, - Config > Settings > Enable Time and Material - Config > Projects > Disable Timesheets - Create a Task and add a Product - Mark as Done Issue : - Confirmation Error : a required field is not set Model: SOL, Fields:Description Cause : - Because there is no timesheet, the field timesheet_product_id is not set on the Task. - Then, when marked as done, action_fsm_validate calls _fsm_create_sale_order_line to write a new sol for the timesheet but there i
Original PR description
Steps : In Field Service, - Config > Settings > Enable Time and Material - Config > Projects > Disable Timesheets - Create a Task and add a Product - Mark as Done Issue : - Confirmation Error : a required field is not set Model: SOL, Fields:Description Cause : - Because there is no timesheet, the field timesheet_product_id is not set on the Task. - Then, when marked as done, action_fsm_validate calls _fsm_create_sale_order_line to write a new sol for the timesheet but there is no timesheet. - Moreover, sol's description is supposed to be timesheet_product_id of the task, which there isn't either. Fix : - Call _fsm_create_sale_order_line only if timesheets are allowed. Also : - It has been noticed during this fix, that in a fsm project's form, tab Invoice, employee rates tree is useless when timesheets are not allowed. - As it is the only content in this tab, we hide it in this case. opw-2747645 Forward-Port-Of: odoo/enterprise#23834
This pull request prepares the Enterprise edition for the Odoo 15.2 release. It appears to be a release/version update rather than a specific functional change, helping align the product codebase with the new release cycle.