shows how asynchronous processing works with platform events. The events published into the bus are delivered in order via publish after commit and then processed in bulk by a flow in a separate synchronous context.

shows an event being published when a record is modified. The message body of the event is stored in a separate data store while the header, which contains a claim check is passed onto a subscriber. The subscriber then uses the claim check to retrieve the message body when it's ready to process the information when necessary.

shows time-based interactions involved in the end-to-end flow of information from customer interactions on the Experience Cloud site to back-end automation in Marketing Cloud and Slack. Mulesoft orchestrates integrations to back-end systems, Slack connects everyone on the team, and Marketing Cloud closes the loop with the customer journey.

The time based interactions of systems in a hospitality loyalty management process.

shows an example of the Queuing pattern that depicts an event being published and written to a queue when a record is modified. Subscribers receive copies of the event from their associated queues and make the appropriate updates to their own records.

This is an example solution architecture diagram from the Building Forms Decision Guide that shows a connection to an external data source via an HTTP Callout in Flow and an HTTP Action in OmniStudio.

A diagram depicting Salesforce Data 360 using out of the box connectors for integration with various Google Cloud Platform Services.

A diagram depicting Salesforce Data 360 using out of the box connectors for integration with various AWS Data Services

A diagram depicting Salesforce Data 360 using out of the box connectors for integration with Snowflake Data Lake House Platform.

A diagram depicting Salesforce Data 360 using out of the box connectors for integration with Databricks Delta Lake house Platform.

An end-to-end diagram depicting Salesforce Data 360 as implemented within Salesforce as our Customer Zero program

A diagram depicting Salesforce Data 360 in an end-to-end solution for marketing activations.

An architecture diagram that depicts the products and capabilities directly involved in a loyalty management solution.

A system landscape for a Customer 360 Architecture implementation. It shows how different components within an integrated Salesforce solution communicate with each other using native connectors. It includes capabilities such as Data Ingress, Identity Resolution, Segmentation, and Activation.

A system landscape capturing the mix of Salesforce products and other technology systems available with Agentforce.

A system landscape showing a B2C Commerce and Marketing solution, indicating the mix of Salesforce products and other technologies involved in the implementation.

A diagram depicting an example org hierarchy, capturing a subset of roles in order to clarify business structure, personas, and permissions for a specific use case.

A diagram depicting a single Salesforce org architecture supporting multiple business units.

A visual roadmap that streamlines resource planning and budgeting by grouping capabilities and identifying implementation order, dependencies, and value.

A visual roadmap that optimize resource planning and budgeting by identifying system functionality, relevant features, implementation order, timeframes, and stakeholder dependencies.

A visual roadmap that enhances collaboration between business and technical teams by identifying feature implementation order, dependencies, and additional functionality for planning purposes.

A diagram detailing the deliverables for an initial Agentforce project release. It includes stages Project Definition, Configure and Test, Pilot Release, and Beta Release.

A roadmap showing the stages for rolling out Agentforce features across a Salesforce Customer 360 implementation.

A roadmap diagram that simplifies resource planning and budgeting.