Monday, March 25, 2024
6 changes · saas-17.2
Resolved issues and error corrections
This fix ensures selected client actions receive the information needed to keep the current record reflected in the browser address bar. It helps users maintain the right context when navigating import guidance and website generation screens.
Original PR description
Since [1], it's now possible for a client action to use the resId and update the resId on the URL as a form view will do. To do this two props are given to the client action: resId and updateResId. This commit adds the missing props to existing client actions that were forgotten by the initial commit. [1] https://github.com/odoo/odoo/commit/3ad4fd65387f60b524e5f786556963ead8ae9dfe
Duplicating read-only Sign templates now works without causing an error. This helps users reuse existing signing templates reliably instead of being blocked by a traceback.
Original PR description
Before this commit, when duplicating a read-only template a traceback was being triggered since we were passing a single template to the copy method. After this commit, we call the copy function passing a batch of a single element, which will return a list of templates containing a single template. After that, we call the action to open this copied template. task-3790206
This fix prevents the manufacturing Bill of Materials overview from failing when Odoo is used in debug mode. It also improves automated test coverage so this screen is checked more reliably in future updates.
Original PR description
In this [commit](https://github.com/odoo/odoo/commit/3ad4fd65387f60b524e5f786556963ead8ae9dfe#diff-552aefb62246b1f4fe6a2607ec8f0a01773e53de2d68293266b38bc99c5cb56dR569-R577), the updateResId has been added to the action props. This did not trigger any error as the props are not validated, except if in debug mode. Adding the standardActionServiceProps solves this problem. This bug highlighted another problem: the component does not appear in a tour. opw-3822623 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The recruitment job positions menu is now hidden from demo users and others who do not have the required recruitment permissions. This prevents confusing access errors when navigating employee recruitment settings and keeps menus aligned with user rights.
Original PR description
In https://github.com/odoo/odoo/pull/157014 we make the mark demo rightless. Rightfully so. That change exposed an issue. After that change click_all fails for mark demo. More specifically, when hr_recruitment is installed, now mark demo gets access error when clicking on Employees / Configuration / Recruitment / Job Positions. Indeed, the user that does not have at least group_hr_recruitment_interviewer rights should not be seeing the menuitem that leads to jobs. In this PR we blacklist the menuitem, unless the user has proper rights
Several Odoo app screens now receive the record information they need to keep the browser URL aligned with the item being viewed. This fixes a consistency issue introduced by an earlier change and helps users navigate or share links more reliably.
Original PR description
Since [1], it's now possible for a client action to use the resId and update the resId on the URL as a form view will do. To do this two props are given to the client action: resId and updateResId. This commit adds the missing props to existing client actions that were forgotten by the initial commit. [1] https://github.com/odoo/odoo/commit/3ad4fd65387f60b524e5f786556963ead8ae9dfe
This fix stops users from selecting certain custom grouping fields that cannot actually be used in reports or list views. It prevents confusing errors later by rejecting unsupported many-to-many fields earlier in the grouping process.
Original PR description
Since https://github.com/odoo/odoo/pull/127353, no-store many2many are considered as groupable (with the `_description_groupable` dry run). This means that users can select an ungroupable field in the custom group selector. Now raise a ValueError if the many2many is not stored in the `_read_group_groupby`.