Daily updates from Odoo
Monday, June 27, 2022
11 changes · master
Enhancements to existing features
Several Odoo Enterprise apps now use a shared messaging asset bundle. This keeps messaging-related features more consistent across approvals, signing, VoIP, and live chat while reducing duplicated setup behind the scenes.
Original PR description
*:
approvals
sign
voip
voip_onsip
website_helpdesk_livechat
Task-2894450
Community: https://github.com/odoo/odoo/pull/94722VoIP now relies on the shared browser capability check to determine whether real-time calling is supported. This helps keep calling behavior consistent with the rest of Odoo and reduces the chance of incorrect availability shown to users.
Original PR description
Community: https://github.com/odoo/odoo/pull/94683
Odoo Studio now places its editing hook in a more stable part of the form view to avoid conflicts during screen rendering. This helps make form customization more reliable, especially around the chatter area, without changing user-facing functionality.
Original PR description
Having the hook on the component conflicted with the render of that component. Move the hook to the parent that is controlled by the form view. Part of task-2871070 https://github.com/odoo/odoo/pull/94307
The Planning portal now shows published open shift dates in a clearer, consistent format. This makes it easier for users to compare open shifts and calendar details without confusion.
Original PR description
This commit changes the way dates are displayed in the portal view for the published `planning.slot`. It also ensures that the format used in the calendar popover and in the section `Open Shifts Available` are the same. task-2741623
Employee NISS values are no longer calculated or tracked for companies outside Belgium. This avoids confusing updates when employee identification details are changed in non-Belgian companies.
Original PR description
The field `niss` was computed and tracked even for non-BE companies, which was a bit confusing when updating the Identification ID of the employee. TaskID: 2859750
Resolved issues and error corrections
The attachment viewer now responds more reliably when invoices move from draft to confirmed and when screen size changes. This prevents layout issues such as incorrect side panels or margins, improving the consistency of the form view for users.
Original PR description
Make hasAttachmentViewer more state oriented than lifecycle oriented. This will fix issue where `aside` is not correctly computed when going from draft invoice to confirmed invoice (attachment viewer gaining the invisible modifier). As a bonus, it will also fix margin issues when going from large screen to small screen while the attachment viewer is active. task-2894325 Part of task-2871070
Code cleanup and technical improvements
This update simplifies how dashboard tooltip information is passed behind the scenes in Payroll and dashboard components. It should not change what users see, but it makes the code easier to maintain and aligns it with newer framework capabilities.
Original PR description
Previously, we would use t-set to add the tooltip info under the key "info" in the rendering context, while this works fine, it was mostly just a workaround for the lack of support in owl for passing a rendering context to be used by the t-call directly. Since this is now supported in owl, the commit uses this feature for the tooltips and adapts the use sites. community: odoo/odoo#94626
Miscellaneous changes
Forward-Port-Of: odoo/enterprise#28808 Forward-Port-Of: odoo/enterprise#27342
Original PR description
Forward-Port-Of: odoo/enterprise#28808 Forward-Port-Of: odoo/enterprise#27342
…n email SO If applied, this commit will fix the following bug by checking for inter company SOs in a more precise way: Steps to reproduce: 1- install sale, purchase, inter_company 2- Create a service product p with auto purchase activated 3- create a Sales Order SO with p normal: 4- confirm the SO 5- a PO is created automatically email: 4- send the SO by email to confirm 5- PO is not created although SO is confirmed Bug: the condition used to check for inter company
Original PR description
…n email SO If applied, this commit will fix the following bug by checking for inter company SOs in a more precise way: Steps to reproduce: 1- install sale, purchase, inter_company 2- Create a service product p with auto purchase activated 3- create a Sales Order SO with p normal: 4- confirm the SO 5- a PO is created automatically email: 4- send the SO by email to confirm 5- PO is not created although SO is confirmed Bug: the condition used to check for inter company operation also matches SO confirmed from email Fix: refine the condition statement to only match inter company operations OPW-2820432 Forward-Port-Of: odoo/enterprise#28801 Forward-Port-Of: odoo/enterprise#26576
Steps to repoduce: - create a storable product - Set the quantity on hand: 100, location: wh/stock/shelf1 - Create a new quotation with Field Service as a product. Confirm the quotation. - Click on the Task smar button and on products: add 1 unit of the storable product you created. - Back on the Task smart button, click on "Mark as Done" Issue: In delivery smart button, on the move lines, the location will be "wh/stock" and not "wh/stock/shelf1" Solution: Verify the qty available a
Original PR description
Steps to repoduce: - create a storable product - Set the quantity on hand: 100, location: wh/stock/shelf1 - Create a new quotation with Field Service as a product. Confirm the quotation. - Click on the Task smar button and on products: add 1 unit of the storable product you created. - Back on the Task smart button, click on "Mark as Done" Issue: In delivery smart button, on the move lines, the location will be "wh/stock" and not "wh/stock/shelf1" Solution: Verify the qty available and only create new order lines if there is not enough stock opw-2831134 Forward-Port-Of: odoo/enterprise#28866 Forward-Port-Of: odoo/enterprise#26993
This condition was added to exclude employees who already received their eco-vouchers before june (aka employees who left the company and received the amount at that time). But the employees who stayed in the company were excluded too as we were including june, which the month where we actually pay the eco-vouchers. Forward-Port-Of: odoo/enterprise#28843
Original PR description
This condition was added to exclude employees who already received their eco-vouchers before june (aka employees who left the company and received the amount at that time). But the employees who stayed in the company were excluded too as we were including june, which the month where we actually pay the eco-vouchers. Forward-Port-Of: odoo/enterprise#28843