Guided Practice (We-do):

1. Enable the ActionCadenceTracker Object for Change Notifications
2. Autolaunched Flow
   1. Define Flow Properties
   2. Create a Record Collection Variable to store leads 
   3. Add a Loop element to retrieve the records from the record collection variable
   4. Add an Assignment element to assign values into a Record Variable (Task)
   5. Add an Assignment element to add the Record Variable to a Record Collection Variable.
   6. Add a Create Records element to create Tasks
3. Asynchronous Apex Triggers for Change Events

Step 1: Enable the ActionCadenceTracker Object for Change Notifications

1. Click Setup.
2. In the Quick Find box, type Change Data Capture and select Change Data Capture.
3. In Available Entities, select Cadence Tracker (ActionCadenceTracker) and click the > arrow.
4. Click Save.

Step 2.1: Define Flow Properties

1. Click Setup.
2. In the Quick Find box, type Flows.
3. Select Flows, then click on the New Flow.
4. Select the Autolaunched Flow (No Trigger) option.
5. Click on Create.

Step 2.2: Add a Record Collection Variable to Store Leads

1. Under Toolbox, select Manager, then click New Resource to store the leads. 
2. Input the following information: 
   1. ResourceType: Variable
   2. API Name: varR_Leads
   3. Data Type: Record
   4. Object: Lead
   5. Check Allow multiple values (collection) 
   6. Check Available for Input
   7. Check Available for Output
3. Click Done.

Step 2.3: Add a Loop Element to Retrieve the Records from the Record Collection Variable

1. On Flow Designer, click on the +icon and select the Loop element.
2. Enter a name in the Label field; the API Name will auto-populate.
3. For Collection Variable select {!varR_Leads}.
4. For Specify Direction for Iterating Over Collection select the option First item to last item.
5. Click Done.

Step 2.4: Adding an Assignment Element to Assign the Values into a Record Variable (Task)

1. Create a Record Variable varR_Task type Task to  create a task for lead owner.
2. On Flow Designer, below the For Each node, click on the +icon and select the Assignment element. 
3. Enter a name in the Label the API Name will auto-populate.
4. Set Variable Values
   1. Row 1:
      1. Field: Subject
      2. Value: Prospect removed from Sales Engagement Cadence
         
   2. Click Add Assignment
   3. Row 2:
      1. Field: Status
      2. Value: Not Started
   4. Click Add Assignment
   5. Row 3:
      1. Field: Priority
      2. Value: High
   6. Click Add Assignment
   7. Row 4:
      1. Field: ActivityDate
      2. Value: {!$Flow.CurrentDate}
         
   8. Click Add Assignment
   9. Row 5:
      1. Field: WhoId
      2. Value: {!Loop_Through_Leads.Id}
         
   10. Click Add Assignment
   11. Row 6:
       1. Field: OwnerId
       2. Value: {!Loop_Through_Leads.OwnerId}
5. Click Done.

Step 2.5: Adding an Assignment Element to Add the Record Variable to Record Collection Variable

1. Create a Record Collection Variable varR_Tasks type Task to store record variable (created in step 2.4) for the bulk process.
2. On Flow Designer, click on the +icon and select the Assignment element. 
3. Enter a name in the Label the API Name will auto-populate.
4. Set Variable Values
   1. Row 1:
      1. Field: {!varR_Tasks}
      2. Operator: Add
      3. Value: {!varR_Task}
5. Click Done.

Step 2.6: Adding a Create Records Element to Create Tasks

1. On Flow Designer, below the After Last node, click on the +icon and select the Create Records element. 
2. Enter a name in the Label the API Name will auto-populate.
3. For How Many Records to Create select Multiple.
4. Map Record Collection: {!varR_Tasks}
5. Click the X at the top to save your changes.

In the end, Benjamin’s Flow will look like the following screenshot:

Once everything looks good, perform the steps below: 

1. Click Save.
2. Enter Flow Label (CadenceTracker) the API Name will auto-populate.
3. API Version for Running the Flow: 59
4. Interview Label: CadenceTracker {!$Flow.CurrentDateTime}
5. Click Save.

Almost there! Once everything looks good, click the Activate button. 

Step 3: Asynchronous Apex Triggers for Change Events

You have the option to receive notifications for changes on the Lightning Platform by subscribing to change events through Apex triggers. While Apex triggers for change events share similarities with those for standard Salesforce objects, there are also notable distinctions. Much like traditional Apex triggers for Salesforce objects, you create a change event trigger for the specific change event associated with the Salesforce object. It’s worth noting that only after-insert triggers are supported in this context.

The change event trigger fires when one or a batch of change events is received. Unlike object triggers, change event triggers run asynchronously after the database transaction is completed. The asynchronous execution makes change event triggers ideal for processing resource-intensive business logic while keeping transaction-based logic in the object trigger. By decoupling the processing of changes, change event triggers can help reduce transaction processing time.

Change event triggers have these characteristics.

• They run under the Automated Process entity. As such, debug logs for the trigger are created by the Automated Process entity, and system fields, such as CreatedById and OwnerId, reference Automated Process.
• They are subject to Apex synchronous governor limits.
• They have a maximum batch size of 2,000 event messages (the number of items in Trigger.New).

1. Create an Apex Trigger on ActionCadenceTrackerChangeEvent object.
   Copy Code Copied Use a different Browser

   
   trigger ActionCadenceTrackerAsyncTrigger on ActionCadenceTrackerChangeEvent (after insert) {
       ActionCadenceTrackerAsyncTriggerHandler.handleChangeEvent(Trigger.new);
   }
   

2. Create an Apex class ActionCadenceTrackerAsyncTriggerHandler, as shown below.
   Copy Code Copied Use a different Browser

   
   public class ActionCadenceTrackerAsyncTriggerHandler {
       
       public static void handleChangeEvent(List<ActionCadenceTrackerChangeEvent> changeEvents) {
           Set<Id> actionCadenceTrackerIds = new Set<Id>();
           
           for(ActionCadenceTrackerChangeEvent event : changeEvents) {
               EventBus.ChangeEventHeader header = event.ChangeEventHeader;
               if (header.changetype == 'UPDATE' && event.CompletionReason == 'ManuallyRemoved') {
                   List<Id> recordIds = header.getRecordIds();
                   actionCadenceTrackerIds.addAll(recordIds);
               }
           }
           
           if(!actionCadenceTrackerIds.isEmpty()) {
               findRelatedLeads(actionCadenceTrackerIds);
           }
       }
       
       private static void findRelatedLeads (Set<Id> actionCadenceTrackerIds) {
           
           List<Lead> associatedLeads  = [Select Id, OwnerId 
                                          from Lead 
                                          where Id IN (SELECT targetId 
                                                       FROM ActionCadenceTracker 
                                                       WHERE Id IN :actionCadenceTrackerIds 
                                                       AND Target.Type = 'Lead')];
           
           if(!associatedLeads .isEmpty()) {
               runFlow(associatedLeads );
           }
       }
       
       private static void runFlow(List<Lead> leads) {
           Map<String, Object> params = new Map<String, Object>();
           params.put('varR_Leads', leads);
           Flow.Interview.CadenceTracker myFlow = new Flow.Interview.CadenceTracker(params);
           myFlow.start();
       }
   }