Payment forms now better keep the selected payment method aligned with the chosen journal. If the current method is no longer valid after changing the journal, Odoo automatically switches to an appropriate default or available method, reducing incorrect payment setup.

Task 2115472

Split from #40957

The register payment wizard now uses the invoices already available to it instead of re-reading the same records from the screen context. This makes journal selection more consistent with company defaults and reduces confusing behavior when registering payments.

It seems very strange that we'd want to use active_ids as invoices to
work with when when we already have invoices available, and these are
browsed / converted from the active_ids if they weren't provided
explicitly.

There's also an odd divergence between the filtering on the journal's
company here and in the default_get too: in the default_get we get a
journal in the user's company but then we only allow selecting a
journal from the invoices' company...

Task 2115472

Split from #40957

The website editor now has a cleaner way to decide which options and controls appear in the left panel. This helps reduce visual flicker and makes the editing experience more consistent while giving future improvements a simpler foundation.

This update adjusts how bank accounts are selected when preparing batch and SEPA payments. It supports a related change in the main accounting app, helping keep payment workflows consistent and reducing selection issues for users.

Cf odoo/odoo#41872

The Documents app now makes lock status easier to understand. Users can no longer try to unlock a document locked by someone else from the inspector, while list and kanban views use a simpler, consistent lock icon.

In the document inspector, the lock button is now
disabled if the document is locked by someone else.

In the Kanban and List view, the icon distinction
between a document locked by someone else or the
current user has been removed.

Task: #2155063

Mass mailing and SMS mailing setup fields now keep their values through stored editable computations instead of temporary form-change logic. This should preserve the same user experience while making mailing configuration more consistent, easier to maintain, and better covered by tests.

PURPOSE

Try to move from onchange / default_get to stored editable computed fields.
Normally behavior should be the same (computed or set by user), with support
in create / write + onchange without additional code.

SPECIFICATIONS

Update classic fields with onchange to stored editable computed fields. It
means their value will come either from manual user input, either computed
based on triggers. Purpose is to remove all onchange and default_get when
possible.

Clean fields definition inconsistencies, like default / required on computed
fields. Indeed computed fields should always have a value, maybe coming from
user input. They should not have default / required that are attributes for
classic fields.

Mailing domain computation is also cleaned and is now reset once the
mailing domain is changed. Indeed trying to keep a previous domain
based on try / except has no meaning from functional point of view. If model
changes then domain should change as it is a business record, not just a
technical domain to try to apply.


Finally add some tests to help develop and maintain those fields computation.

LINKS

Task ID 2088577
PR #41877
Enterprise PR odoo/enterprise#7278