Skip to main content

Trigger Context Variables

These variables are contained in the System.Trigger class.

isExecutingReturns true if the current context for the Apex code is a trigger, not a Visualforce page, a Web service, or an executeanonymous() API call.
isInsertReturns true if this trigger was fired due to an insert operation, from the Salesforce user interface, Apex, or the API.
isUpdateReturns true if this trigger was fired due to an update operation, from the Salesforce user interface, Apex, or the API.
isDeleteReturns true if this trigger was fired due to a delete operation, from the Salesforce user interface, Apex, or the API.
isBeforeReturns true if this trigger was fired before any record was saved.
isAfterReturns true if this trigger was fired after all records were saved.
isUndelete*Returns true if this trigger was fired after a record is recovered from the Recycle Bin.
This recovery can occur after an undelete operation from the Salesforce user interface,
 Apex, or the API.
newReturns a list of the new versions of the sObject records.
This sObject list is only available in insertupdate, and undelete triggers, and the 
records can only be modified in before triggers.
newMapA map of IDs to the new versions of the sObject records.
This map is only available in before updateafter insertafter update, and 
after undelete triggers.
oldReturns a list of the old versions of the sObject records.
This sObject list is only available in update and delete triggers.
oldMapA map of IDs to the old versions of the sObject records.
This map is only available in update and delete triggers.
operationTypeReturns an enum of type System.TriggerOperation corresponding to the current operation.
 AFTER_DELETE, and AFTER_UNDELETEIf you vary your programming logic based on
 different trigger types, consider using the switch statement with different permutations of unique trigger execution enum states.
sizeThe total number of records in a trigger invocation, both old and new.
Recycle Bin = Available on home tab in classic mode 

Best Practice :

  •  Always use helper apex class to write the implementation or business logic.
  • Use Test class to cover Trigger not to helper class, helper class will be automatically covered through that.
  • Always use above context variable.

An Example :
Trigger exampleTrigger on Account (after insert) {
  if (Trigger.isInsert) {

public with sharing class ExampleTriggerHelper{
   public static void afterInsertLogic(List<Account> newAccountsList){
    Contact[] cons = [SELECT LastName FROM Contact
                      WHERE AccountId IN :newAccountsList];
     //implement your business logic here


Popular posts from this blog

Platform Developer I Certification Maintenance (Winter '23)

 Maintain Your Platform Developer I Certification for Winter ’23 1. Field update actions have changed in API Version 54.0. Which record-triggered flows do field update actions now execute? Answer: Before-Save after After-Save 2. Which Apex class is used to determine the hostnames for the domains that Salesforce hosts for your org? Answer: System.DomainCreator 3. Which modules can be used for notifications in a Lightning web component instead of native APIs? Answer: LightningAlert, LightningConfirm, and LightningPrompt 4. What determines an org’s “shape” in Salesforce? Answer: Features, settings, edition, limits, and licenses 5. Which lightning-modal-* component is required to create a modal? Answer: Body 6. How do you call an invocable action from Apex code? Answer: Reference Invocable.Action Get Hands-On With Apex Assertions 1. Create Two Apex class: Copy and Paste below codes (A.) TestFactory @isTest public class TestFactory {    public static Account getAccount(String accountName, B

Administrator Certification Maintenance (Spring '23)

 Maintain Your Administrator Certification for Spring '23 1. What information is listed in the Details panel for recently used reports? Answer: A, B, C 2. What is used to give sales reps access to a guided process to import contacts and leads? Answer:  Sample CSV file 3. Which feature efficiently removes inactive picklist values? Answer: Bulk Delete Unused Values 4. Which type of Process Builder processes can be converted using the Migrate to Flow tool? Answer: Record-triggered Get Hands-on with Enhance Record Pages With Dynamic Forms Follow steps show in Screenshot also highlighted with Red Box:

Platform App Builder Certification Maintenance (Winter ’23)

Maintain Your Platform App Builder Certification for Winter ’23 1. What component customizes related lists directly from the Lightning App Builder? Answer:      Dynamic Related List – Single 2. Where can a debug flow test be created and saved? Answer:      Flow Builder 3. What action enables smart email auto-responses in Flow Builder? Answer:      Create Article Recommendations 4. Custom address fields improve address data accuracy for your users using what type of list? Answer: State and Country/Territory Picklists 5. What are the benefits of using Dynamic Forms on record pages? Answer:      Place fields anywhere on the page  Use Visibility Rule to show and hide fields  6. Restriction or scoping rules now allow multiple values. When should double quotes surround a value? Answer:      If a single value contains a comma  Get Hands-On With Permission Set Expiration Verify before performing this: Permission Set & Permission Set Group Assignments with Expiration Dates should be enabled