Author: zeusexam

The following screenshot summarizes this configuration: Get Records screen configuration for contacts Create another Get Records element for the Account object with the same configuration that’s shown in the preceding screenshot; the only things we need to change are the object type (which should be set to Account), the matching condition based on the Duns…

Connecting flows and subflows We can connect data between flows using input/output resources. When you set up a new resource, you can specify whether that resource can be seen from outside its flow, as shown in the following screenshot: Setting our resource’s availability Let’s say we want to create a flow to help sales reps…

This flow, coupled with a Process Builder on the opportunity object, sends an email alert (using an Email Alert action): The flow is configured like so: This is the configuration of Mild Deal pause conditions: Pause Configuration for mild deal path This is the configuration of the Resume event for the Mild Deal path: Resume…

The Coding Approach When deeper customization is needed, the coding approach is a win-win situation. In this chapter, you will learn how Apex triggers can provide complex automation for your processes when a point & click approach is not enough. Also, we will see how to evaluate Visualforce and Lightning Components customizations (which you won’t…

Managing a flow Like any other automation process, a flow can be activated and deactivated. It supports versioning (and so cloning is a good choice if you wish to experiment with different versions) and, as in Process Builder, only one version of a flow can be active at a given time. A flow can be…

Order of execution We can basically do five different operations on Salesforce records:• Insert• Update• Upsert (which is just an insert or update operation, depending on the fact that the record may already be in the database, given a unique field such as its ID)• Delete• Undelete While the delete and undelete operations have never…

Trigger features and rules In the previous section, we saw that the order of execution of Salesforce automation has to deal with all of the available automation tools within the Salesforce platform and that Apex triggers are called twice, before and after the record is saved to the database. This is one of the pros…

Apex trigger anatomy So far, we know that a trigger is defined by the following: This is more or less the code involved in a trigger’s definition: 1. trigger OpportunityTrigger on Opportunity (before insert, before update,2. before delete, after insert, after update,3. after delete, after undelete) {4.     //code goes here…5. } All possible event combinations…

The trigger logic worked as we expected! What if we try to delete the record? Unexpected error when deleting the opportunity How’s that? This is related to how the trigger is written. Let’s jump back to the Developer Console and the Logs panel: Debugging log after an unexpected record on a save operation Filtering a…

This property is a list of records of the opportunity type that contains all records that are part of the current trigger execution (and that have the most recent field values). A list is just a complex Apex type that is used to store a set of items of the same type. These elements can…