Use uuid4 instead of uuid1 to get 128 bits of entropy.
Rename database.uuid.private to the more meaningful database.secret as it
explains the usage instead of the technical details to generate it. And we
might switch to a longer string with more entropy in the future.
This string can be used to sign cookies or token with
sign(src) -> (src, hash(src + secret))
check(msg) -> msg[1] == hash(msg[0] + secret)
Review kanban to have only create by default without the search view
Rename model leads_dry_run into crm_leads_dry_run
Fix bug when toggle the running field on kanban was done before save
Remove useless link Assign now and Dry Run
Add dry run action_server in team.user more context
Fix kanban:
Move invisible user_id field outside the kanban-box.
Since jQuery migration (1.8 -> 1.11), the function append has not the same behavior.
$([undefined]).append() will crash, so when Odoo whas trying to render the user_ids m2m field in kanban, that crashs.
Anyway, moving the code outside this kanban-box, will avoid to render an invisible m2m_tag.
Misc:
Escape html
concat with %s
crm_lead:
overwritte create and write from crm_lead to force assign_date to be computed according to the field user_id is updated.
Else when the assignation was done manually, this field was not updated and so the lead not added in the instant pipe from the saleman (section_user)
sales_team:
Add context when assignation is done by cron to avoid to spam the sales. Notification of assignation will be only done via a log on the lead/opportunity.
Don't force to write assign date since write of crm_lead is overwritted to do it
Misc improve - check that leads exists before to make useless call to browse/write on nothing
Move section_user before the use of this one in a many2many, else demo data are not installable because field id is never created in db. (same 'issue' that https://github.com/odoo/odoo/issues/2386)
Add a cron to compute score each hours
Add merge pageview and merge (clean) score when we merge opportunities via merge_opportunities/merge_dependencies
Score the lead after the assignation to salesteam. Because when we assign to salesteam, sometimes we call the method merge_opportunities which one delete old scores on this lead, all score rules needs to be recomputed since the fields have been updated. So we compute now the score not at starting, but between assignation to salesteam and salesman.
Antony Lesuisse