2

I'm writing a generic handler for notifications received from Outbound Messaging.

A single notification SOAP message may contain one or more notifications.

As I understand it, whether I get 1 message with 40 notifications or 40 messages with 1 notification each is under the control of Salesforce. Correct?

My question is really about whether the notifications could potentially be of different types.

Say I had two Outbound Messages configured to send to the same endpoint url. For example one triggered on changes to Lead and another triggered on changes to Opportunity.

Is salesforce smart enough to batch up a mixture of Lead and Opportunity notifications in the same SOAP message? Or would it produce a batch of Lead notifications in one message and a batch of Opportunity notifications in another message.

Is it safe to assume that all the notifications in a SOAP message will be for the same sObject Type?

Footnote:

The reason I'm building a generic handler is because I don't want to keep importing WSDL it's a major pain. I'm writing a set of C# classes that will be handlers for Salesforce Notifictions, along with code that will choose and dynamically instantiate the appropriate handler based on the content of the SOAP message, and although I've had to temporarily shelve this work, my prototype works and this method looks viable.

Improve this question

1 Answer 1

Reset to default
1

You won't see a mix of sobject types in a single message. You can somewhat infer this from the WSDL, which has actionId at the message level, rather than at the notification level.

Improve this answer
3
  • What would you infer actionId represents? (Just out of interest).
    – IanT8
    Aug 5, 2014 at 2:59
  • actionId represents the instance of the outbound message config
    – superfell
    Aug 5, 2014 at 4:48
  • i.e. the thing that says send these fields to this URL.
    – superfell
    Aug 5, 2014 at 4:48

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .