Monday, February 1, 2021
10 changes · master
Enhancements to existing features
Accounting users can now more easily tell whether a journal entry is connected to a payment or a bank statement line. New smart buttons and improved navigation help users open the related payment or bank statement directly, reducing confusion during bank and cash review.
Original PR description
Increase the distinction between a journal entry linked to a bank statement line and another one linked to a payment by adding a smart button linked to them. Also, improve the navigation from the Bank And Cash view to directly open the linked bank statement line or payment. Task id #2448618 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
User login names are now handled in lowercase, so people can sign in even if they type uppercase letters in their email or username. This reduces failed login attempts and makes access more intuitive for customers and other users.
Original PR description
Description of the issue/feature this PR addresses: - create a e-commerce website used by your grand mother or your grand father (for exemple :-) ) - create a user with this login many@gmail.com - try to connect with MANY@GMAIL.COM --> Issues it doesn't work For better experience it should be logical that login is insensitive. @odony https://github.com/odoo/odoo/pull/24517 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
New Odoo databases can now automatically fill in missing company details using the partner autocomplete service, based on the company email or website. This improves the first-use experience by making company records look more complete without overwriting existing user-entered information, except for the logo.
Original PR description
In order to make a wow effect right after DB install we enrich the base company based on the given email address or company website at install. In order to achieve that goal we use the…
In order to make a wow effect right after DB install we enrich the base
company based on the given email address or company website at install.
In order to achieve that goal we use the partner_autocomplete service from
IAP. It uses free credits that are offered to new clients on saas platform.
Only the fields that are not filled yet are enriched to avoid erasing user
entered data, except logo. Indeed as partner_autocomplete is probably installed
as a core app (mail -> iap -> partner_autocomplete auto install chain) it is
unlikely that people already updated their company logo.
We consider that having a call to IAP consuming a token is ok for a standard
use case, especially that
* if no iap service is configured call to IAP won't add much timing;
* on Odoo SaaS free credits are given and company is enriched;
* on custom SaaS with custom iap service, at db creation probably no
credits are given and call will simply give no results back;
We decided to call IAP asynchronously at client web load. Session combined to
a boolean field on company model allows to do this call only once per company.
Doing this allows to avoid adding yet another post init hook. It also eases
behavior tweak through inheritance.
This call is limited to admin for obvious security reasons as well as
performance reason (limiting calls to external providers). As call will be
done once per company generally admin is the first person to log into the
its newly created Odoo.
In addition to enriching companies on the fly, we also enrich companies
when creating them. It allows to have an enrich on companies existing
before using autocomplete, and have results of enrich directly at create
for companies created after installing this module.
LINKS
Task ID-2322455
PR odoo/odoo#64600
PR odoo/upgrade#2086
Co-Authored-By: David Beguin <dbe@odoo.com>
Co-Authored-By: Thibault Delavallee <tde@odoo.com>Online store product search snippets can now show customer ratings and allow sorting or filtering by rating. Rating totals and averages are stored for faster browsing and more reliable ordering, helping shoppers compare products more easily.
Original PR description
The search product snippet can now display the rating of the products. task-1961400
Event teams can now choose whether each event tag category is visible as a filter on the website event page. This lets businesses keep internal tags for reporting and organization without exposing them to website visitors.
Original PR description
PURPOSE Allow users to use event tags both externally (filter on the /event page) as well as internally [NDLR: which is considered the "advanced mode"] (reports, filters, o-spreadsheets, ...). SPECIFICATIONS Current User cannot decide the filter by tag category on website should be shown. To be Add a boolean field on event tag categories. Default value is TRUE. If true, the category is shown on event page in header in website If false... Well, hide it! LINKS PR Task: 2300230 I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Financial reports now use a more consistent way to identify and manage report lines, aligning them with the accounting report framework. This should make future report improvements easier and help reduce inconsistencies across accounting reports without changing day-to-day workflows.
Original PR description
This also opens the doors to further refactoring of the caret options, once the existing account.report instances have all been converted to account.account.report. Task 2347659
The Social app settings menu is now hidden unless debug mode is enabled, keeping advanced demo-related options out of the regular user interface. The demo option wording was clarified so users understand it requires demo data to be active before it can work.
Original PR description
Purpose ======= We want to hide the settings menu in non-debug mode so the option "Demo Module" is considered as an advanced feature. Reword the option "enable demo", so the users know that they need the demo data to be activated to make the option work. Task 2253851
Accounting users can now more easily tell whether a journal entry comes from a payment or a bank statement line. New direct navigation helps users open the related payment or bank statement from Bank and Cash views, reducing confusion and saving time during reconciliation or review.
Original PR description
Increase the distinction between a journal entry linked to a bank statement line and another one linked to a payment by adding a smart button linked to them. Also, improve the navigation from the Bank And Cash view to directly open the linked bank statement line or payment. Task id #2448618
Outbound payments now appear as negative amounts in the batch payment view. This makes the displayed total more accurate by reducing the total when money is going out, helping users understand the net payment position at a glance.
Original PR description
In batch payment view : - show payments amount as negative when payment is outbound - "Total" must also reflect this (negative amount decrease total) Task: 2429361
Batch payment views now show outbound payment amounts as negative values. This makes totals easier to understand because outgoing payments reduce the displayed total instead of increasing it.
Original PR description
In batch payment view : - show payments amount as negative when payment is outbound - "Total" must also reflect this (negative amount decrease total) Task: 2429361