Thursday, November 18, 2021
8 changes · master
Enhancements to existing features
This change centralizes common business calculations used across invoices, sales, purchases, and related flows. It helps ensure prices, taxes, fiscal position mappings, and vendor-specific values are handled consistently, reducing discrepancies between documents and improving future EDI support.
Original PR description
Multiple things are duplicated in every business models and sometimes, done in a wrong way like taxes management.
For example:
- price included taxes set on a product with fiscal position mapping
- taxes using the round globally setting
- default price_unit suggested on a line from product
Also, there is some feature that are badly managed like the custom seller on product that is currently working only with purchase but give different results on vendor bill.
In the future, we will need to unify all these behaviors to manage more easily the values to be set on EDI documents (only working on invoices right now).
task_id: 2654784
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prEmployee skill records are easier to manage, with clearer forms and automatic resetting of skill levels when the skill or skill type changes. This helps HR teams keep skill information consistent and better organized.
Original PR description
- Reset skill levels on skill/skill type change - Improve form view - Add a sequence on hr.skill TaskID: 2575351 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website editors can now customize the connector lines between steps by choosing their style and color. This improves visual flexibility for process or timeline sections while keeping connectors aligned when layouts resize.
Original PR description
New options are added to the steps snippets, allowing to pick the type of the steps connector and its color. A Widget linked to the s_process_steps snippet is introduced to reload the connectors when a column or the window is resized. As the length and position of the connectors is computed from the widget, a class o_loaded was added to avoid flickering before the final render. The s_process_steps snippet CSS version is now 001. Coming from https://github.com/odoo/odoo/pull/71152 task-2463009 Co-authored-by: Matthieu Stockbauer <tsm@odoo.com> -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Clicking a department from an employee record now opens the employee kanban filtered to that department instead of the department form. This helps HR users quickly see everyone in the same department and navigate employee information more efficiently.
Original PR description
Description of the issue/feature this PR addresses: Display the kanban view of the employees when clicking on the department from the employee form Current behavior before PR: Clicking on the department from the employee form displays the default form for the department Desired behavior after PR is merged: Clicking on the department from the employee form displays the kanban views with the employees of the department task-2678198 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The customer follow-up settings screen now uses tabs again, making email and letter options easier to navigate. The update keeps the newer email subject field, clarifies the message body label, and shows customization guidance when sending letters is selected.
Original PR description
Revert view changes made in commit https://github.com/odoo/enterprise/commit/24ffaf34439fca4bbddda7029c9c09c24d3238d4 while : - taking into account 'email subject' field introduced in said commit - change description title to 'Message Body', and only display it when email subject is also shown - showing 'ho to customize' also when 'send a letter' is only action checked Task: 2669223
This update centralizes common business calculations such as taxes, product pricing, fiscal position handling, and seller selection so they behave more consistently across documents. It reduces duplicated logic and helps invoices, purchases, sales, subscriptions, and EDI-related flows produce more reliable results.
Original PR description
Multiple things are duplicated in every business models and sometimes, done in a wrong way like taxes management.
For example:
- price included taxes set on a product with fiscal position mapping
- taxes using the round globally setting
- default price_unit suggested on a line from product
Also, there is some feature that are badly managed like the custom seller on product that is currently working only with purchase but give different results on vendor bill.
In the future, we will need to unify all these behaviors to manage more easily the values to be set on EDI documents (only working on invoices right now).
task_id: 2654784Chile localization now uses standardized Latin American document types for referenced documents instead of a fixed list, making document matching more consistent. Incoming vendor bills with unknown reference document information are handled more gracefully, reducing manual interruptions when processing electronic invoices.
Original PR description
Instead of using a selection field for reference document types, we use a many2one field with latam document type. This PR is related to its homonym in: https://github.com/odoo/odoo/pull/75865 Additionally in fetchmail server implementation: when vendor bills enter, with an unknown code/type/reference field, this document is automatically created in latam document type model.
Resolved issues and error corrections
This update separates general document activation from whether Chilean document types can be used in invoicing. It prevents users from selecting inactive or unsuitable reference documents and also refreshes related Chilean tax, account, and translation data.
Original PR description
This PR solves the problem that is produced in l10n_cl_edi, when trying to select as a reference, a document type that is not active. We replaced the use of the active field with l10n_cl_active field. This new field is used to indicate odoo, which active documents should be included as usable in invoicing, instead of using the active field. #20565 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr