Purpose:
- mail is now focused on messaging; partner document is now a classic document, without specific behavior; removed the concept of 'my followers' from mail;
- hr adds social features to mail: employee profile is used to display internal messages; employees can follow other employees, comment and react on their profile messages;
- display suggestion of Groups and Employees to follow in the Inbox, using a new widget. The purpose is to promote social interactions between employees and to improve the visibility of groups;
mail:
- add suggestions.Group widget that allows to display a list of suggested groups to follow; this widget is displayed in the Inbox;
- display 'Partner profile of' or 'News from' when reading messages from a partner profile / employee profile in the Inbox;
- 'Compose a new message or Write to my followers' is not present anymore when hr is not installed, because this social aspect comes with HR;
- mail_thread: add a search function on message_is_follower;
- mail_group: implement suggested groups behavior;
- res_partner: removed specific code changing message_post with type='email' to a private discussion between author and destination partner; partner document behaves like a classic document;
- res_users: add 'display_groups_suggestions' field that controls the display of suggested groups to follow;
- res_users: writing on a res.users object is considered as a private discussion; when Hr is not installed, only aliases should be able to post on a user;
hr_employee:
- when creating an employee, post a message on its profile and push it to every employees of the same company;
- add follow/unfollow and message and follower count on employee kanban view;
- implement suggested employee behavior;
- HR improves the basic Inbox by adding the 'Compose a new message or Write to my followers';
- allow to post on an employee profile when having read access right if the user that posts is an employee;
HR:
- add suggestions.Employee widget that allows to display a list of suggested employees to follow; this widget is displayed in the Inbox;
- res_users: add 'display_employees_suggestions' field that controls the display of suggested employees to follow;
- res_users: do not welcome new users anymore, welcome new employees instead
- res_users: incoming emails are still considered as private messages (using aliases); however messages posted on user profile are redirected to the related employee profiles (used for 'Write to my followers')
bzr revid: tde@openerp.com-20130612121258-j38do5opsot2ur7c
- [FIX] [IMP] mail_thread: allow to use message_post on models not having message_post method defined. mail_compose_message.send() wizard and mail_thread.message_process() now check that the active model has message_post defined. Otherwise using thread_model context key, it is possible to use mail_thread.message_post() while keeping model and res_id on the created mail_message.
- [FIX] [TESTS] mail_message, mail_mail: fixed reply_to and email_from default / specified values + added tests (mostly backported from trunk)
- [IMP] mail_message, mail_followers: _notify now have 2 new arguments force_send and user_signature. force_send allows to immediately send the notification emails. user_signature tells whether to add the author's signature in the notification emails sent.
- [FIX] mail_message: notified people: when having no subtype, just avoid notifying the followers but take into account specified recipients (partner_ids).
- [FIX] mail_mail: removed duplicate field email_from, as it is already defined on mail_message (mail_mail inherits from mail_message).
- [IMP] mail_mail: no need to search on type = email in list view.
- [FIX] email_template: allow to add a context action even without having create access on ir.values and ir.action by using SUPERUSER_ID.
- [FIX] mail_compose_message: support user_signature of template. Note that in case of multiple wizards (having ids), user_signature=False on one template is used for all wizards.
- [FIX] mass mailing: emails due to mass mailing are not queued instead of sent immediately.
- [IMP] Chatter: better display of recipients when having a message_post due to mass mailing (not always displaying logged a note).
bzr revid: tde@openerp.com-20130607101641-5h6z2707tu0f3i2n
mail.compose.message wizard and messaage_process now check that the active model
has message_post defined. Otherwise using thread_model context key that is better
managed in message_post, it is possible to use mail_thread.message_post() with a
thread_model and thread_id that should not allow message_post otherwise.
Hint: look for backport into 7.0
bzr revid: tde@openerp.com-20130606123230-d7ql14yydzfrlc7h
Mass mailing: emails due to mass mailing are not queued instead of sent immediately.
As most of cases go through mail_followers._notify(), a new argument is added that
allows to control the force_send (like what is done in email_template).
Chatter: better display of recipients when having a message_post due to mass mailing
(not always displaying logged a note).
Notified people: when having no subtype, just avoid notifying the followers but
take into account specified recipients (partner_ids).
bzr revid: tde@openerp.com-20130606102437-43s4xp96b5wa3r1q
Thibault Delavallée
Launchpad Translations on behalf of openerp
niv-openerp
DBR (OpenERP)
Christophe Matthieu
Martin Trigaux
Xavier Morel
Olivier Dony
Vo Minh Thu