Search
Navigate
Branch
Monday, August 14, 2023
10 changes
New functionality added to Odoo
Hong Kong payroll now supports key Inland Revenue Department employee tax reports, including IR56B, IR56E, IR56F, and IR56G. The update also improves allowance and rental benefit handling and lets employees access IR56B reports through the Documents app, making tax reporting and record sharing easier.
Original PR description
Impacted Version: - 16.4 or above This commit improve below features: - Change internet allowance field to Monetary to follow the standard - Change rental into a new model for IRD report - Add IR56B report - Add IR56E report - Add IR56F report - Add IR56G report - Document app integration for IR56B report to allow employee view the report in document app task-2901528
Enhancements to existing features
Users can now share dashboard views directly from the spreadsheet interface, making it easier to distribute insights without switching tools. This improves collaboration around dashboards and streamlines the workflow for teams using spreadsheet-based reporting.
Original PR description
This PR implements the sharing of dashboards from spreadsheet view.
Miscellaneous changes
Add tax computation for Brazil. Just like in the US, taxes in Brazil are highly variable and depend on all sorts of details of the seller, customer and the products being sold. This module provides these details to Avatax and Avatax tells us what taxes we should charge. Depending on `account_avatax` was considered and attempted but resulted in complex code and features that weren't needed, e.g. `avatax_tax_date`, `product.avatax.category` and the concept of committing records. On top
Original PR description
Add tax computation for Brazil. Just like in the US, taxes in Brazil are highly variable and depend on all sorts of details of the seller, customer and the products being sold. This module provides…
Add tax computation for Brazil. Just like in the US, taxes in Brazil are highly variable and depend on all sorts of details of the seller, customer and the products being sold. This module provides these details to Avatax and Avatax tells us what taxes we should charge. Depending on `account_avatax` was considered and attempted but resulted in complex code and features that weren't needed, e.g. `avatax_tax_date`, `product.avatax.category` and the concept of committing records. On top of that some changes needed to be made anyway to the core of `account_avatax`, most importantly having to support price-included taxes and subtracted taxes (negative "price-excluded" taxes). Another major difference is the need to have separate sandbox and production credentials and the fact that this module requires IAP: customer accounts have to be created under Odoo Inc's "master" Avatax account. A separate IAP service will create these "sub-accounts" and proxy the tax calculation requests and perform an IAP charge for each of them. A final difference is that negative lines are not allowed by the Brazilian government, because of this the module will spread these amounts over the positive lines (similar to `l10n_mx_edi`). There's also the concept of "transport" costs which are distributed over lines based on the subtotal. The downside of not inheriting `account_avatax` is duplicated code (~32% more, from 1054 LOC (excl mocked API responses) to 1388 LOC). The goal is to extract the duplicated code to a common module in master. Community PR: https://github.com/odoo/odoo/pull/128216 IAP PR: https://github.com/odoo/iap-apps/pull/610 task-2968770 Alternative approach to #39970 Forward-Port-Of: odoo/enterprise#45223 Forward-Port-Of: odoo/enterprise#43797
Grid views now handle row titles and missing measure fields more reliably, reducing errors in timesheet and web grid screens. Custom grid buttons also correctly stay hidden when their visibility rules say they should, improving consistency for users.
Original PR description
## [IMP] account_consolidation: add test for consolidation grid view ## [FIX] web_grid: hide custom button if invisible = true Before this commit, when the custom button should be invisible when a…
## [IMP] account_consolidation: add test for consolidation grid view
## [FIX] web_grid: hide custom button if invisible = true
Before this commit, when the custom button should be invisible when
a context is not there or falsy, the custom button is always displayed
because the `invisible` modifier is not used to conditionally display
the custom button.
This commit adds a visibility condition to display the custom if
invisible modifier is falsy, otherwise the custom button is not
rendered.
## [IMP] {web,timesheet}_grid: add grid_component to use it in row title
Before this commit, the row/section title was rendered with components
in `fields` registry but we have to use `Record` component to be able
to use those components since `record` is needed.
This commit creates some grid components to be able to use it in
section/row title to avoid using the `fields` registry and Record
component in grid view.
## [IMP] web_grid: avoid using parseFieldNode in grid arch parser
Before this commit, `parseFieldNode` from Field component was used
to get label for measure field, to get widget and invisible values.
This commit avoids using it and search the attributes needed directly
on the node because `parseFieldNode` also search the field component
to use but in the grid view it is not needed since the field registry
is no longer used for section and row fields.
## [FIX] web_grid: fallback on count measure if no measure field
Before this commit, when a grid view is defined without any measure
field in its definition, a traceback is occured because the "__count"
field is not inside the fieldsInfo which is expected.
This commit reviews the measureField attribute in archInfo to
determine if the field is readonly or not and then improves
editable attribute in archInfo to determine if the grid view
can be editable or not including the readonly attribute of
measure field. By doing that, it is no longer needed to check
the field inside fields info in the grid controller.
task-3222154*: l10n_din5008_account_followup,l10n_din5008_industry_fsm The DIN5008 layout is mandatory in Germany, Austria and a part of Switzerland. The community module l10n_din5008 implements it but it is currently still not working correctly for (at least) the follow-up report (from account_followup) and the task report (from industry_fsm). This PR makes the DIN5008 layout work for both of the aforementioned reports. The new modules 'l10n_din5008_account_followup' and 'l10n_din5008_industry_fsm'
Original PR description
*: l10n_din5008_account_followup,l10n_din5008_industry_fsm The DIN5008 layout is mandatory in Germany, Austria and a part of Switzerland. The community module l10n_din5008 implements it but it is…
*: l10n_din5008_account_followup,l10n_din5008_industry_fsm The DIN5008 layout is mandatory in Germany, Austria and a part of Switzerland. The community module l10n_din5008 implements it but it is currently still not working correctly for (at least) the follow-up report (from account_followup) and the task report (from industry_fsm). This PR makes the DIN5008 layout work for both of the aforementioned reports. The new modules 'l10n_din5008_account_followup' and 'l10n_din5008_industry_fsm' are added as part of this fix. It also fixes some issues in case the DIN5008 format is not used. 1. The font-size of the salutation is too small. See comparison pictures in https://github.com/odoo/enterprise/pull/44908#issuecomment-1669461467 2. There is an unnecessary address below the document title https://github.com/odoo/enterprise/pull/44908#issuecomment-1669465457 Community PR: https://github.com/odoo/odoo/pull/130337 task-3394263 Forward-Port-Of: odoo/enterprise#45736 Forward-Port-Of: odoo/enterprise#44908
The tour testing css has been removed (see Community PR), so the override is useless now. Forward-Port-Of: odoo/enterprise#45740 Forward-Port-Of: odoo/enterprise#44977
Original PR description
The tour testing css has been removed (see Community PR), so the override is useless now. Forward-Port-Of: odoo/enterprise#45740 Forward-Port-Of: odoo/enterprise#44977
Before these commit when we create quotation and confirm it. we will not be able to see the cancel button on the form. Fix : When we install the bridge module sale_subscription the cancel button gets hide due to that we can't see the cancel button. After doing some changes in sale_subscription we will be able to see the cancel button on the form. task-3433526 Forward-Port-Of: odoo/enterprise#44623
Original PR description
Before these commit when we create quotation and confirm it. we will not be able to see the cancel button on the form. Fix : When we install the bridge module sale_subscription the cancel button gets hide due to that we can't see the cancel button. After doing some changes in sale_subscription we will be able to see the cancel button on the form. task-3433526 Forward-Port-Of: odoo/enterprise#44623
Issue: ------ The `note` field in the form view: Payroll > Configuration > Rule Categories > New does not use the full width of the form. opw-3451106 Forward-Port-Of: odoo/enterprise#45655 Forward-Port-Of: odoo/enterprise#45438
Original PR description
Issue: ------ The `note` field in the form view: Payroll > Configuration > Rule Categories > New does not use the full width of the form. opw-3451106 Forward-Port-Of: odoo/enterprise#45655 Forward-Port-Of: odoo/enterprise#45438
Since shop floor app. The mrp_workorder module is an auto install of mrp and not trigger by the setting of work orders anymore. Also the mrp_workorder contains now the shop floor application. The shop floor app doesn't require the workorder and could be use for simple use case with only production orders mrp_workorder should be rename mrp_enterprise in a future work. Currently since the workorders are not related to the module, we remove it from the demo data Forward-Port-Of: odoo/enterpr
Original PR description
Since shop floor app. The mrp_workorder module is an auto install of mrp and not trigger by the setting of work orders anymore. Also the mrp_workorder contains now the shop floor application. The shop floor app doesn't require the workorder and could be use for simple use case with only production orders mrp_workorder should be rename mrp_enterprise in a future work. Currently since the workorders are not related to the module, we remove it from the demo data Forward-Port-Of: odoo/enterprise#44492
Steps to reproduce: 1. Install l10n_co_edi 2. configure co localization: https://drive.google.com/file/d/10Y6rTEg14kOMXS_yqZfLrBhOFXM2d3y0/view 3. Create a Vendor Bill with any product, with an amount of "0.00" 4. traceback Issue: according to https://www.odoo.com/web#id=2985449&cids=1&menu_id=5879&action=333&active_id=5645&model=project.task&view_type=form it's not possible to have lines with "0" in invoices. It is also the same for `Doc soporte` Fix: create a validation error for
Original PR description
Steps to reproduce: 1. Install l10n_co_edi 2. configure co localization: https://drive.google.com/file/d/10Y6rTEg14kOMXS_yqZfLrBhOFXM2d3y0/view 3. Create a Vendor Bill with any product, with an amount of "0.00" 4. traceback Issue: according to https://www.odoo.com/web#id=2985449&cids=1&menu_id=5879&action=333&active_id=5645&model=project.task&view_type=form it's not possible to have lines with "0" in invoices. It is also the same for `Doc soporte` Fix: create a validation error for this case opw-3442071 Forward-Port-Of: odoo/enterprise#45168