In Salesforce, Triggers are known as Apex Triggers. The triggers are unique and are accessible, particularly for general and anticipated actions such as lead conversions. Trigger in the Salesforce is the Apex code that we use to perform the operation before and after we report the record. In this article, we will study different kinds of Trigger scenarios in Salesforce.
If you would like to become a Salesforce cpq training certified professional, then visit onlineitguru - A Global online training platform: “ Salesforce Certification Training” Course. This course will help you to achieve excellence in this domain.
Important Points for Trigger Scenarios
1. As per the execution order, we have two types of triggers: 1) before trigger 2) after the trigger.
- Before the Insert Event
- While using this event, we execute the code block before we insert a new record.
- Data committed to the database.
- After the Insert event
While using this event, first, we will execute the code block, and after that, we insert the record.
2.We use the Before trigger to perform the logic on the same object.
3.We use the “before event” trigger if we have to update the same record in the trigger.
4.In the Before trigger, the records are not committed to the database. Therefore, we skip the DML.
5.When the record is committed to the database, i.e. record Id is created, and our trigger records in read-only mode. We cannot update the values for more salesforce cpq learning path.
[Related Article: "How to create Sample Apex Triggers in Salesforce"]
Keywords of Trigger Syntax:
- Trigger name: It is the name that we have to give to our trigger.
- Object name: It is the object over which we have to perform the action.
- Trigger_events: They are the events list separated with commas.
Real-Time Trigger Scenarios in Salesforce
Scenario 1:
Create “Sales Rep” with data type on Account object. While we create account records, account owners will be systematically inserted into the sales representative field. While we update the record account owner, the sales representative will be systematically updated.
Description:
In the upper trigger scenario, we have to start the trigger prior to the account creation, so we use the “before insert” trigger over the Account object. Likewise, according to the requirement, for the update event, therefore, we update the “before update” trigger over the Account object.
Step 2:
We use “set” for storing the “Ids” because we don’t require duplicate Ids of the account owner. So, we create an instance for that like the “SetAccowner”.
Step 3:
After that, we use the “for” loop to all the new accounts; therefore, we use “trigger. new” in the loop. In the “for” loop, we add the account “OwnerId” in the set.
Step 4:
After that, we create the instance of the map “user map” that stores “value = user” and “Key = Id” along with the query. SELECT Name FROM user WHERE Id IN: setAccowner
Step 5:
After that, in the following “for” loop, we create the instance “usr” for the user, which is equivalent to the Account “owner” that we get from “map”.
Step 6:
In the end, the sales representative “sales_rep_c” is equivalent to “usr. Name”
Scenario 2:
Create the field with the name “Contact Relationship” checkbox over the contact object and generate an object known as “Contact Relationship” that is associated with contacts. Develop a logic while we create a connection by verifying the contact relationship checkbox; after that contact, the relationship is established systematically for the contact. Trigger:
Description
Step 1:
According to the requirement, we perform the operation over the trigger when a user submits a record which means we have to use the “after insert” trigger. After that, when we have to check about an event, therefore we use “trigger. insert” and “trigger.isAfter” to dismiss trigger on these specific events.
Step 2:
After that, we create an instance of the apex class “Contact Master Handler” as “ConIns”. After that, we call a “call Contact Relationship By Contact” method from the apex class.
