Odoo/addons/crm/views/res_config_settings_views.xml, branch 14.0 The current checkout of upstream Odoo [FIX] *: update documentation links Following the recent reorganisation of the documentation in 12.0+, the majority of the documents have been moved and their old links are no longer valid. Some redirection rules will soon be deployed, but those rules might be dropped in some years and we want the links to still work, which is why we still replace the links to the new ones. 2021-05-17T08:25:31+00:00 Victor Feyens vfe@odoo.com 2021-05-12T14:07:43+00:00 598dda32f48ffeb64cbd398c6ffb1fe7577468f2 FW-Port of odoo/odoo#70675 (13.0) closes odoo/odoo#70728 X-original-commit: 85c24961ab9ff5c1c79eb7415c97c46d9a77cca3 Related: odoo/enterprise#18283 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com> 
FW-Port of odoo/odoo#70675 (13.0)

closes odoo/odoo#70728

X-original-commit: 85c24961ab9ff5c1c79eb7415c97c46d9a77cca3
Related: odoo/enterprise#18283
Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com>
[FIX] crm: change default 'crm_alias_prefix' to 'contact' 2020-11-06T07:23:14+00:00 Aurélien Warnon awa@odoo.com 2020-11-03T08:37:40+00:00 31497e17e2369147fa40ab8b3f82cb2602ec9012 This commit changes the default crm alias prefix from 'info' to 'contact'. As the alias of the default sales team is configured to 'info', also having 'info' for the "crm_alias_prefix" setting was leading to an alias collision. This change allows an easier configuration by the end user and avoids confusion when first playing with your CRM settings. Task 2373095 closes odoo/odoo#61025 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com> 
This commit changes the default crm alias prefix from 'info' to 'contact'.

As the alias of the default sales team is configured to 'info', also having
'info' for the "crm_alias_prefix" setting was leading to an alias collision.

This change allows an easier configuration by the end user and avoids confusion
when first playing with your CRM settings.

Task 2373095

closes odoo/odoo#61025

Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
[FIX] *: fix image parsing error on saving res config 2020-11-02T17:40:06+00:00 IEL iel@odoo.com 2020-10-30T11:07:14+00:00 bade0ba9b2021c4fae799752328721ec4dad59df WHAT: apply 93a7695f65baf00d1f82481d6a2a97e6c11940a8 for all res.config.settings menus WHY: the same reason as in 93a7695f65baf00d1f82481d6a2a97e6c11940a8: When saving, a read is called. By default, read has bin_size to true to avoid performances issues. It will return the image size instead of the content it may lead to image dissapearing or "Incorrect padding" error HOW: find . -iname "*.xml"|xargs grep "\"context\".*'module'" -l | xargs sed -i "s/\(\"context\".*'module'.*\)\}/\1, 'bin_size': False}/" git checkout -- addons/base_setup/views/res_config_settings_views.xml --- PR for General Settings: https://github.com/odoo/odoo/pull/47297 opw-2346644 closes odoo/odoo#61212 X-original-commit: 7c55efa88b72bd1f3f0f32f7f738e2fda5aa4abd Related: odoo/enterprise#14545 Signed-off-by: Ivan Yelizariev // IEL <yelizariev@users.noreply.github.com> 
WHAT: apply 93a7695f65baf00d1f82481d6a2a97e6c11940a8 for all res.config.settings
menus

WHY: the same reason as in 93a7695f65baf00d1f82481d6a2a97e6c11940a8:

	When saving, a read is called. By default, read has
	bin_size to true to avoid performances issues.
	It will return the image size instead of the content

it may lead to image dissapearing or "Incorrect padding" error

HOW:

    find . -iname "*.xml"|xargs grep "\"context\".*'module'" -l | xargs sed -i "s/\(\"context\".*'module'.*\)\}/\1, 'bin_size': False}/"
    git checkout  -- addons/base_setup/views/res_config_settings_views.xml

---

PR for General Settings: https://github.com/odoo/odoo/pull/47297

opw-2346644

closes odoo/odoo#61212

X-original-commit: 7c55efa88b72bd1f3f0f32f7f738e2fda5aa4abd
Related: odoo/enterprise#14545
Signed-off-by: Ivan Yelizariev // IEL <yelizariev@users.noreply.github.com>
[IMP] crm : improve crm settings usability 2020-10-27T04:47:35+00:00 Dharmraj Jhala dja@odoo.com 2020-10-26T06:42:52+00:00 55b05ed5e2cf083ac1e6d807d59e5533f4fb94b6 This commit fixes few of the strings / layout for the settings related to CRM and makes it less technical and thus more understandable and also updates the required translation strings. TaskID - 2351582 closes odoo/odoo#60687 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com> 
This commit fixes few of the strings / layout for the settings related
to CRM and makes it less technical and thus more understandable and
also updates the required translation strings.

TaskID - 2351582

closes odoo/odoo#60687

Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
[FIX] *: update document links 2020-10-19T05:24:27+00:00 Swapnesh Shah swapneshshah111@gmail.com 2020-10-15T18:37:53+00:00 7ac08486d91d0ff0151abeeda057ffa6beda72e8 Before this commit, links to the documentation were referenced the previous version, 13.0, instead of the current one, 14.0. Eventhough there is a redirection done by NGINX of a "versionless" URL to the latest one (e.g. /documentation/user/general/auth/google.html -> /documentation/user/14.0/general/auth/google.html as of today), the goal is to keep links owrking for users that will still be using the 14.0 in three years (and should not endup on the 17.0 doc). closes odoo/odoo#59554 Signed-off-by: Martin Trigaux (mat) <mat@odoo.com> 
Before this commit, links to the documentation were referenced the
previous version, 13.0, instead of the current one, 14.0.

Eventhough there is a redirection done by NGINX of a "versionless" URL
to the latest one (e.g. /documentation/user/general/auth/google.html
-> /documentation/user/14.0/general/auth/google.html as of today), the
goal is to keep links owrking for users that will still be using the
14.0 in three years (and should not endup on the 17.0 doc).

closes odoo/odoo#59554

Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
[FIX] crm: fix mail extension module documentation URL 2020-10-08T09:43:34+00:00 Aurélien Warnon awa@odoo.com 2020-10-08T09:38:46+00:00 3968cfebfabcf34f800203d880c4a719c0f1174c The URL to the mail extension module documentation in the settings view is currently wrong. It only works temporarily because of a redirect we setup on our website. This commit updates the URL to the proper location of the documentation. When we later support Gmail, the view will have to be updated to contain two documentation links: one to Outlook and one to Gmail. Task 2356910 closes odoo/odoo#59481 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com> 
The URL to the mail extension module documentation in the settings view is
currently wrong.
It only works temporarily because of a redirect we setup on our website.

This commit updates the URL to the proper location of the documentation.

When we later support Gmail, the view will have to be updated to contain two
documentation links: one to Outlook and one to Gmail.

Task 2356910

closes odoo/odoo#59481

Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
[IMP] crm: Disable pls cron and autoincrement frequencies when won/lost 2020-09-14T14:26:19+00:00 David Beguin dbe@odoo.com 2020-05-11T10:36:26+00:00 cd291b79eb2d2df80899867263ec71438ab8fe87 Purpose ======= Get rid of the cron. Always have an up to date frequency table to compute lead probability. Clean PLS code and ensure to remove unnecessary code Specifications ============== Disable the cron: - Increment won and lost count for lead PLS params from frequency table at each won/lost - The complete set of leads won't be recomputed anymore every day - A lead probability will only be recomputed if one of the PLS parameter will be modified (stage_id, team_id + the ones checked in settings) - No more onboarding phase : as frequency table is always up to date and only the modified leads are recomputed, we can drop this. (So even on onboarding, winning or losing a lead won't impact other leads, except the ones we modify manually afterwards) - Add an button to force the recompute of all the lead probabilities (kind of reset) in the settings. The cron has been disabled by default. Users can know choose to reactivate it if they want to continue updating their lead probabilities on a daily basis. Code have been reorganised for better structure and understanding. Some code parts have been factorised to be usable in both Live Increment and Full Rebuild mode. In this commit, we also update probabilities using only computes Before this commit, _update_probability was called during write and create, to ensure both probability and automated_probability were correct. That was necessary because of onchanges and readonly field (automated_probability was not given to the write method while saving after a change on the lead). After this commit, we use the force_save tag on the readonly field automated_probability. So we ensure that write always receives the new automated_probability value and everything can be handled directly by the compute. Also, we force the lead to start in automated probability mode. So when creating a new lead, both probability and automated probability are computed and aligned. Finally, when winning a lead, we ensure that both probabilities are aligned (=100), so that if user take the lead back to a previous stage, the probabilities are correctly recomputed, and the lead will not be stuck to 100%. Also, this commit applies some fix and minor changes listed here under: - Ensure to have always positive frequencies - Fix lost counts for team not set in pls computation - optimise set_won : write only once per values Finally, include tag in frequency table even if less than 50 occurences: Due to refactoring in which we increment frequency table at each won/lost instead of rebuilding the frequency table each day, the tags are never added in frequency table. This is due to the 50 occurence conditions that avoid to create the frequency if we have less than 50 won or lost for a tag. After this commit, we include the tag_ids in the frequency table, no matter the number of occurences. But, during the PLS computation, we skip the tag frequencies if the number of occurences for this tag is under 50. This allows to have a complete vision on the tag frequencies, even for small number of occurences. Task ID : 2254543 
Purpose
=======

Get rid of the cron.
Always have an up to date frequency table to compute lead probability.
Clean PLS code and ensure to remove unnecessary code

Specifications
==============

Disable the cron:
- Increment won and lost count for lead PLS params from frequency table at
  each won/lost
- The complete set of leads won't be recomputed anymore every day
- A lead probability will only be recomputed if one of the PLS parameter will
  be modified (stage_id, team_id + the ones checked in settings)
- No more onboarding phase : as frequency table is always up to date and only
  the modified leads are recomputed, we can drop this. (So even on onboarding,
  winning or losing a lead won't impact other leads, except the ones we modify
  manually afterwards)
- Add an button to force the recompute of all the lead probabilities
  (kind of reset) in the settings.

The cron has been disabled by default.
Users can know choose to reactivate it if they want to continue updating their
lead probabilities on a daily basis.

Code have been reorganised for better structure and understanding.
Some code parts have been factorised to be usable in both Live Increment and
Full Rebuild mode.

In this commit, we also update probabilities using only computes

Before this commit, _update_probability was called during write and create,
to ensure both probability and automated_probability were correct. That was
necessary because of onchanges and readonly field (automated_probability
was not given to the write method while saving after a change on the lead).

After this commit, we use the force_save tag on the readonly field
automated_probability. So we ensure that write always receives the new
automated_probability value and everything can be handled directly by the
compute. Also, we force the lead to start in automated probability mode.
So when creating a new lead, both probability and automated probability are
computed and aligned.
Finally, when winning a lead, we ensure that both probabilities are aligned
(=100), so that if user take the lead back to a previous stage, the
probabilities are correctly recomputed, and the lead will not be stuck to
100%.

Also, this commit applies some fix and minor changes listed here under:
- Ensure to have always positive frequencies
- Fix lost counts for team not set in pls computation
- optimise set_won : write only once per values

Finally, include tag in frequency table even if less than 50 occurences:

Due to refactoring in which we increment frequency table at each won/lost
instead of rebuilding the frequency table each day, the tags are never added
in frequency table.
This is due to the 50 occurence conditions that avoid to create the frequency
if we have less than 50 won or lost for a tag.

After this commit, we include the tag_ids in the frequency table, no matter
the number of occurences. But, during the PLS computation, we skip the tag
frequencies if the number of occurences for this tag is under 50.
This allows to have a complete vision on the tag frequencies, even for
small number of occurences.

Task ID : 2254543
 [ADD] mail_client_extension 2020-08-21T14:47:37+00:00 Florimond Husquinet (fhu) fhu@odoo.com 2020-02-03T09:40:06+00:00 c317232223460ba659feb27e9d48a60d3f5ffc25 This module provide routes to manage people, companies, and leads from the outlook add-on. It could eventually be accessed by add-ons for other mail clients. closes odoo/odoo#44936 Signed-off-by: Xavier Morel (xmo) <xmo@odoo.com> 
This module provide routes to manage people, companies, and
leads from the outlook add-on. It could eventually be accessed by
add-ons for other mail clients.

closes odoo/odoo#44936

Signed-off-by: Xavier Morel (xmo) <xmo@odoo.com>
[IMP] crm: add recurring revenues feature 2020-08-14T12:59:30+00:00 Patrick Hoste pko@odoo.com 2020-07-06T15:07:33+00:00 a54f3852d612e4bd9341713680b1228570c27051 PURPOSE Allow users to configure contract recurrences and Monthly Recurring Revenues on Opportunities they're trying to close. One short revenues are not sufficient to cover real life use cases of CRM revenu analysis. SPECIFICATIONS Adds an option in the settings to activate the recurring revenue feature. This feature is set on an opportunity to indicate a revenue that could be perceived over time. This time indicator is set by the crm.recurring.plan model in which the number of months is determined. By default some plans are added in data. When using plans, revenues are computed across the plan months. LINKS Task ID-2283052 odoo/odoo#54194 odoo/enterprise#12423 odoo/upgrade#1463 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com> 
PURPOSE

Allow users to configure contract recurrences and Monthly Recurring Revenues
on Opportunities they're trying to close. One short revenues are not sufficient
to cover real life use cases of CRM revenu analysis.

SPECIFICATIONS

Adds an option in the settings to activate the recurring revenue feature.
This feature is set on an opportunity to indicate a revenue that could be
perceived over time. This time indicator is set by the crm.recurring.plan
model in which the number of months is determined.

By default some plans are added in data. When using plans, revenues are
computed across the plan months.

LINKS

Task ID-2283052
odoo/odoo#54194
odoo/enterprise#12423
odoo/upgrade#1463

Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
[IMP] crm: lint data and menu entries 2020-04-14T11:52:46+00:00 Thibault Delavallée tde@odoo.com 2020-04-06T08:19:53+00:00 bc86d8c57da74ec9abe21091953e5e8e279e4b2c PURPOSE Prepare enhancements of sales team membership. SPECIFICATIONS Lint crm data and demo, notably about sales team and file organization. Also move crm menu entries declaration in a single file and remove some menu entries not imported anymore. LINKS Task ID 2086889 (sales team enhancements) Task ID 2234698 (preparation lint) Community PR odoo/odoo#49520 
PURPOSE

Prepare enhancements of sales team membership.

SPECIFICATIONS

Lint crm data and demo, notably about sales team and file organization.
Also move crm menu entries declaration in a single file and remove some
menu entries not imported anymore.

LINKS

Task ID 2086889 (sales team enhancements)
Task ID 2234698 (preparation lint)
Community PR odoo/odoo#49520