Skip to main content

Trigger Context Variables

These variables are contained in the System.Trigger class.

VariableUsage
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.
Possible values of the System.TriggerOperation enum are: BEFORE_INSERTBEFORE_UPDATEBEFORE_DELETE,AFTER_INSERTAFTER_UPDATE,
 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:
Trigger exampleTrigger on Account (after insert) {
  if (Trigger.isInsert) {
     ExampleTriggerHelper.afterInsertLogic(Trigger.new);
  }
}

Class:
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
   }
}







Comments

Popular posts from this blog

Maintain Your Administrator Certification for Spring ’24

Maintain Your Administrator Certification for Spring ’24 Intelligence Views Intelligence views are now available for leads, contacts, and accounts in Sales Cloud. Turn on a view in Setup and then add the Intelligence View button to the view-button layout for the applicable page. New Salesforce organizations include the views by default, but admins for existing orgs can enable: Lead Intelligence View Contact Intelligence View Account Intelligence View Find specifics about these views in the next three topics. Turn on Contact Intelligence View in Contact Intelligence View Setup and add the Intelligence View button to the Contact List View button layout. To view engagement metrics, enable Email Tracking in the Inbox section of Sales Engagement Setup. To see the Intelligence View, users go to the Contact home page and click Intelligence View. To view engagement metrics, choose Engagement Metrics from the Metrics menu. To see the Account Intelligence view, go to the account home page and cl...

Platform App Builder Certification Maintenance (Winter '24)

 Maintain Your Platform App Builder Certification for Winter ’24 The Enable Reactive Components for Screen Flows running API Version 57.0 and 58.0 setting expires in Winter ’25. Before that release, upgrade your flows to run on API version 59.0 or later to take advantage of reactive components. Build Screen Flows with Reactive Global Variables Save time by referencing global variables in reactive formulas on flow screens. Use custom labels in reactive formulas to display translatable text to your users. For example, create a custom setting called DiscountPercentage, which specifies org, profile, and user discount percentages. Reference the variable in reactive formulas across a screen flow. The screen flow applies the correct discount value for the user running the flow and recalculates the value as the user makes changes.   Build Screen Flows with Reactive Selections Use choice components to respond to user selections elsewhere on the same screen. For example, on a flow ...

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:

Translate