Tuesday, February 2, 2021
9 changes · master
Enhancements to existing features
Monetary changes shown in record messages now include the relevant currency symbol, making updates such as revenue changes easier to understand at a glance. CRM recurring revenue tracking is also aligned with expected revenue tracking, improving visibility into commercial changes.
Original PR description
# Purpose Add the currency symbol in the message for the monetary tracking field. For example, if we have a record with a monetary field displaying "$ 500". If we modify the currency and the value to…
# Purpose Add the currency symbol in the message for the monetary tracking field. For example, if we have a record with a monetary field displaying "$ 500". If we modify the currency and the value to have "450 €", the message containing the tracking values will display: "500 € -> 450 €". # Specifications Add the currency symbol for the monetary tracking field to better represent the change of a monetary field. The currency will be fetch from the currency defined in the monetary field or on the record's company in case there is not. We only use one field to track the currency of a monetary field. Indeed, in the case where the currency is changed with the value of a monetary field, only the new currency is tracked. We focus on the fact that the more important thing is the new value. Furthermore, when modifying a currency of a monetary field, the user can already see the new currency before saving the changes. This allows him to adapt the value of the field if he needs it. (N.B. we assume that this case will happen very rarely) Using only one field takes also into account that there are millions of record for this model and adding a new field would take a lot of memory. task-2387268 odoo/upgrade#2060
Accounting chart templates can now be linked to the countries they apply to, helping Odoo choose the right accounting setup for each company. The update also supports more limited accounting data imports, making setup and localization handling more precise.
Sales users can now access the CRM Reporting menu according to their permission level. Additional access rules ensure users only see reporting data they are authorized to view, including partnership and lead generation information.
Original PR description
The purpose of the task is to let users of all access right levels access their reporting, and to make sure that it does not give them access to the data that does not match their access rights. After applying this commit all crm user can access reporting menu, the only difference being the records that they can or not access. **TaskId - 2357311** -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
CRM now asks users to confirm before updating lead and opportunity probabilities from settings. This prevents accidental bulk updates and gives users a chance to review or cancel the action before it runs.
Original PR description
PURPOSE
In CRM setting menu when we click on update, it should ask confirm or cancel, because a user can click button by mistake.
SPECIFICATIONS
Current
When we click button it updates probability directly.
To be
On click on the "update proba" button, display a modal with the following info:
Title: Update Probabilities
Body: Confirm to update the probabilities of all the Leads/Opportunities created since StartDate. This can take up to several minutes depending on the number of Leads/Opportunities you have.
Buttons: Confirm (primary), Cancel (secondary)
LINKS
PR
Task 2355562
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prWhen someone tries to create an email alias that already exists, Odoo now explains where that alias is already being used. This helps users quickly identify the related document or system use and decide whether to choose a different alias or update the existing one.
Original PR description
Purpose Current: When I try to create a new alias with an already used prefix, I'm greeted by a message telling me: The e-mail alias is already used. Please enter another one." Which does not help much because I do no know who, where, when, why (another Sales team? HR and their job positions? Accounting? Documents? Helpdesk? Maintenance?). Specifications Change the "the e-mail alias is already used. Please enter another one." error message into: "The e-mail alias prefix@mycompany.odoo.com is already used by the ParentDocumentName alias_parent_model_id.name. Choose another alias or change it on the other document." e.g. "The e-mail alias prefix@mycompany.odoo.com is already used by the Benelux Sales Team. Choose another alias or change it on the other document." PR #62367 task-id: 2375552 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo Studio users can now create custom stat buttons using both many-to-one and many-to-many relationship fields. This gives businesses more flexibility when building dashboards and shortcuts without custom development.
Original PR description
Currently, when creating a custom stat button through studio, the user can only set it up by selecting a many2one field. in this commit, when creating a custom stat button through studio, is able to select many2one as well as many2many . TaskId: 2349284
Resolved issues and error corrections
List view buttons now ignore rapid repeat clicks for a short moment after the first click. This helps prevent accidental duplicate actions, such as sending the same email twice, improving reliability for everyday users.
Original PR description
PURPOSE
It aims at prevent the following use case:
A user double clicks on a 'send email' listview button and sends the email twice.
Listview buttons should be disabled on click until the action is resolved (i.e. longer than the time it takes to double click)
SPEC
When clicking on a button in listview, disable the clicked button until the action is resolved/done.
NB: do not disable the whole row or list, but just the clicked button
TASK 2391298
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prOriginal PR description
Task link: https://www.odoo.com/web#id=2252801&model=project.task&view_type=form&cids=1&menu_id=
Installing the Newsletter Popup from the website editor now includes the required anti-spam component, preventing the popup from failing after a newsletter is selected. This restores the expected setup flow for website newsletter signups and avoids confusion for users configuring campaigns.
Original PR description
When we "Install Newsletter Popup" from website editor
(which installs the 'mass_mailing' app), the snippet popup
doesn't open after setting a Newsletter.
This is because the code at 'website_mass_mailing' module
which has the following config:
'depends': ['website', 'mass_mailing'],
'auto_install': True,
Requires 'google_recaptcha.ReCaptchaV3' while 'google_recaptcha'
module is not installed.
The goal of this PR is to fix this issue by setting
'google_recaptcha' as a dependency for the 'mass_mailing' module.
task-2312878
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-prSocial Marketing users who do not have access to marketing campaign features will no longer see the Campaigns menu. This prevents users from opening menus they cannot use and avoids confusing access errors.
Original PR description
User has only the access rights for social manager and, no access rights for email marketing, marketing automation and sms marketing, is still able to see the campaigns menu similarly this issue is for social manager rights. Which leads to record rule error. This commit will solve that issue, i.e. the campaigns menu will not shown if user dont have access rights regarding that menu. **TaskID - 2417993**