Wednesday, July 10, 2024
36 changes · master
New functionality added to Odoo
Employees can now be asked to sign documents even when they do not have an HR contract in the system. This makes document signing available to more HR workflows by separating general employee signing from contract-specific signing.
Original PR description
This module adds the ability to sign documents for employees even without hr_contract and hr_contract_sign.
Enhancements to existing features
The payroll and contract salary kanban card layouts were simplified to use newer standard interface components. This makes the views easier to maintain and helps keep the employee contract and payroll screens consistent with current Odoo interface practices.
Original PR description
In this commit we have simplified the kanban arch for the hr_payroll module. The goal is to simplify them, make them easier to read, and use bootstrap utility classnames. - Previously, we used `kanban-box`, but now we are using `kanban-card` instead. - Deprecated `oe_kanban_global_click` and `oe_kanban_global_click_edit`. - More use of `<field/>` tags - Removed the `oe_kanban_colorpicker` class and replaced it with the `kanban_color_picker` widget. - Changed type='edit' to type='open' to open records. since version 16, records always open in edit mode by default. - `kanban_image` from rendering context, is deprecated so we use `<field name=... widget=image/>` instead Task-3992107
Resolved issues and error corrections
This update corrects a spreadsheet edition test so it matches the expected behavior for comment threads. It reduces false test failures, helping keep development and release checks more reliable without changing user-facing functionality.
Original PR description
The test `Selecting the cell with a unsolved thread does not open the thread popover` was sometimes failing. After investigation, it seems like the test is plain wrong. The thread popover should open for unsolded threads, it's for resolved threads that it should not open. Running the test in debug make it clear that the threads popoved is opened. I'm not sure how the test was somehow passing before. Task: [4042515](https://www.odoo.com/web#id=4042515&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)
Miscellaneous changes
*l10n_account_customer_statements,l10n_my_reports,l10n_us_reports Currently some reports add buttons on their lines to perform some action on them. However, when prefix groups are used, the buttons are also shown on these lines, but refer to nothing and will thus either cause an error when clicked or lead to a new record. This commit fixes that by providing a generic hook in the `line_name` template to inject buttons. This generic hook checks whether the line is a prefix group line and doe
Original PR description
*l10n_account_customer_statements,l10n_my_reports,l10n_us_reports Currently some reports add buttons on their lines to perform some action on them. However, when prefix groups are used, the buttons are also shown on these lines, but refer to nothing and will thus either cause an error when clicked or lead to a new record. This commit fixes that by providing a generic hook in the `line_name` template to inject buttons. This generic hook checks whether the line is a prefix group line and doesn't render the buttons if it is. All other reports were adapted to use this hook now. task-3932945 Forward-Port-Of: odoo/enterprise#65270
The Data Cleaning manual merge view has been renamed from the less clear “merge action manager” label. It is now available without enabling debug mode, making it easier for regular users to access data merge tools.
Original PR description
With this commit, manual merge view's name will replace "merge action manager" and will be accesible without debug mode. task-3861100
Point of Sale can now use a customer's email address and mobile number for marketing communication. This helps businesses follow up with shoppers more easily after in-store purchases, including through WhatsApp-enabled workflows.
Original PR description
*: whatsapp, whatsapp_pos Before this commit: ========== - There is no feature for marketing in Point of Sale. After this commit: ========== - Now, we can use the customer's email and mobile number for marketing in Point of Sale. task-3872538
Bank reconciliation can now be created directly from the Kanban view without opening a separate popup. This streamlines the workflow and makes the process feel more consistent with other Odoo apps such as CRM and Project.
Original PR description
This commit adds the quick create feature to the bank reconciliation kanban view. (no more popup) In order to make bank reconciliation more intuitive and overall easier to use, we are opting for a quick create feature that is similar to the way it currently works in apps like CRM or Project. This makes the reconciliation flow a lot more streamlined. Task ID: 3916563
Graph views and some pivot-related components now load only when they are needed. This can make affected apps open faster and reduce unnecessary browser work, while keeping reporting features available when users access them.
Original PR description
We make the graph view and its js classes be lazy loaded. For simplicity some js classes of the pivot view are lazy loaded too. We plan to lazy load the pivot view and its other extensions/patches in the near future. Task ID: `3546321`
This commit moves the generic `_with_locked_records` from `l10n_mx_edi.document` in `l10n_mx_edi` -> `res.company` in `account` This allows multiple EDIs to use the same generic method for locking their record before using them in requests. This prevents 2 (or more) users to send the same invoice at the same time. Affected EDIs: l10n_mx_edi, l10n_ro_edi task-id: 3595436 related community PR: https://github.com/odoo/odoo/pull/144061 Forward-Port-Of: odoo/enterprise#65602
Original PR description
This commit moves the generic `_with_locked_records` from `l10n_mx_edi.document` in `l10n_mx_edi` -> `res.company` in `account` This allows multiple EDIs to use the same generic method for locking their record before using them in requests. This prevents 2 (or more) users to send the same invoice at the same time. Affected EDIs: l10n_mx_edi, l10n_ro_edi task-id: 3595436 related community PR: https://github.com/odoo/odoo/pull/144061 Forward-Port-Of: odoo/enterprise#65602
before this commit: Insurance amount was sent in rating request but not in shipping request. Resulting in no insurance amount being printed on label. After this commit: If the insurance amount is sent, it is added to the shipping request and gets printed on label. opw-3845693 Forward-Port-Of: odoo/enterprise#66036
Original PR description
before this commit: Insurance amount was sent in rating request but not in shipping request. Resulting in no insurance amount being printed on label. After this commit: If the insurance amount is sent, it is added to the shipping request and gets printed on label. opw-3845693 Forward-Port-Of: odoo/enterprise#66036
Before this commit, avatax used the longitude and latitude in priority even if the partner has an address. The problem with this is that when you print the AvaTax report, the fields DestStreet, DestCity, and DestPostalCode are not populated because AvaTax was not sent any of that information. The customer needs those fields to be populated or else they may be charged more money. So now it will be the opposite, we will use the address in priority but if the customer has a delivery address wit
Original PR description
Before this commit, avatax used the longitude and latitude in priority even if the partner has an address. The problem with this is that when you print the AvaTax report, the fields DestStreet, DestCity, and DestPostalCode are not populated because AvaTax was not sent any of that information. The customer needs those fields to be populated or else they may be charged more money. So now it will be the opposite, we will use the address in priority but if the customer has a delivery address with no address information we will use the latitude and longitude of the delivery address partner. Task: 4011481 Forward-Port-Of: odoo/enterprise#66193 Forward-Port-Of: odoo/enterprise#65726