diff options
| author | Thibault Delavallée <tde@odoo.com> | 2020-11-19 11:24:58 +0000 |
|---|---|---|
| committer | Thibault Delavallée <tde@odoo.com> | 2020-11-23 13:41:15 +0000 |
| commit | 7fbeda3f7d92fa501c2752c873be2255697f5d97 (patch) | |
| tree | e58606ed73953b396b1d8279950d59f9698f8660 /doc/python3.rst | |
| parent | 3fe5416f07e76ccca6c0bb05a6fa12d8e2ca0e6c (diff) | |
[FIX] crm_livechat: do not set public user partner as lead customer usign /lead command
When chatting with visitors, operator may use /lead command to directly create
a lead from discussion. That way commercial discussion can follow visitors
inquiries.
Anonymous (public) users may be part of channels, notably since f5fe11cf1e74216afea7976d8515d4448f054dd2.
In that case we don't want new leads to be associated with those users. Indeed
* they are not real users, just technical users for website / frontend;
* merge processes may think all leads having public users as customer are
duplicates and should be merged, which means loosing information and
leads;
We therefore set the following heuristics
* if a public user is member of a channel -> consider this is a livechat
with an anonymous and set customer_id to False;
* otherwise try to find a share partner in channel members and link the lead
to that partner;
Task ID-2389564
closes odoo/odoo#62006
Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
Diffstat (limited to 'doc/python3.rst')
0 files changed, 0 insertions, 0 deletions
