Apex Salesforce Triggers

Salesforce Apex Triggers - Examples & Tips

[apextrigger-com]

Apex Triggers on Change Data Capture Events

In the Summer '19 release, we're very excited about Asynchronous Apex Triggers. This allows you to decouple business logic and heavyweight processing outside of the transaction. What we've done is enabled the case object for Change Data Capture. And we've written this new asynchronous Apex trigger on the case change event itself. This is now going to be executed when these case change events flow through the event bus rather than synchronously inside the transaction on the Case sObject. What we're going to do here is a red account prediction. This process is very limit-intensive, and computationally slow. So, we're going to do this asynchronously, outside the transaction, rather than slowing down the end-user's experience. When this case gets updated, we're going to receive the change event, and predict if this red account is applicable for the account record associated with the case that has just been logged. So, let's do that. We're going to log a case for, "Astro," and it was a phone call with high priority. The part that's failing is the, "GH22." And then, we're going to save that. As you can see, that asynchronous Apex trigger kicked off on that case change event, and predicted that the account, "Astro," may be red. Let's take a look at that. As you can see here, asynchronously, we evaluated that case, and the account status, and determined it was at-risk for an escalation. So, we've updated the rating to red. And now, our service agent can take more direction and action. Also, we've removed that heavyweight calculation outside of the transaction so that all the synchronous processing and transactional logic can happen very quickly. Asynchronous Apex triggers for this release are a very new, exciting enhancement for all those enthusiasts with Apex and Apex triggers.

https://youtu.be/Y_0vejL_wFo

[apextrigger-com]

Apex - Triggers

welcome back in this lecture we will talk about triggers this is often considered as one of those big topics in epics coding have to say that I am pretty excited I think you'll be amazed to see how that for all the height they aren't all that complicated have you ever run into any of these workflow limitations where your workflow can't create or update a separate object or you are not allowed to reference certain fields like owner name or even you need your workflow to do more than simple field updates and emails nothing is more frustrating than being limited by a platform imagine triggers to be workflows without any limitations a trigger is simply a bit of code that kicks off processes when we change a record in Salesforce the whole purpose of a trigger is to wait around listening for some kind of event to happen events like insert update delete or even and delete that's why they're called triggers because they are triggered by some kind of database event they are sort of like conditional logic if an account is updated do this and then this if an account is deleted do this and so on there are two main types of triggers before triggers and after triggers the structure of these two types of triggers are the same but the difference is when they do their work and the data they have available to them before triggers affect the data before the record is committed to the database for example you might want to validate or update a certain field in the record before writing it to the database after triggers let you use the data in a record after it has been committed to the database anytime you want to pull out an ID of a record that you come into to the database you want to use an after trigger a great example would be creating any related records let me walk you through a flow chart that helps you understand what happens in before and after triggers once a change is made to a card the trigger gets fired if it said before trigger the trigger is going to call the method in the class and pass it all the records that were just changed the method would do things like validate data make changes to the data and then finally the records are committed to the database if it is an after trigger records are first committed to the database then the trigger is going to call the method in the class and pass it all the records that were just changed then finally the method would do things like creating related records using the IDS or perform circle queries using the IDS of records that were created let me talk about two scenarios imagine when a new contact is being created you want to validate couple of fields and also update certain fields based on some criteria here I would use it before trigger because I need to validate and update the record before the contact is written to the database think about another scenario where I need to create a related opportunity as soon as an account is created in this scenario we need to use the newly populated account ID to create a related opportunity therefore we would use an actor trigger you should think of before triggers as a default kind of trigger because they use way more often then after triggers they also have an added advantage of not needing PML to save your changes with before triggers your changes to the data are made before record is saved so it's like you're sneaking in your change and then using Salesforce standards a functionality that's pretty neat however there's still plenty of times you will want to use an after trigger the basic structure of a trigger looks like this pretty straightforward trigger name of the trigger on what object and when you want the trigger to fire let's modify our base trigger and add few elements you can probably see that there is only one object specified which is account that's because triggers are specific to one and only one object they can of course involve code that affects many other Salesforce objects like creating or updating records but we'll cover that later how do you say when you want the trigger to run you may want a particular piece of code to run whenever a new record is inserted into your database and when a record is updated a nice thing about a fix triggers is that you don't have to duplicate code to handle this we can just add another event here you can probably tell what we did here we asked the trigger when the account is added or updated in our database then please run the following bit of code there are seven different events that triggers can listen for before insert before update before delete after insert after opti after italy and after and delete where do we put the code we want to run when the apex trigger is well trigger there are two options within the trigger itself or in a separate apex class which we call from within the trigger for lots of reasons the second way is the apex best practice it's easier to read the code and understand what's going on this is a huge part of efficient code maintenance best practice is to keep all your business logic out of the actual trigger it's easier to reuse code classes and methods are usable they can be called from anywhere else it's easier to control the order of code to run if you only have one trigger for each object when your deal with small subsets of your code it's easier to write distinct unit nests we haven't talked about unit tests yet we should get to them soon so just to quickly summarize we talked about what triggers are a trigger is simply a bit of code that kicks off process when we create or change a record in Salesforce you can think of triggers as workflows without any limitations there are two main types of triggers before triggers having the data before that I could has committed to the database and after triggers let you use the data in the record after it has been committed to the database the syntax of a trigger looks like this trigger name of trigger on object and events you on the trigger listen to there are seven different events the trigger can listen to in the next lecture my co-instructor Sal will talk about creating a trigger APICS class and a method and tying it all together

https://youtu.be/d1rLnpzy82k

[apextrigger-com]

Trigger in Salesforce

hi friends welcome to my youtube channel for thunder in this video we'll see what is epics trigger in Salesforce her name is making it and she's working as a sales force developer training while reading about epics trigger first time she is having difficulty to visualize FX trigger and she became sad and this is how she became part of other beginner salesforce developers who all are having seen concerned trigger trigger trigger all beginner developers came together and asked for help to guru ji suddenly guru ji appeared we call him epics guru because he knows everything about epics in order to solve the problem of all beginner developers he delivered some statement about trigger trigger is defined on Salesforce object object could be standard on custom trigger execute when DML occur on object DML in the same insert update or delete trigger contains logic which executes when trigger fired by sister havegot these statements probably not all developers also haven't got any idea about trigger from those treatments so they are - guru ji for real world example finally guru ji agreed to give an example his name is John and he decided to go for movie in cinema there's a security guard for that cinema we can consider him as FX trigger why we are calling him as have extruder because if you remember one of the statement by FX guru he said that FX trigger contains custom logic and fired by the system so how this is treatment applied to the security guard because security guard also has custom logic inside his mind he will check whether John has valid ticket or not if John has valid ticket then he will be allowed to enter into cinema we can consider John as a viewer or object recur and cinema hall has sales force database now John wants to enter into cinema to watch movie but security guard our epics trigger which whether John has valid ticket or not if John has valid ticket then security guard will give one free water bottle to him and allowed him to enter in cinema and presume if John doesn't have valid ticket then security guard won't allow him to enter in Salesforce database let's summarize what we have discussed so far in this video we have introduced three things first one viewer object second FX trigger third Salesforce database novia object record wanna enter in Salesforce database it means PML happened on fear object and we have defined epochs trigger for VR object so FX trigger will come in picture apex trigger will execute before DML and after event the example which we have discussed is part of before insert event type John has valid and critical after successful execution of FX trigger John will be allowed to enter in cinema Hart Wow epics guru we have understood the meaning of FX trigger let's have a look at how trigger defined on a Salesforce object trigger is a keyword security guard is a trigger name fear is object name and in parentheses will define different event type it could be before demon or after DML and in parentheses custom logic will be placed let's clap my friends we have understood the meaning of FX trigger

https://youtu.be/dMZRXZVoY_4