Interaction Process Flow
Interaction process flow diagrams illustrate the sequence of interactions, data flows, and process steps between system components, services, and users. These diagrams help architects and developers understand how different parts of a system communicate, how events propagate through the architecture, and how asynchronous and synchronous processes are orchestrated. They provide essential documentation for understanding system behavior, identifying bottlenecks, and optimizing process flows.
This section contains 16 reference diagrams related to interaction process flow:
| Diagram Name | Description |
|---|---|
| Asynchronous Apex Monitoring Via Custom Query | Shows the components involved with tracking the status of asynchronous processes and viewing the results of batch jobs and scheduled jobs. |
| Asynchronous Processing Via Platform Events | Shows how asynchronous processing works with platform events. The events published into the bus are consumed by subscribers for processing. |
| Batch Apex Fair Usage Algorithm | Shows how the fair usage algorithm ensures that each org on the Salesforce platform gets a "fair share" of batch processing resources. |
| Batch Apex Message Re Enqueueing | Shows how the Salesforce Platform's Flow Control mechanism prevents one org from flooding the batch queue by re-enqueueing messages when limits are exceeded. |
| Boxcarring In Javascript Remoting | Shows how multiple JavaScript remoting requests can be issued at the same time, or "boxcar'ed" in a single XHR request to improve performance. |
| Boxcarring In Lightning Actions | Shows how multiple Lightning actions can be issued at the same time, or "boxcar'ed" in a single XHR request to optimize network calls. |
| Claim Check | Shows an event being published when a record is modified. The message body of the event is stored in a database, and only a reference is passed through the message bus. |
| Customer Personalization Flow | Shows time-based interactions involved in the end-to-end flow of information from customer interactions through personalization engines to delivery systems. |
| Fanout | Shows an event being published and written to a single queue when a record is modified via a user interaction, with multiple subscribers processing the event. |
| Hospitality Loyalty Management Process | The time-based interactions of systems in a hospitality loyalty management process. |
| Middleware Pull Via Platform Event Notification | Shows how you can use platform events to deliver outbound integrations or instruct a middleware tool to pull data from Salesforce. |
| Middleware Scheduled Pull | Shows how Middleware can make synchronous requests to SOAP API or REST API to minimize delays associated with real-time processing. |
| Passed Messages | Shows an example of a process flow for the Passed Messages pattern that includes a publisher, a subscriber, and message passing between components. |
| Publish Subscribe Unique Copy | Shows an event being published when a record is modified via a user interaction, a flow, or a batch job, with each subscriber receiving a unique copy of the event. |
| Queuing | Shows an example of the Queuing pattern that depicts an event being published and written to a queue, with subscribers processing events in order. |
| Retail Loyalty Management Process | Time-based interactions of systems in a retail loyalty management process. |