Salesforce Platform Event

-

Platform Events provide a way to deliver secure, scalable, and customizable event notifications within and outside of the Salesforce platform. Platform Events are based on the publish-subscribe model, allowing publishers to broadcast events and subscribers to receive and process those events in real time.

Salesforce Event Bus














Example: OrderPlaced Platform Event

Let's assume you want to create a Platform Event called OrderPlaced__e to represent the event of a new order being placed in your Salesforce org. This event will contain information about the order, such as the order ID, customer name, and total amount.

Define the Platform Event Schema:

Go to Setup > Platform Events > New Platform Event.

Define fields for the event, such as OrderID__c, CustomerName__c, and TotalAmount__c.

Publish the Platform Event:

You can publish a Platform Event using Apex, Process Builder, Flow, or other methods. Below is an example of publishing an event using Apex.

// Publish OrderPlaced event
OrderPlaced__e orderEvent = new OrderPlaced__e(
    OrderID__c = 'ORD123',
    CustomerName__c = 'John Doe',
    TotalAmount__c = 1000
);
Database.SaveResult result = EventBus.publish(orderEvent);
if (result.isSuccess()) {
    System.debug('OrderPlaced event published successfully.');
} else {
    for(Database.Error error : result.getErrors()) {
        System.debug('Error publishing OrderPlaced event: ' + error.getMessage());
    }

}

Subscribe to the Platform Event:

You can subscribe to Platform Events using Apex triggers or external systems connected to Salesforce via the Streaming API.
Below is an example of subscribing to the OrderPlaced__e event using an Apex trigger.

trigger OrderPlacedTrigger on OrderPlaced__e (after insert) {
    List<OrderPlaced__e> newEvents = Trigger.new;
    for (OrderPlaced__e event : newEvents) {
        // Process the OrderPlaced event
        System.debug('New order placed: ' + event.OrderID__c + ' by ' + event.CustomerName__c + ' for ' + event.TotalAmount__c);
    }
}

Process the Event:

Once the event is published, the trigger subscribes to the event and processes it.
In this example, the trigger logs a debug message with information about the new order.
That's it! You've created a Platform Event called OrderPlaced__e, published an event when a new order is placed, and subscribed to the event to process it in real time.

Platform events publishing demeanors

In Salesforce, there are two types of publishing behavior for platform events.

Publish after commit — Enabling this option allows for event publishing after a successful transaction commit. This feature is useful in situations where a subscriber needs to be notified upon the completion of a transaction. For instance, upon completing a checkout process, an email can be triggered to user based on the Order status.

Publish immediately — This option involves publishing the event irrespective of whether the transaction is successful. It is suitable if the subscriber does not require the process to be completed successfully. An example of this would be alerting the user about a critical error.

The publish behavior option applies to event messages published through the Lightning Platform, such as Apex, Process Builder, and Flow Builder, and through Salesforce APIs.

Platform Events provide a powerful mechanism for building event-driven architectures and integrating Salesforce with other systems in a scalable, reliable, and customizable manner. They enable organizations to create responsive, real-time applications and automate business processes based on event-driven triggers and notifications.

References

Event-Driven App Architecture On The Customer 360 Platform

Platform Events Developer Guide

Platform Events Basics

Define a Platform Event

Standard Platform Event Object List

Platform Event Considerations

Comments

Post a Comment

Popular posts from this blog

Introduction to Salesforce Agent Script: Build Predictable AI Agents

-
Image
Please visit here for more details - https://ayaninsights.com/guestblogs/introduction-to-agent-script/ In my latest blog, I introduce Salesforce Agent Script and explain how it helps teams build AI agents that are more predictable, controlled, and aligned with business processes. Large language models are flexible, but relying only on natural-language instructions can sometimes produce inconsistent results. Agent Script addresses this challenge by combining the conversational capabilities of an LLM with structured business logic. The blog explains how developers can use conditions, variables, actions, topics, and transitions to control how an Agentforce agent behaves. Agent Script supports familiar logic such as if/else conditions, value comparisons, sequential actions, and checks for missing data. I also cover its core structure, including system settings, configuration, global variables, languages, connections, and topic blocks. The start_agent topic acts as the entry point for each...
Read more

Anti-Patterns in Salesforce Agentforce: What to Avoid When Building AI Agents

-
Image
Salesforce Agentforce is powerful because it allows teams to build AI agents that can understand user intent, retrieve grounded information, execute actions, and support business workflows across Salesforce. But like any powerful platform, the quality of the implementation matters. A good Agentforce implementation does not start with “How many things can the agent do?" It starts with “What problem should the agent solve reliably?” That is where anti-patterns come in. Anti-patterns are common implementation habits that look useful at first but eventually create confusion, poor user experience, inconsistent answers, or hard-to-maintain agents. Below are some of the most common Agentforce anti-patterns and how to avoid them. 1. Trying to Build One Agent That Does Everything One of the biggest mistakes is designing a single agent to handle every business process, every department, and every possible customer question. At first, this feels efficient. One agent, many use cases. Bu...
Read more

MCP vs. Traditional APIs: Choosing the Right Integration Approach

-
Image
Enterprise integration has traditionally been built around APIs. Applications send structured requests, services process them, and predictable responses are returned. This model has supported everything from payment processing and customer portals to mobile applications and large-scale system integrations. The rise of AI agents introduces a different integration challenge. An AI agent does not always follow a fixed sequence designed in advance. It may need to determine which system to use, discover the operations available to it, gather relevant context, and select the appropriate action based on a user’s request. This is where the Model Context Protocol, or MCP, becomes relevant. MCP and traditional APIs are related, but they solve different problems. APIs expose system capabilities. MCP provides a standardized way for AI applications to discover and use those capabilities as tools and contextual resources. Understanding this distinction is important when designing enterprise AI solut...
Read more