Search
Navigate
Branch
Wednesday, April 26, 2023
16 changes
New functionality added to Odoo
Adds a new Point of Sale self-ordering module that lets restaurant customers browse menus and place orders themselves, including through QR-code menu flows. This can reduce staff workload, speed up table service, and create a more modern ordering experience.
Sign requests can now include automatic email reminders for recipients who have not responded, helping businesses complete documents faster. Users can also set an expiry date after which a request is no longer available, improving control over time-sensitive agreements.
Original PR description
This PR add an email reminder to the sign requests that is setup at the creation of sign request sent by mail. These reminder mail are sent by a CRON to all recipient that have not responded yet and haven't chosen to ignore the reminder for this Sign Request. Validity allow the user to set a validity after which the sign request will be unavailable. task-id : 3230052
Enhancements to existing features
Users can now show, sort, filter, and group documents by file extension in the Documents list. File extensions are detected during upload, can be corrected later, and are used to keep downloaded filenames accurate when needed.
Original PR description
We have added the file extension in the list view in order to ease the search of document by format. The user can enable the file extension column in the view and sort on it and also perform a filter or a group by extension. The extension is automatically detected when uploading a new file and can be changed later in the document inspector if the auto-detection fails. Task-3221644
Resolved issues and error corrections
Cohort reports no longer fail when they are based on date-only fields. This prevents an error screen and helps users reliably view cohort analysis for records that use dates instead of date-times.
Original PR description
Since b0a952ab1ba132de863c59b251fff8c8942de640,
get_cohort_data doesn't work with `fields.Date`:
File "/data/build/odoo/odoo/api.py", line 430, in _call_kw_model
result = method(recs, *args, **kwargs)
File "/data/build/enterprise/web_cohort/models/models.py", line 91, in get_cohort_data
if col_start_date > datetime.today():
TypeError: can't compare datetime.datetime to datetime.date
Previously every date/datetime string (result of `_read_group_raw`) was converted into datetime. Now _read_group return the same date type than the field used.
Fix this issue.Miscellaneous changes
Before this commit invoices sent automatically via the subscriptions were not properly generated / linked to the account.move. This is because of: https://github.com/odoo/odoo/commit/955091e707df1206ccda8314f1f182e2a37a8 362 that changed the way we want to generate invoices. This commit ensures that we rely on the send&print flow for invoice generation. task-id:3253019 Forward-Port-Of: odoo/enterprise#39011
Original PR description
Before this commit invoices sent automatically via the subscriptions were not properly generated / linked to the account.move. This is because of: https://github.com/odoo/odoo/commit/955091e707df1206ccda8314f1f182e2a37a8 362 that changed the way we want to generate invoices. This commit ensures that we rely on the send&print flow for invoice generation. task-id:3253019 Forward-Port-Of: odoo/enterprise#39011
The Odoo 16 refactoring of Accounting forgot to adapt the Winbooks import module. This fix: - allows imported analytics items to be negative - imports existing data from the imported file to be kept as is (no recomputing of already existing VAT lines, for example) - adapts the formatting of Odoo-generated counterpart balancing lines to the new refactored flow (when importing an unbalanced move). opw-3198906 Forward-Port-Of: odoo/enterprise#39945
Original PR description
The Odoo 16 refactoring of Accounting forgot to adapt the Winbooks import module. This fix: - allows imported analytics items to be negative - imports existing data from the imported file to be kept as is (no recomputing of already existing VAT lines, for example) - adapts the formatting of Odoo-generated counterpart balancing lines to the new refactored flow (when importing an unbalanced move). opw-3198906 Forward-Port-Of: odoo/enterprise#39945
In sign, when sending the sign.request via email, we were not translating the email content with the partner's language. This commit fixes this by passing the correct language when we call the qweb render method. task-3267171 Forward-Port-Of: odoo/enterprise#40006
Original PR description
In sign, when sending the sign.request via email, we were not translating the email content with the partner's language. This commit fixes this by passing the correct language when we call the qweb render method. task-3267171 Forward-Port-Of: odoo/enterprise#40006
Before this fix, we used .show() and .hide() to toggle lines' display. These 2 functions add a style "display: block" and "display: none" on the selected element. It caused a problem because the table row should have a "display: table-row" instead. Now, we're toggling a specific class to hide lines or not. This class adds a "display: none" on the line. opw-3236881 opw-3237049 Forward-Port-Of: odoo/enterprise#40270
Original PR description
Before this fix, we used .show() and .hide() to toggle lines' display. These 2 functions add a style "display: block" and "display: none" on the selected element. It caused a problem because the table row should have a "display: table-row" instead. Now, we're toggling a specific class to hide lines or not. This class adds a "display: none" on the line. opw-3236881 opw-3237049 Forward-Port-Of: odoo/enterprise#40270
Add condition to generate AddressTypeCode only for clients with RUC   Legal Reference: https://cpe.sunat.gob.pe/sites/default/files/inline-files/ValidacionesGREv20221020_publicacion.xlsx Support Ticket: https://www.odoo.com/web#id=3264284&menu_id=4720&cids=3&action
Original PR description
Add condition to generate AddressTypeCode only for clients with RUC   Legal Reference: https://cpe.sunat.gob.pe/sites/default/files/inline-files/ValidacionesGREv20221020_publicacion.xlsx Support Ticket: https://www.odoo.com/web#id=3264284&menu_id=4720&cids=3&action=333&active_id=49&model=project.task&view_type=form Latam Task: https://latam-localizations.odoo.com/web#id=1006&menu_id=88&cids=1&action=188&model=project.task&view_type=form Forward-Port-Of: odoo/enterprise#39394
Currently, the formula for calculating the average creditors days in the executive summary is wrong. It is using the operating income as the denominator, instead of the the cost of goods sold, which can be computed as the sum of the cost of sales and the expenses (excluding depreciation). opw-3222694 Forward-Port-Of: odoo/enterprise#40271 Forward-Port-Of: odoo/enterprise#40184
Original PR description
Currently, the formula for calculating the average creditors days in the executive summary is wrong. It is using the operating income as the denominator, instead of the the cost of goods sold, which can be computed as the sum of the cost of sales and the expenses (excluding depreciation). opw-3222694 Forward-Port-Of: odoo/enterprise#40271 Forward-Port-Of: odoo/enterprise#40184
When a provider does not support a company currency, a UserError is raised. This is a problem for the cron, as all companies rate updates are stopped or rolled back. To avoid this, we differentiate between the manual and cron using a method arg (with default to False). In the case of manual update, errors are raised. But the cron will suppress warnings to the log. Task-3265345 OPW-3188333 Forward-Port-Of: odoo/enterprise#39658
Original PR description
When a provider does not support a company currency, a UserError is raised. This is a problem for the cron, as all companies rate updates are stopped or rolled back. To avoid this, we differentiate between the manual and cron using a method arg (with default to False). In the case of manual update, errors are raised. But the cron will suppress warnings to the log. Task-3265345 OPW-3188333 Forward-Port-Of: odoo/enterprise#39658
Description of the issue/feature this PR addresses: In kanban view of field service, there is a break line between partner name and partner city. Current behavior before PR: partner name and partner city are in different line. Desired behavior after PR is merged: partner name and partner city are in same line. Fix: in kanban view of project module, partner city is inherit from the industry_fsm module. Style is added in both the fields(partner name and city), due to which line break
Original PR description
Description of the issue/feature this PR addresses: In kanban view of field service, there is a break line between partner name and partner city. Current behavior before PR: partner name and partner city are in different line. Desired behavior after PR is merged: partner name and partner city are in same line. Fix: in kanban view of project module, partner city is inherit from the industry_fsm module. Style is added in both the fields(partner name and city), due to which line break is occurs. so style is removed from both the fields and added to the parent <span> tag of the fields. <t> tag is converted into <span> tag so that style can be applied. task-3252521 Forward-Port-Of: odoo/enterprise#39756
Steps to reproduce: - install quality_mrp_workorder - create 2 SN tracked products: test_manufacture, test_component - add 2 test_component into stock (i.e. 2 SNs) - create BoM for test_manufacture w/ 1 operation + test_component consumed in the operation - create + confirm a MO for test_manufacture - open WO tablet view + set both finished_lot_id and lot_id (set lot_id to the NOT reserved SN) - click on validate Expected behavior: - finished_product_check_ids shows test_component - (
Original PR description
Steps to reproduce: - install quality_mrp_workorder - create 2 SN tracked products: test_manufacture, test_component - add 2 test_component into stock (i.e. 2 SNs) - create BoM for test_manufacture…
Steps to reproduce: - install quality_mrp_workorder - create 2 SN tracked products: test_manufacture, test_component - add 2 test_component into stock (i.e. 2 SNs) - create BoM for test_manufacture w/ 1 operation + test_component consumed in the operation - create + confirm a MO for test_manufacture - open WO tablet view + set both finished_lot_id and lot_id (set lot_id to the NOT reserved SN) - click on validate Expected behavior: - finished_product_check_ids shows test_component - (your selected sn) Actual behavior: - finished_product_check_ids shows test_component - (original reserved sn) Issue was due to: https://github.com/odoo/enterprise/blob/88031ec9e4a3db7ac96a7e3d9feaf44305c6c46b/quality_mrp/models/quality.py#L31-L33 always being called, even if the compute is triggered by the production_id.lot_production_id, which means the selected qc.lot_id would be overwritten by the qc.move_line_id.lot_id in the super: https://github.com/odoo/enterprise/blob/88031ec9e4a3db7ac96a7e3d9feaf44305c6c46b/quality_control/models/quality.py#L164-L169 Unfortunately because _compute_lot_line_id is being used to handle different use cases, the move_line `write` must also be overridden. Cases to be handled: - QC set on MO for SN tracked product (QC.lot_id should ALWAYS match sml.lot_id) - sml.lot_id is changed => all QCs associated with it (MO or operation related) will have their lot_id updated to match - `register_consumed_materials` QC lot_id is changed to NOT match sml.lot = allowed => QC validation = sml.lot_id should be updated to match QC.lot_id opw-3129597 Forward-Port-Of: odoo/enterprise#39584 Forward-Port-Of: odoo/enterprise#38364
Due to performance issues, the computation of the balance in GL was changed (odoo/odoo#103697) Since it is computed in `_get_journal_dashboard_bank_running_balance` as the last statement balance (balance_end_real) + transactions (account.bank.statement.line since the last statement), we rename the label on the journal dashboard to "Running Balance". Also, fix the order clause of the "Last Statement" balance as it has a problem when there are 2 statements on the same day. OPW-3265511 Forward-
Original PR description
Due to performance issues, the computation of the balance in GL was changed (odoo/odoo#103697) Since it is computed in `_get_journal_dashboard_bank_running_balance` as the last statement balance (balance_end_real) + transactions (account.bank.statement.line since the last statement), we rename the label on the journal dashboard to "Running Balance". Also, fix the order clause of the "Last Statement" balance as it has a problem when there are 2 statements on the same day. OPW-3265511 Forward-Port-Of: odoo/enterprise#40194
In 16.2, we made a task (https://www.odoo.com/web#id=3097097&cids=1&menu_id=4720&action=333&active_id=967&model=project.task&view_type=form) to improve the layout of invoice. But the l10n_ec localisation was wrongly impacted due to a xpath. This commit correct that by changing the xpath with the id added in the community pr. opw-3097097 Forward-Port-Of: odoo/enterprise#40203
Original PR description
In 16.2, we made a task (https://www.odoo.com/web#id=3097097&cids=1&menu_id=4720&action=333&active_id=967&model=project.task&view_type=form) to improve the layout of invoice. But the l10n_ec localisation was wrongly impacted due to a xpath. This commit correct that by changing the xpath with the id added in the community pr. opw-3097097 Forward-Port-Of: odoo/enterprise#40203
search only 1 purchase journal and don't match b2c vendors in GSTR2B opw-3275773 Forward-Port-Of: odoo/enterprise#39878
Original PR description
search only 1 purchase journal and don't match b2c vendors in GSTR2B opw-3275773 Forward-Port-Of: odoo/enterprise#39878