Apex Trigger Framework v2.1

Best Practice Series
Apex Trigger Framework
Presented by
Joseph Msallem
Nicole Tannous
Ziad Azoury
1
Copyright © 2020 EI-Technologies-Lebanon SAL.
Plan
01 Current Triggers Best Practices
02 What is a Salesforce Apex trigger framework
03 Apex Trigger Framework Architecture
04 What do we need to develop an Apex Trigger Framework
05 Benefits of an Apex Trigger Framework
06 Demo
2
Current Trigger Best Practice v2,0
• The trigger contains only one combination of type(isBefore /

Triggers isAfter) and DML (isInsert / isUpdate / isDelete)
(Best Practice v2,0) • We also had the PAD ByPass while verifying the DML. We can
also bypass by method.
3
trigger AccountTrigger on Account (before insert){
if(PAD.CanTrigger('AccountBeforeInsert’)){
if(PAD.CanTrigger('AccountBeforeInsertMethode01’)){
AP01Account.myMethodeAccBeforeInsert01(Trigger.new, Trigger.old);
}
if(PAD.CanTrigger('AccountBeforeInsertMethode02’)){
AP01Account.myMethodeAccBeforeInsert02(Trigger.new, Trigger.old);
}
}
}
trigger AccountTrigger on Account (after insert){
if(PAD.CanTrigger('AccountAfterInsert’)){
if(PAD.CanTrigger('AccountAfterInsertMethode01’)){
AP01Account.myMethodeAccAfterInsert01(Trigger.new, Trigger.old);
}
}
}
trigger AccountTrigger on Account (before Update){
if(PAD.CanTrigger('AccountBeforeUpdate’)){
if(PAD.CanTrigger('AccountBeforeUpdateMethode01’)){
AP01Account.myMethodeAccBeforeUpdate01(Trigger.new, Trigger.old);
}
}
}
4
• The trigger must contain only the instantiation of the

corresponding handler class, the isBefore / isAfter, and the the
Triggers verification of DMLs isInsert / isUpdate / isDelete
(Best Practice v3,0) • We also had the PAD ByPass while verifying the DML. We can
also bypass by method.
5
trigger AccountTrigger on Account (before insert, before update, before delete, after insert, after update){
AccountTriggerClass ATC = new AccountTriggerClass();
if(Trigger.isBefore){
if(Trigger.isInsert && PAD.CanTrigger('AccountBeforeInsert’)){
ATC.myMethodeBeforeInsert(Trigger.new);
}
if(Trigger.isUpdate && PAD.CanTrigger('AccountBeforeUpdate')){
if(PAD.CanTrigger('AccountBeforeUpdateMethode01'))
ATC.myMethodeBeforeUpdate01(Trigger.new, Trigger.old);
if(PAD.CanTrigger('AccountBeforeUpdateMethode02'))
ATC.myMethodeBeforeUpdate02(Trigger.new);
}
if(Trigger.isDelete && PAD.CanTrigger('AccountBeforeDelete')){
ATC.myMethodeBeforeDelete(Trigger.new);
}
}
if(Trigger.isAfter){
if(Trigger.isInsert && PAD.CanTrigger('AccountAfterInsert')){
if(PAD.CanTrigger('AccountAfterInsertMethode01'))
ATC.myMethodeAfterInsert01(Trigger.new, Trigger.old);
if(PAD.CanTrigger('AccountAfterInsertMethode02'))
ATC.myMethodeAfterInsert02(Trigger.new);
}
if(Trigger.isUpdate && PAD.CanTrigger('AccountAfterUpdate')){
ATC.myMethodeAfterUpdate(Trigger.new);
}
}
}
6
Definition
The trigger framework The base class includes

bundles a single context-specific methods
TriggerHandler base class that are automatically
that you can inherit from called when a trigger is
in all your trigger handlers executed
The base class also The most important part

provides a secondary role of this framework is that
as a supervisor for Trigger it's minimal and simple to
execution use
7
Apex Trigger Framework Architecture
SObject Interface
ITriggerHandler
DML Business Logic
<sObject>Trigger Implements
Calls
Calls Dynamic Binding
<sObject>TriggerHandler
TriggerDispatcher
Run (ITriggerHandler handler)

Utils
Interface Trigger Error Handling

Dispatcher
Contains all trigger

SERVICES
Sits between Apex Another Apex Class
context method Trigger and handler which create the Error
class and routes to logs and Stores in a
correct method or custom Object
Handler class
9
Steps to create it
01 Each trigger must be implemented in a custom metadata that allows the trigger to be
active/inactive from UI.
10
Steps to create it
02 Create a record for each trigger
02 Lorem Ipsum
03 Lorem Ipsum
04 Lorem Ipsum
11
Steps to create it
03 Create a Trigger Handler Interface
Public interface ITriggerHandler{
void beforeInsert();
02
void afterInsert();
void beforeUpdate();
Lorem Ipsum
void afterUpdate();
void beforeDelete();
void afterDelete();
void afterUnDelete();
Boolean isDisabled();
03
}
Lorem Ipsum
04 Lorem Ipsum
12
Steps to create it
04 Create the dispatcher
This is a part of the dispatcher code

You can check the complete code from the link below:
https://github.com/kevinohara80/sfdc-trigger-framework
NB: Check the API version is always 51 or higher
04 Lorem Ipsum
13
Steps to create it
05 Create the SObject Trigger Handler extending the Trigger Handler and implementing the Trigger
Handler Interface
public class SObjectNameTriggerHandler extends TriggerHandler implements ITriggerHandler{
private Map<Id, SObject> newMap;

private Map<Id, SObject> oldMap;
private List<SObject> triggerNew;
Lorem List<SObject>
private Ipsum triggerOld;
public SObjectNameTriggerHandler(){
this.newMap = (Map<Id, SObject>) Trigger.newMap;
this.oldMap = (Map<Id, SObject>) Trigger.oldMap;
this.triggerNew= (List<SObject>) Trigger.New;
this.triggerOld= (List<SObject>) Trigger.Old;
03
}
public static Boolean TriggerDisabled = false;
LoremBoolean
public IpsumisDisabled(){
return TriggerDisabled;
}
public override void beforeInsert() {}
public override void afterInsert() {}
04
public override void beforeUpdate() {}
Loremoverride
public Ipsum void afterUpdate() {}
public override void beforeDelete() {}
public override void afterDelete() {}
public override void afterUnDelete() {}
14
Steps to create it
06 Create the Sobject’s trigger
/*
@Author : TMA NTA
@CreatedDate : 11-02-2021
@Description : SObjectName Trigger.
*/
trigger SObjectNameTrigger on SObject(before insert, after insert, before update, after update, before delete, after
delete, after unDelete) {
new SObjectNameTriggerHandler().run();
}
15
Benefits
A single trigger per object gives complete

control over the order of execution
Implementing trigger logic in handler class,
makes unit testing and maintenance much
easier
Implementation of best practices
It allows to prevent trigger recursion without

adding separate logic
It is easier to work on a single trigger for
multiple developers and reduce the
development lifecycle
It allows to make decisions to active/inactive
the trigger from transaction and UI as well
16
Cool features
Max Loop Count

06
To prevent recursion, you can set a public class OpportunityTriggerHandler extends TriggerHandler {
max loop count for Trigger public OpportunityTriggerHandler() {
this.setMaxLoopCount(1);
Handler. If this max is exceeded, }
and exception will be thrown. A public override void afterUpdate() {

List<Opportunity> opps = [SELECT Id FROM Opportunity WHERE Id IN:Trigger.newMap.keySet()];
great use case is when you want to }
update opps; // this will throw after this update
}
ensure that your trigger runs once
and only once within a single
execution. Example:
17
Cool features
Bypass API
What if you want to tell other trigger handlers to halt execution? That's easy with the bypass api:
public class OpportunityTriggerHandler extends TriggerHandler {
public override void afterUpdate() {
List<Opportunity> opps = [SELECT Id, AccountId FROM Opportunity WHERE Id IN :Trigger.newMap.keySet()];
Account acc = [SELECT Id, Name FROM Account WHERE Id = :opps.get(0).AccountId];
TriggerHandler.bypass('AccountTriggerHandler’);
acc.Name = 'No Trigger’;
update acc; // won't invoke the AccountTriggerHandler
TriggerHandler.clearBypass('AccountTriggerHandler’);
acc.Name = 'With Trigger’;
update acc; // will invoke the AccountTriggerHandler
}
}
If you need to check if a handler is bypassed, use the isBypassed method:

if (TriggerHandler.isBypassed('AccountTriggerHandler')) {
// ... do something if the Account trigger handler is bypassed!
}
If you want to clear all bypasses for the transaction, simple use the clearAllBypasses method, as in:
// ... done with bypasses!
TriggerHandler.clearAllBypasses();
// ... now handlers won't be ignored!
18
Demo
DEMO
19
THANK YOU
ANY QUESTIONS?
20
References
https://github.com/kevinohara80/sfdc-trigger-framework
https://www.biswajeetsamal.com/blog/salesforce-apex-trigger-framework/
https://trailhead.salesforce.com/en/content/learn/modules/success-cloud-coding-conventions

Apex Trigger Framework v2.1

Uploaded by

Copyright:

Available Formats

Apex Trigger Framework v2.1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Apex Trigger Framework v2.1

Uploaded by

Copyright:

Available Formats

Best Practice Series

Apex Trigger Framework

01 Current Triggers Best Practices

02 What is a Salesforce Apex trigger framework

03 Apex Trigger Framework Architecture

04 What do we need to develop an Apex Trigger Framework

05 Benefits of an Apex Trigger Framework

• The trigger contains only one combination of type(isBefore /

trigger AccountTrigger on Account (before insert){

trigger AccountTrigger on Account (after insert){

trigger AccountTrigger on Account (before Update){

• The trigger must contain only the instantiation of the

AccountTriggerClass ATC = new AccountTriggerClass();

The trigger framework The base class includes

The base class also The most important part

DML Business Logic

Copyright © 2020 EI-Technologies-Lebanon SAL.

Interface Trigger Error Handling

Contains all trigger

02 Create a record for each trigger

03 Create a Trigger Handler Interface

Public interface ITriggerHandler{

04 Create the dispatcher

This is a part of the dispatcher code

NB: Check the API version is always 51 or higher

public class SObjectNameTriggerHandler extends TriggerHandler implements ITriggerHandler{

private Map<Id, SObject> newMap;

public override void afterInsert() {}

public override void afterDelete() {}

public override void afterUnDelete() {}

06 Create the Sobject’s trigger

A single trigger per object gives complete

Implementation of best practices

It allows to prevent trigger recursion without

Max Loop Count

and exception will be thrown. A public override void afterUpdate() {

If you need to check if a handler is bypassed, use the isBypassed method:

// ... now handlers won't be ignored!

Copyright © 2020 EI-Technologies-Lebanon SAL.

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.