Wednesday, April 17, 2024
10 changes
3 changes
Enhancements to existing features
HR teams can now mark specific fleet vehicle stages so vehicles in those stages no longer appear in the salary configurator. This keeps employee salary offers focused on eligible vehicles and reduces confusion during package selection.
Original PR description
When hide_in_offer set to true, all the vehicles in that stage will not appear in the salary configurator anymore task-3649947
Resolved issues and error corrections
Appointment invitation emails now include the correct Google Meet link when a meeting is booked with Google Calendar synchronization. This helps attendees join meetings easily and ensures the required Google Calendar integration is installed automatically when needed.
Original PR description
Steps to reproduce ==================== 1. Install Appointment and the Gcal sync. 2. Sync your Google Calendar. 3. Create an appointment type and select Google Meet in the videoconference link. 4. Book an appointment. The meeting link is not propagated to invitation mail. After this PR ================== -The meeting link is propagated to mail. -The appointment_google_calendar module is automatically installed based on dependencies. Task-3614890
Code cleanup and technical improvements
Payment and subscription follow-up actions are now handled after the main payment state change, so one failed action is less likely to block other required business steps. This improves reliability for subscription payments, SEPA direct debit, appointment payments, and related tax flows without changing the customer-facing payment process.
Original PR description
Some modules were overriding \_set\_'state' functions to trigger some business operations. In case of failure of one override function the rest of them would also fail. This overrides are moved to post-processing in order to ensure proper execution of all functions. See also: - https://github.com/odoo/odoo/pull/144710 - https://github.com/odoo/upgrade/pull/5546 task-2309987
7 changes
Enhancements to existing features
Odoo now successfully imports UBL electronic invoice files that have namespaces formatted on individual lines instead of just in the root element. This improvement ensures that invoice data can be properly extracted from a wider variety of UBL file formats, reducing import failures and improving compatibility with different EDI systems.
Original PR description
Backporting: https://github.com/odoo/odoo/commit/1e24b151c6ad0023769b5a561690cb62bcda1d8a When importing a UBL file, Odoo expects the UBL specific namespaces to be in the root element of the file. This is not always the case as these namespaces could exist in every element in the file. When a file is formatted this way, Odoo cannot extract the necessary data from it because it is missing the necessary namespaces. To cover this case we use the lxml.etree.Element.find function instead, and pass in the UBL specific namespaces to successfully extract the data. task-3657563 opw-3839398 Forward-Port-Of: odoo/odoo#161857 Forward-Port-Of: odoo/odoo#161034
Resolved issues and error corrections
This update improves the appointment booking experience by adding a 'More Options' button that lets users access the complete appointment form without opening a new tab. It also fixes an issue where the wrong person was being set as the organizer when booking through the calendar view. These changes make the booking process more efficient and accurate.
Original PR description
1>To activate the complete form view, allowing additional details beyond the fields in the 'calendar_event_view_form_gantt_booking' view to be included without requiring users to open a new tab and search for the event separately, which is highly inefficient. 2>The logged user was being set as an organizer by default even though a particular attendee's slot had been clicked on the gantt view. so the attendee will be set as an organizer by default when clicking on the slot. A test case has been added to ensure the above functionality for the gantt view does not break. Task-3679307
This fix resolves an error that occurred when employees tried to request signatures for multiple contracts at once from the contracts list. The signature request action has been removed from the bulk actions menu to prevent this issue, ensuring users can only request signatures for individual contracts.
Original PR description
STEP TO REPRODUCE:
=================
* Go on Employee App
* Select contracts menu item
* Select two contracts
* Click on actions
* Select "signature request"
You will have a traceback due to multiple selection.
task: 3802377This fix prevents crashes when users try to add access rights category fields to the Users view in Odoo Studio. These fields are dynamic and change based on group hierarchy, so they are no longer offered as available fields to add. This improves the stability and user experience when customizing user management views.
Original PR description
…or res.users Open the base action for res.users (Settings => Users) Unfold the Existing fields list, and search for a field reprensenting an access rights category. Before this commit, adding such field crashed because some meta data were missing in the fields_get. Since those fields are dynamic and may change with any changes in groups' hierarchy, it doesn't really make sense to make them available to add on a view. Before this commit, those fields are not proposed any more. opw-3842879 Forward-Port-Of: odoo/enterprise#60719 Forward-Port-Of: odoo/enterprise#60321
This fix resolves an issue where e-invoices submitted from Rio Grande do Sul were being rejected by tax authorities due to missing recipient name information. The system now correctly includes the location name attribute when required by specific Brazilian states, allowing invoices to be successfully submitted and processed.
Original PR description
Some states (e.g. Rio Grande do Sul) require the name attribute to be set, others (e.g. Paraná) do not and will take the businessName. Before this, submitting an e-invoice for Rio Grando do Sul results in "Rejeicao: NF-e sem o nome do destinatario" (code: 724). After this, submitting the invoice succeeds. opw-3793773
This fix resolves issues with how the accounting system handles dependencies across multiple companies. The change ensures that account move line records properly respect company boundaries, preventing data conflicts and ensuring accurate financial reporting when using multiple company configurations.
Original PR description
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
This fix resolves a bug where autocomplete fields (like the salesperson field in CRM) could get stuck with invalid values that couldn't be saved. When users typed an invalid value and clicked away, scrolled, or pressed escape, the field would remain in a broken state. Now the field properly reverts to the last valid value, ensuring data integrity and preventing confusing situations where changes appear unsaved.
Original PR description
This commit fixes a bug where the value of an autocomplete with autoselect could go into an undefined state where the model value doesn't match the input value but no change is detected. This would…
This commit fixes a bug where the value of an autocomplete with autoselect could go into an undefined state where the model value doesn't match the input value but no change is detected. This would happen on escape press, scroll and more recently due to https://github.com/odoo/odoo/pull/159333 on click out. To fix this issue, the commit introduces some change in the autocomplete behavior so that it will no longer select the active option on click out (blur) when autoselect is active and instead it will revert the input value to the one stored into the model. Also applies this behavior on escape key press and scroll for the before mentioned reasons. Steps to reproduce: - Go to CRM form view - Edit the salesperson name to some non existant one and click out (or scroll or press escape) Before the fix, the name was stuck to the invalid one but no change was detected so we couldnt save it. Before https://github.com/odoo/odoo/pull/159333, click out would select the active option of the dropdown instead (and launch a dialog for quick create). This is removed because the behavior is neither intuitive nor practical. After the fix, the name is reset to its previous valid value instead. This applies to all autocomplete components with autoselect prop set to true. Forward-Port-Of: odoo/odoo#161913 Forward-Port-Of: odoo/odoo#161251