Saturday, December 7, 2024
7 changes · saas-17.2
Miscellaneous changes
Steps to reproduce ================== - Open any form view - Drag and drop a new html field at the start of the form view => It goes to the bottom Cause of the issue ================== The generated xpath was `<xpath expr="//form[1]/sheet[1]" position="inside"/>` This puts the new element at the end of the sheet Solution ======== If we want to insert something at the start of the sheet, we need to put it before it's first child. If the sheet is empty, we can use inside like p
Original PR description
Steps to reproduce ================== - Open any form view - Drag and drop a new html field at the start of the form view => It goes to the bottom Cause of the issue ================== The generated xpath was `<xpath expr="//form[1]/sheet[1]" position="inside"/>` This puts the new element at the end of the sheet Solution ======== If we want to insert something at the start of the sheet, we need to put it before it's first child. If the sheet is empty, we can use inside like previously opw-4339407 Forward-Port-Of: odoo/enterprise#75276
- Created a new module `l10n_mt_pos` to provide a compliance letter required by Maltese businesses for requesting an EXO number. - Automatically installs for Malta by default. - Added a menu item under "Reporting" > "Compliance Letter" to allow users to download the document. Task ID: 4373339 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#189868 Forward-Port-Of: odoo/odoo#189640
Original PR description
- Created a new module `l10n_mt_pos` to provide a compliance letter required by Maltese businesses for requesting an EXO number. - Automatically installs for Malta by default. - Added a menu item under "Reporting" > "Compliance Letter" to allow users to download the document. Task ID: 4373339 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#189868 Forward-Port-Of: odoo/odoo#189640
This commit adds the E-invoicing app for Jordan. The E-invoicing is mandatory for businesses in Jordan as the end of May 2024. It is a backport of this PR: https://github.com/odoo/odoo/pull/182983 task-3895493 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#176625
Original PR description
This commit adds the E-invoicing app for Jordan. The E-invoicing is mandatory for businesses in Jordan as the end of May 2024. It is a backport of this PR: https://github.com/odoo/odoo/pull/182983 task-3895493 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#176625
Description of the issue/feature this PR addresses: When there is more than one mail.activity.schedule records created in a process, the function `_compute_plan_available_ids()` will face the error Expected singleton. Current behavior before PR: This issue will not happen when launching the activity plan on WUI because users open one launch plan wizard at a time. When activity plans need to launch simultaneously, we need to create a separate wizard for each plan, this process will caus
Original PR description
Description of the issue/feature this PR addresses: When there is more than one mail.activity.schedule records created in a process, the function `_compute_plan_available_ids()` will face the error Expected singleton. Current behavior before PR: This issue will not happen when launching the activity plan on WUI because users open one launch plan wizard at a time. When activity plans need to launch simultaneously, we need to create a separate wizard for each plan, this process will cause the issue. Desired behavior after PR is merged: The function `_compute_plan_available_ids()` will work properly. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#189843
Before this commit, since the addition of the dual stream feature in v17, starting the screen sharing while the blur was active or swapping from blur to unblur and back would cause a black camera screen. This commit fixes this issue by: 1) Not closing streams when removing them from a RTC session when those streams originate from the device (and not a remote session). 2) Removing the condition on the state, which was always false when attempting to recover an old stream. Forward-Port-Of
Original PR description
Before this commit, since the addition of the dual stream feature in v17, starting the screen sharing while the blur was active or swapping from blur to unblur and back would cause a black camera screen. This commit fixes this issue by: 1) Not closing streams when removing them from a RTC session when those streams originate from the device (and not a remote session). 2) Removing the condition on the state, which was always false when attempting to recover an old stream. Forward-Port-Of: odoo/odoo#189799
The `OpenMoveWidget` was usually called from an `account.move.line`, since https://github.com/odoo/enterprise/commit/6ec55979a79a959b0a7a784ceaa5cdc0b7854182 it is called from `account.move`. With this commit, by using `this.props.record.resModel`, we allow the model to be either `account.move` or `account.move.line`, any other models would raise an error as there is no `action_open_business_doc` defined in other models. Steps: - Install 'Accounting` - Create an asset with passed depreciation
Original PR description
The `OpenMoveWidget` was usually called from an `account.move.line`, since https://github.com/odoo/enterprise/commit/6ec55979a79a959b0a7a784ceaa5cdc0b7854182 it is called from `account.move`. With this commit, by using `this.props.record.resModel`, we allow the model to be either `account.move` or `account.move.line`, any other models would raise an error as there is no `action_open_business_doc` defined in other models. Steps: - Install 'Accounting` - Create an asset with passed depreciation entries and confirm it - Go to 'Depreciation Board' tab - Click on a posted entry name -> We land on an other move (in fact, move that have the line with the same id as the depreciation move) or an error (non existing record) opw-4357468 Forward-Port-Of: odoo/odoo#189861
…anges In previous commit [1], we made changes to handle better the invoicing address partner and the commercial partner. This broke facturx constraints. [1]: https://github.com/odoo/odoo/commit/053c6de8e48ff3fea469531cf32352d88111469e task-no Forward-Port-Of: odoo/odoo#189907
Original PR description
…anges In previous commit [1], we made changes to handle better the invoicing address partner and the commercial partner. This broke facturx constraints. [1]: https://github.com/odoo/odoo/commit/053c6de8e48ff3fea469531cf32352d88111469e task-no Forward-Port-Of: odoo/odoo#189907