Monday, September 25, 2023
6 changes · master
Enhancements to existing features
Point-of-sale users can now choose the display order of combo options instead of relying on the system's default ID order. This makes combo menus easier to organize and present in the intended sequence for staff and customers.
Original PR description
Prior to this commit the combo choices were displayed in their ID order. This commit add a sequence field that allows the user to choose the order of the combo choices.
Help Center menus are now handled so backend users can see them even when they are not published. Related website blog performance checks were adjusted to account for the additional page requests this can create.
Original PR description
This commit adapts website_blog tests to change in website_helpdesk. The method _compute_visible of model website.menu is modified to display help team menus to backend user, even if they are unpublished. This potentially add extra requests when rendering a website page. Therefore, the performance tests are adapted accordingly. task-3186564
User avatar fields are now only clickable when viewed in a form. This avoids unintended navigation from list-style screens and makes readonly views behave more predictably.
Original PR description
This commit changes the canOpen prop of the many2oneAvatar field to be set to true only when in form view. The field will therefore stop being a link in readonly when outside of form view.
Odoo Studio was updated to align with a core platform change in how record context is handled. This keeps editing related record views working reliably and avoids hidden dependencies on older internal behavior.
Original PR description
PR https://github.com/odoo/odoo/pull/135782 explicitly adds the "context" key into the
evalContext, whereas before the whole evalContex was considered as
being the context. Studio relied on that loophole to handle the
edition of x2many views, by adding a key "parent" in the context,
which could thus be accessed in expressions without doing
context.get("..."). This commit refactors the way Studio makes the
created datapoint aware of their parent record, without relying on
the context.
Moreover, with https://github.com/odoo/odoo/pull/135782, datapoints makes the assumption
that there's a context in their config, which wasn't the case for
the fake group created in Studio. We thus had to set it.This update removes unused log fields from subscription sales records. It simplifies the underlying data model, reducing clutter and making future maintenance easier without changing day-to-day user workflows.
Original PR description
taskid: 3274815
The Field Service task form now hides the Navigate button when no customer or partner is assigned. This prevents users from clicking an action that cannot work and avoids confusing invalid field errors.
Original PR description
In this commit, the functionality of the 'Navigate' button in the FSM task form has been improved. The 'Navigate to' button is now enhanced to better interact with the task. Specifically, the button is hidden when no partner is assigned to the task. This enhancement prevents the 'Navigate to' button from causing an 'invalid field' error when clicked, as it's not applicable in such cases. Task: 3460000