Monday, July 15, 2024
38 changes
11 changes
Enhancements to existing features
The Sign template action previously called Duplicate has been moved to a more appropriate place and renamed Edit. This makes the action clearer for users when they need to modify or reuse signing templates.
Original PR description
In the Sign module, move the 'Duplicate' button to a new location and rename it to 'Edit'. task: 3977796
Features or functions removed from Odoo
An obsolete file from Marketing Automation was removed after a previous update changed how users create new items. This cleanup reduces leftover code and helps keep the module easier to maintain, with no expected change for day-to-day users.
Original PR description
Following odoo/enterprise#61777 , the action helper is removed to use instead a dialog template picker when using the 'new' button. However, it looks like one of the file should have been cleaned but was not. This commit removes it. Task-4035826
Code cleanup and technical improvements
This internal cleanup makes messaging-related data use the same names across Python and the web interface. It reduces duplicate technical labels and prepares the system for future improvements in how related records are handled, without changing day-to-day user workflows.
Original PR description
Not having the correct name based on python model name makes it much harder to implement future improvement such as auto-formatting of relations (PR in progress: https://github.com/odoo/enterprise/pull/66544) due to python having no knowledge of JS model definitions. This also allows to remove a lot of unnecessary type and model keys for channel and persona, because they can be deduced from the model name. Part of task-3605717 https://github.com/odoo/odoo/pull/172731
Miscellaneous changes
In this commit, we test the feature implemented in this PR: https://github.com/odoo/enterprise/pull/50383 task-3874263 Forward-Port-Of: odoo/enterprise#66367 Forward-Port-Of: odoo/enterprise#61329
Original PR description
In this commit, we test the feature implemented in this PR: https://github.com/odoo/enterprise/pull/50383 task-3874263 Forward-Port-Of: odoo/enterprise#66367 Forward-Port-Of: odoo/enterprise#61329
2 changes
Resolved issues and error corrections
This update fixes visual alignment issues in the sign module where text and icons were inconsistently positioned in both the customer portal and backend interfaces. The fix ensures a polished, professional appearance with consistent alignment across all sign-related screens, improving the overall user experience.
Original PR description
Before this PR: In the sign module, there are inconsistencies with the alignment of texts and icons, in both the portal and backend interfaces. After this PR: This fix addresses alignment issues and ensures consistency between the portal and backend interfaces. Now, texts and icons in the sign appear aligned and consistent across both interfaces.
This change simplifies the internal tour testing setup by moving disabled-element checks from each tour step definition into the shared action helpers. It keeps test behavior consistent while reducing maintenance across business apps such as Approvals, Payroll, Planning, Studio, Inventory, Rentals, and Appointments.
Original PR description
To simplify the tours API and the number of keys a tour step can have, it was decided to remove the allowDisabled key. In reality, it was not really removed but moved to the tour helpers side. Indeed, when performing the action, we check at that moment whether the targeted element is enabled or not depending on the action that is performed (click, dblclick, draganddrop,...). If the element isn't enabled, it throws an error. task~3974087 https://github.com/odoo/odoo/pull/171028
When opening a message thread on cells, the request fetching the messages is not properly awaited. We didn't find any actual issue with this (in prod or in tests), but this is the kind of things leading to non-deterministic tests. So we prefer to fix it. Forward-Port-Of: odoo/enterprise#66601 Forward-Port-Of: odoo/enterprise#66559
Original PR description
When opening a message thread on cells, the request fetching the messages is not properly awaited. We didn't find any actual issue with this (in prod or in tests), but this is the kind of things leading to non-deterministic tests. So we prefer to fix it. Forward-Port-Of: odoo/enterprise#66601 Forward-Port-Of: odoo/enterprise#66559
In this PR: Steps to reproduce: 1. Create a POS session. 2. Make two orders: one with an invoice and one without. Close the session. 3. Create another session, make an order, and create an invoice for an order from the previous session. Close the session. 4. Create a GST return period and generate the GSTR-1 spreadsheet. Changes made: - Fixed the retrieval of POS line details by move ID. - Added a safe access method using get to prevent key errors during HSN summary generation. Ta
Original PR description
In this PR: Steps to reproduce: 1. Create a POS session. 2. Make two orders: one with an invoice and one without. Close the session. 3. Create another session, make an order, and create an invoice for an order from the previous session. Close the session. 4. Create a GST return period and generate the GSTR-1 spreadsheet. Changes made: - Fixed the retrieval of POS line details by move ID. - Added a safe access method using get to prevent key errors during HSN summary generation. Task ID: 3935317 Forward-Port-Of: odoo/enterprise#66596 Forward-Port-Of: odoo/enterprise#66311
Forward-Port-Of: odoo/enterprise#66635
Original PR description
Forward-Port-Of: odoo/enterprise#66635
**Steps to reproduce the bug:** - Create a storable product P1 with BoM: - Component: Add any component - operation: OP1 - Create a MO with P1: - Confirm it - Start the workorder and mark it as done - Come back to the dashboard > workorders list - Select the finished workorder - Try to start it **Problem:** The work order can be started while it is in the 'done' state. When the function `button_start` is called, we will check if we need to skip the employee ch
Original PR description
**Steps to reproduce the bug:** - Create a storable product P1 with BoM: - Component: Add any component - operation: OP1 - Create a MO with P1: - Confirm it - Start the workorder and mark it as done…
**Steps to reproduce the bug:**
- Create a storable product P1 with BoM:
- Component: Add any component
- operation: OP1
- Create a MO with P1:
- Confirm it
- Start the workorder and mark it as done
- Come back to the dashboard > workorders list
- Select the finished workorder
- Try to start it
**Problem:**
The work order can be started while it is in the 'done' state.
When the function `button_start` is called, we will check if we need to
skip the employee check or not. However, since the current user is also
an employee, we will use them:
https://github.com/odoo/enterprise/blob/c4604d8b398713898b014e6073219d6202c154c3/mrp_workorder/models/mrp_workorder.py#L258-L259
The function start_employee will then be called:
https://github.com/odoo/enterprise/blob/c4604d8b398713898b014e6073219d6202c154c3/mrp_workorder/models/mrp_workorder.py#L284-L286
The state of the work order will then be updated:
https://github.com/odoo/enterprise/blob/c4604d8b398713898b014e6073219d6202c154c3/mrp_workorder/models/mrp_workorder.py#L740"
opw-4024904
Forward-Port-Of: odoo/enterprise#66358task-4004305 Forward-Port-Of: odoo/enterprise#65167
Original PR description
task-4004305 Forward-Port-Of: odoo/enterprise#65167
Updated description when connecting new IoT Box to db, added help buttons redirecting to Odoo documentation. Task: 4021957 Forward-Port-Of: odoo/enterprise#66298
Original PR description
Updated description when connecting new IoT Box to db, added help buttons redirecting to Odoo documentation. Task: 4021957 Forward-Port-Of: odoo/enterprise#66298
Code cleanup and technical improvements
The subscription invoice generation process has been refactored to introduce a new customization hook. This makes it easier for developers to modify how invoices are processed without rewriting the entire function. Businesses can now customize invoice workflows more efficiently, such as keeping auto-generated invoices in draft state before posting.
Original PR description
before this commit, if some customization has to be done for changing the workflow of invoice generation, i.e., to keep the auto generated invoice in draft state the entire function has to be rewritten after this commit, a hook is introduced _process_auto_invoice which will post the invoice, later to alter this flow just need to inherit this function Forward-Port-Of: odoo/enterprise#66200