Skip to Content
This question has been flagged
developmentmessageaddonv7
5 Replies
54372 Rodiniai
Portretas
Allison

I am trying to set up some notifications in an addon that go directly to a specified user's OpenERP inbox. I was able to post a message to one of the document streams but I need to send a message to a user's inbox.

The following code adds a message to a (hardcoded) user's document (Sales > Customers, remove filter) message stream and not their inbox:

user = self.pool.get("res.users").browse(cr, uid, 1)
user.message_post(context=context, body="Hi, this message is showing up in the wrong place")

Does anyone have pointers to get my message to go to the right place?

Portretas
Atmesti
Portretas
Allison
Autorius Best Answer

I have figured it out on a very basic level; I am able to send messages based on partner ID (not on user ID).

post_vars = {'subject': "Message subject",
             'body': "Message body",
             'partner_ids': [(4, 3)],} # Where "4" adds the ID to the list 
                                       # of followers and "3" is the partner ID 
thread_pool = self.pool.get('mail.thread')
thread_pool.message_post(
        cr, uid, False,
        type="notification",
        subtype="mt_comment",
        context=context,
        **post_vars)

I'm still getting my feet wet with OpenERP development so I can't explain this code as thoroughly as I would like - any help with that would be appreciated!

Portretas
Atmesti
Yannick Payot

What needs to be known is that a user is a partner, res.users inherit of res.partner.

Yannick Payot

What you do here is using the message_post method which will call create method of mail.message object.

You could make this call on any model which inherit from mail_thread. However, in your case, as you don't define thread_id, your message won't be attached to any model.

Yannick Payot

When passing arguments to create a mail.message, you have to use the strange notation for m2m to assign partners to your message. And if you look in mail.message, the field partner_ids is for Recipients.

Yannick Payot

I see that mail.message has type 'notification' this might be better than 'comment'

Thibault Delavallee (tde)

Two things here : 1/ active_model_pool.message_post(cr, uid, thread_id, ...) posts a new message on the record given by thread_id in active_model_pool; all followers will be notified 2/ specifying partner_ids pushes a notification (on the Inbox and by email, according to its preferences) to some specific partners

Yannick Payot

I edited the python style plus used 'notification' instead of 'comment'

Vinod Kumar

Hello sir i have created message as you mentioned like that but i want to send message with record id if i click that id it should transfer control to that particular record like sales order confirmation message please how can i do it

Portretas
Ethan Furman
Best Answer

Thanks, Allison. Using your work I was able to figure out a few more details.

First, the model should inherit from mail_thread:

class some_table(osv.Model):
    _inherit = ['mail.thread']

Then, when you want to post a message that only goes to the current discussion:

self.message_post(cr, uid, ids, body=body, context=context)

and if you want the message notification to go to all followers:

records = self._get_followers(cr, uid, ids, None, None, context=context)
followers = records[ids[0]]['message_follower_ids']
self.message_post(cr, uid, ids, body=body,
        subtype='mt_comment',
        partner_ids=followers,
        context=context)

The value for partner_ids can be one of:

  • [(4, id), (4, id), (...)]
  • [(6, 0, (id1, id2, id3), (...)]
  • (id1, id2, id3, id4)

or some combination thereof.

Portretas
Atmesti
Portretas
Yannick Payot
Best Answer

Here, I'm creating a notification for 3 partners (let's suppose they are users)

/!\ Warning this isn't a good solution, it was more for test purpose, as it bypasses mail_thread.post_message logic. Prefer the solution of Allison.

recipient_ids = [2, 4, 6]

recipient_links = [(4, partner_id) for partner_id in recipient_ids]
model_data_obj = self.pool.get('ir.model.data')
ref = model_data_obj.get_object_reference(cr, uid, 'mail', 'mt_comment')

message_data = {
    'type': 'notification',
    'subject': "Message subject",
    'body': "Message body",
    'partner_ids': recipient_links,
    'subtype_id': ref,
    }

msg_obj = self.pool.get('mail.message')
msg_obj.create(cr, uid, message_data)
Portretas
Atmesti
Thibault Delavallee (tde)

Actually using mail_message.create() bypasses some of the logic contained in message_post. Unless you have some specific needs, you should use message_post instead of directly create a mail_message when trying to create messages and notifications. You can post on a 'void' resource (mail.thread, no thread_id) to create a private conversation or push to some specific partners.

Yannick Payot

Thanks for the precision. I see that the bypassed logic is for attachments, thread and parent_id. So for simple notifications wouldn't that be ok?

Allison
Autorius

It looks like this code will in fact create an OpenERP message (as visible in Settings > Technical > Messages) but not deliver it to the user. To get it to deliver to the inbox 'subtype_id' needs to be added to the message_data dictionary. For my testing purposes I hardcoded the value as 1 (which is what subtype="mt_comment" evaluated to in my first example)

Yannick Payot

Ok so it is cleaner to call the message_post method than hardcoding the subtype_id. Unless you really want to get the subtype_id this way:

model_data_obj = self.pool.get('ir.model.data')
ref = model_data_obj.get_object_reference(cr, uid, 'mail', 'mt_comment')
Thibault Delavallee (tde)

Indeed, the subtype is used to filter the followers of the document that will receive a notification of the message. message_post has an argument subtype that is the xml_id of the subtype; 'mail.mt_comment' is the xml_id of 'Discussions'; we generally use it for user input. In your addon, you may define specific subtypes (mail.message.subtype). Examples of subtypes can be found in crm/crm_lead_data.xml (Stage Changed, Lead Won, ...).

Michael Karrer

message_post() does not send E-Mails to followers for me even if i do use a subtype?!? What i do: Create a New Lead AND assign a Sales Team: # Create a new Lead (request.registry is deprocated - should use request.env instead) values['section_id'] = request.env.ref('website.salesteam_website_sales').id newlead = request.registry['crm.lead'].create(request.cr, SUPERUSER_ID, values, request.context) Because of the Sales Team there are three Followers for the newly created lead Post a message with message_post() I would expect that all followers of the new lead will receive an e-mail BUT THEY DONT?!? The normal E-Mail (the one for the lead creation is send via E-Mail but messge_post() does not send E-Mails?!? What do i need to do to send E-Mails also when posting a message through code?!? Here is how i call the message_post: leadrecord.message_post(body=recordtext, subject=values['name'], type='email', subtype='mt_lead_create', content_subtype='plaintext') Also tried with: leadrecord.message_post(body=recordtext, subject=values['name'], type='notification', content_subtype='plaintext') Message is posted BUT no E-Mails are send :(

Related Posts Replies Rodiniai Veikla
Best way to get a document URL (internally)
development addon v7 link
Portretas
1
kov. 15
8349
Livechat Offline Operator
development message
Portretas
0
bal. 25
1458
What's the context? Solved
development v7
Portretas
Portretas
Portretas
Portretas
9
kov. 24
120880
How to do custom implementions on the login screen?
addon v7
Portretas
Portretas
Portretas
Portretas
Portretas
4
bal. 23
14587
How to hook to events of objects?
development v7
Portretas
Portretas
1
birž. 20
13038