Monday, September 9, 2024
9 changes · master
New functionality added to Odoo
Users can now choose whether an Engineering Change Order should update a product version when it is applied. This gives teams more control over product lifecycle changes and avoids unnecessary version changes when an ECO does not require one.
Original PR description
With this Commit : -------------------------------------- -Introduced a new checkbox in the ECO form allowing users to choose whether to update the version when applying the ECO. -This feature provides greater flexibility for users by giving them control over version updates during the ECO process. Task id : 3962137
Enhancements to existing features
The contract form now always shows the salary attachment button, even when no attachments exist yet. Users can also create new salary attachments directly from the contract, making payroll setup and maintenance faster and more convenient.
Original PR description
This PR improves the contract form view by making the salary attachment button visible even when there are zero attachments. Additionally, it allows users to directly create new attachments from the contract form view. task-4096116
This change adds support for the newer Font Awesome 6 icon set while keeping the existing Font Awesome 4 icons available. It helps preserve compatibility for current screens and customizations while enabling newer icon choices in the web interface.
Original PR description
https://github.com/odoo/odoo/pull/179626
Engineering changes can now be applied without automatically increasing the product or Bill of Materials version number. This gives teams more control over when version numbers change while keeping the existing automatic update behavior as the default.
Original PR description
Sometimes users don't want an ECO to affect the version number of a product/BoM when it is applied, so we add in the option to avoid it. By default we leave `will_update_version=True` so that the current behavior is still the default behavior. This involved manually updating code in several places to ensure this behavior occurs for many different flows including: - create BoM ECO from MO, - applying rebase/conflict resolve due to orig BoM change or new BoM created by another ECO - ECO for a product Note that: - the new BoM version will auto-update when the option is activated/deactivated so that the number matches the final applied version number and is easier for the user to keep track of it. - The Update BoM (for an out of date BoM) logic has been updated to consider newer BoMs with the same version number (i.e. we still expect the previous BoMs to still be archived like the previous flow) Task: 3962137
Colombian companies can now automatically retrieve daily currency exchange rates from Banco de la Republica. This reduces manual updates and aligns exchange rates with the source commonly used by local customers.
Original PR description
The Colombian localization does not have a provider for automatic currency rates yet. This commit implements the API of the Banco de la Republica (because most of the Colombian clients already use this rate) to get the daily rate. task: 4043989
The Documents app now avoids an extra server lookup when showing certain error dialogs. This reduces the risk of server overload when many errors happen at once and helps prevent repeated error loops.
Original PR description
This commit removes the orm call which provides the id of the support folder to the error dialog and replaces it by a simple isAdmin check. The reason for this change is that in case of multiple tracebacks triggered at the same time, it could overload the server with orm calls which could also trigger more tracebacks in an infinite cycle.
When the salesperson on a subscription is changed, the linked customer record is now updated to match. This keeps customer ownership aligned during subscription changes and when confirming subscription quotations, reducing manual follow-up and reporting mismatches.
Original PR description
Before this commit, when salesperson on subscription is changed we do not change salesperson for customer related to that subscription. After this commit, update salesperson on customer if salesperson on subscription is get changed. update salesperson on customer while confirming subscription quotation. task-3891309
Resolved issues and error corrections
Belgian SODA imports with incorrect VAT details will now continue instead of stopping the process. The system creates the journal entry and records VAT-related issues in the chatter, helping onboarding and testing proceed with clearer follow-up information.
Original PR description
The blocking message for importing a soda with wrong VAT is not needed as it blocks onboarding or testing. Instead of blocking, create the journal entry and log VAT related errors in the chatter. task-4072804
Code cleanup and technical improvements
The Mexican delivery EDI stock functionality has been consolidated into the main stock EDI module because the extended address data is now required for the feature to work. This simplifies module setup and ensures businesses using Mexican delivery EDI have the required data and validations available in one place.
Original PR description
To use the mexican delivery EDI, it is now required that we have the address field from the mx_edi_extended (the module that stock_extended previously additionally depends on). Using base mx_edi_stock without the extended module will not work anymore. With that in mind, it is now a good time to make the base stock depends on extended and merge everything from the stock extended to the base stock module, including the recently merged stock_extended_31 module. task-id: 3894340