When you process outbound data in real time, the Organization and Person records in Customer 360 SaaS are synchronized in Salesforce instantaneously.
Before you configure real-time outbound records synchronization, set up your Kafka streaming platform.
To process outbound records in real time, define a publishing event in Business 360 Console for the Customer 360 SaaS business entity records that you want to synchronize. When you create, update, merge, or unmerge a record, the publishing event triggers. Business 360 Event Connector captures the change, and a streaming ingestion and replication task writes it as a message to a Kafka topic.
Kafka is a message bus between Customer 360 SaaS and Salesforce. It holds each change as a message on a Kafka topic in the order the changes occur, and delivers the message to an Application Integration process. An Application Integration process reads each message from Kafka. Through Salesforce Streaming Event Connector, the process publishes the message to Salesforce as a platform event.
In Salesforce, the platform event reaches the event bus, where an Apex trigger processes it and updates the target Account or Contact record.
The following image shows how you can synchronize the outbound records in real time:
Source system filtering
Real-time outbound records synchronization uses the source system of a record to determine whether to export the record to Salesforce. You configure the source systems in the Application Integration process to export only the records you want. This configuration prevents a synchronization loop, where an exported change triggers another export back to the source system.
When a record is created in Customer 360 SaaS, the Application Integration process exports the record to Salesforce only if its source system is in the allowed list. The process skips records from any other source system. For example, the process doesn't export a record created directly in Customer 360 SaaS unless you add the Informatica source system to the allowed list.
When a record is updated in Customer 360 SaaS, the Application Integration process exports the update to Salesforce unless the update originated in the Salesforce source system. The Application Integration process skips updates from any source system in the skip list. The record in Salesforce already has the update, and exporting it again causes a synchronization loop.
Application Integration uses universal resource names (URNs) to identify source systems. In the SourceSystemIDOutbound URN mapping, the URL value holds the allowed list, and in the SourceSystemIDSkip URN mapping, the URL value holds the skip list. By default, the URL value in both URN mappings is infac360sf_src_Salesforce.
To export records from your source systems, add those source systems to the URL value in the SourceSystemIDOutbound URN mapping.
