A company is planning on sending orders from Salesforce to a fulfillment system. The integration architect has been asked to plan for the…

When planning an integration, the architect must first understand the capabilities of the external system to select the most appropriate integration pattern. Callback Capability (B): Asking if the fulfillment system can make a callback is critical for designing an asynchronous integration. For an order fulfillment process, Salesforce needs to know the final status (e.g., shipped, canceled). A callback allows the fulfillment system to update Salesforce asynchronously, which is a robust and scalable pattern for long-running processes. Outbound Messaging Support (C): Outbound Messaging is a standard, declarative Salesforce integration feature that sends a SOAP message to a designated endpoint. Asking if the fulfillment system can implement an interface based on the Salesforce-generated WSDL (a contract-first approach for the endpoint) directly assesses its compatibility with a reliable, asynchronous, fire-and-forget pattern.

1. Salesforce Architect Documentation

Integration Patterns and Practices: The "Fire and Forget" pattern section discusses solutions like Outbound Messaging. The "Remote Process Invocation—Request and Reply" pattern highlights the importance of the remote system's ability to process requests and

in asynchronous variations

provide updates

often via a callback mechanism. This underscores the need to evaluate the remote system's capabilities (Reference B and C).

2. Salesforce Developer Documentation

"Outbound Messaging": This documentation explicitly states

"The endpoint must be able to process the SOAP message defined by the WSDL generated by Salesforce." This confirms that evaluating the fulfillment system's ability to implement a contract-first interface (Reference C) is a primary consideration.

3. Salesforce Architect Documentation

"Event-Driven Architecture": This guide discusses how event-driven patterns

which often involve callbacks or separate update events

are used for decoupling systems. It states

"The subscriber can... call back to the event producer to get more data." This validates that assessing callback capability (Reference B) is a standard architectural consideration.