Thursday, February 18, 2021
4 changes · master
Enhancements to existing features
Odoo's LDAP login configuration can now check the same login against multiple directory fields, such as email address and user ID. This gives companies more flexibility in how employees sign in and avoids errors when using multi-field LDAP filters.
Original PR description
### Description of the issue/feature this PR addresses: This patch allows to match login on several LDAP attributes. This is very useful if you want to login either against an email or an uid. Then you can use a filter such as: ``` (|(mail=%s)(uid=%s)) ``` ### Current behavior before PR: A filter like `(|(mail=%s)(uid=%s))` raises a `TypeError` ### Desired behavior after PR is merged: A filter like `(|(mail=%s)(uid=%s))` is usable. Closes #25502 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The portal grant access wizard now lets users grant, revoke, or resend invitations for each partner individually. This makes access administration clearer and safer, while preserving user preferences when portal access is temporarily revoked and later restored.
Original PR description
Purpose ======= Improve the "grant access wizard" usability, allow to re-invite the partners and grant / access per partner and not in batch. Specifications ============== Add 3 buttons to grant / revoke the access and to re-invite the partner. When the partner has an internal user linked, do not allow to manage him in the view (disable the button) because we do not want to remove the "internal user group" in the wizard, but only the "portal user group". Task 2381921
Products marked as subscriptions must now have a subscription template selected before they can be saved. This helps prevent incomplete subscription product setup and reduces configuration errors during sales operations.
Original PR description
### Summary When creating a product with subscription, it was possible to leave the subscription template field unselected. This PR makes the subscription template field required when the product is set as subscription. Task ID: 2392038
Resolved issues and error corrections
The forecast report now uses stock values only for the selected warehouse's company. This prevents errors when businesses manage inventory across companies that use different currencies.
Original PR description
Before this commit, the SVL domain wasn't correctly set. So we got back SVL for all companies, which can lead to an error if the companies use different currencies. How to reproduce: - Create a new company with a different currency than the existing one; - For a product, define a cost and add some qty. on hand for the two companies; - Display the Forecast Report for this product -> traceback. To fix that, we use `product.product` `value_svl` field instead of recomputing the value from the SVL and we do that only for the current selected warehouse's company, so we deal with only one currency at the time.