Saturday, December 21, 2024
6 changes · master
Enhancements to existing features
WhatsApp integrations can now record detailed request and response information when debug logging is enabled. This helps administrators troubleshoot message delivery and integration issues more easily while limiting control of the setting to authorized access-rights users.
Original PR description
PURPOSE Implement detailed logging of WhatsApp requests and response data, for enhanced debugging and traceability. SPECIFICATION In debug logs, for requests, the log captures the WhatsApp account name (to identify the source of the log), request type, call URL, and data payload. It logs the account name, call URL, response status code, and response body text for responses. TECHNICAL The WhatsApp account's `debug_logging` boolean field controls logging. When enabled, logs are created. Access to manage `debug_logging` is restricted to users in the `Administration / AccessRights` group, ensuring alignment with `ir.logging` access permissions. Task-4004969
The Knowledge app has a cleaner, more user-friendly look across the sidebar, top bar, article views, and website Knowledge pages. The Search menu is now called Articles, making navigation clearer for users, and related guided tours were updated to match the new experience.
Original PR description
This commit improves the look of the app based on feedback we received/saw online. Specifications ============== 1. UI & UX changes of sidebar, topbar, view. 2. The 'Search' menu is renamed to 'Articles'. 3. website_knowledge is also adapted to appropriate changes. 4. The tour has been adapted to above changes. Task-4246990
Australian payroll opening balances can now include the relevant income stream type during setup or import. This helps ensure year-to-date payroll values are reported correctly when employees had income stream changes before moving to Odoo.
Original PR description
All year to date values are expected to be reported per income stream type. That requires all the opening balance to be imported with an income stream type if it has changed prior to transferring to Odoo. This commit adds the income stream type field to the opening balances and the import flow.
Helpdesk and project views now show a meaningful label when grouped information is missing, instead of displaying a generic empty or false value. This makes map, Gantt, graph, pivot, list, and kanban reporting easier to read while removing some custom view code.
Original PR description
*helpdesk, project_enterprise This commit is the counterpart of https://github.com/odoo/odoo/pull/190719 which adds an attribute on field allowing to specify, on a field definition, the value to display when that field is not set. We use that attribute in the map and gantt views to display its value as group name, for the false group. Moreover, we define it in helpdesk on two fields, which allows to get rid of several custom views (js_class). Task~4410227
Resolved issues and error corrections
Splitting a manufacturing order now keeps the related work order statuses accurate on the backorder. This helps production teams avoid confusion and rely on correct progress information after a split.
Original PR description
Before this Commit: ---------------------------- Whenever a manufacturing order (MO) with work orders is split, the work order states in the backorder MO are incorrect. Step to Produce: ---------------------------- 1. Create a MO with work orders. 2. Split the MO. 3. Open the backorder MO and check the work order states. With this Commit: ---------------------------- The issue was due to improper state computation and a lack of necessary dependencies. The dependencies have been properly applied, ensuring the correct state computation of work orders in backorder MOs. Task-id: 4410926
Code cleanup and technical improvements
Mexican electronic invoicing can now attach more than one addenda to an invoice and place required extra information in either the Addenda or Complemento sections. This improves compliance flexibility for businesses that need to send customer- or authority-specific XML details before government submission.
Original PR description
This commit refactors the usage of `l10n_mx_edi.addenda` to allow adding multiple addendas at once, and also to support injecting to Complemento instead of Addenda node. On top of it, we will now also be able to inject before sending to make sure the injected XML gets sent to the government. - l10n_mx_edi_addenda_id on res_partner and account_move is now l10n_mx_edi_addenda_ids (Many2many) - new fields in the addenda model to support specifying where to inject the XML, and when to inject so that it may be sent to government related-upgrade-PR: https://github.com/odoo/upgrade/pull/6862 task-id: 3894067