"One Trigger Per Object" Pattern

-

The "One Trigger per Object" pattern is a best practice in Salesforce development that involves consolidating multiple trigger logic into a single, well-structured trigger handler class per object. This pattern helps to maintain clean and organized code, reduces the risk of trigger order issues, and facilitates better code reuse and maintainability.

Trigger Handler Class

public class AccountTriggerHandler {
    
    public static void onBeforeInsert(List<Account> newList) {
        // Your before insert logic here
    }
    
    public static void onBeforeUpdate(List<Account> newList, Map<Id, Account> oldMap) {
        // Your before update logic here
    }
    
    public static void onBeforeDelete(List<Account> oldList) {
        // Your before delete logic here
    }
    
    // Add methods for after insert, after update, after delete, and any other trigger events as needed
    
    // Example method for handling custom logic
    public static void customLogic(List<Account> newList, Map<Id, Account> oldMap) {
        // Your custom logic here
    }

}

Trigger Calls the Trigger Method

trigger AccountTrigger on Account (before insert, before update, before delete) {
    
    // Call the appropriate handler methods based on trigger event
    if (Trigger.isBefore) {
        if (Trigger.isInsert) {
            AccountTriggerHandler.onBeforeInsert(Trigger.new);
        } else if (Trigger.isUpdate) {
            AccountTriggerHandler.onBeforeUpdate(Trigger.new, Trigger.oldMap);
        } else if (Trigger.isDelete) {
            AccountTriggerHandler.onBeforeDelete(Trigger.old);
        }
    }
    
    // Optionally, you can call additional handler methods for after events
}

Benefits of this Pattern:

Modularity: Each trigger handler class focuses on specific object-related logic, making the code easier to understand and maintain.
Reduced Complexity: Consolidating logic into a single handler class reduces the complexity of individual triggers, making them easier to manage and debug.
Avoids Trigger Order Issues: By consolidating logic, you can ensure that the order of execution is consistent across different trigger events.
Code Reusability: Handler methods can be reused across different trigger events and even across different triggers for the same object.

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