Real Time Event Capture

Topics:

Salesforce Considerations for Outbound Messaging

Outbound messages and workflow rules must be configured to enable event handling for the iWay Application Adapter for Salesforce. The concept of outbound messaging is part of the workflow rule functionality in Salesforce. Workflow rules can be configured to look for specified field changes or other record activities, such as creating a new object.

Salesforce Considerations for Outbound Messaging

You can configure more than one workflow for each outbound message.
Workflows and outbound messages are associated with the same Salesforce object.
If the destination event listener is unavailable, messages remain in a queue until sent successfully, or until they are 24 hours old. After 24 hours, the messages are dropped from the queue.
If a message cannot be delivered, the interval between retries increases exponentially up to a maximum of two hours between retries.
Messages are retried independent of their order in the queue, so this can result in messages being delivered out of order.
You cannot build an audit trail using outbound messaging. Each message should be delivered at least once, but it can be delivered more than once. It may not be delivered at all if delivery cannot be achieved within 24 hours. The source object may change after a notification is sent, but before it is delivered, so the destination listener will only receive the latest data, not any intermediate changes.
For security reasons, Salesforce restricts the outbound ports you may specify to one of the following:
- 80: This port only accepts HTTP connections.
- 443: This port only accepts HTTPS connections.
- 1024-66535 (inclusive): These ports accept HTTP or HTTPS connections.

	WebFOCUS