Visit My YouTube Channel - Technical Potpourri

How to Run part of the Flow after the Triggering Event | Spring 21 New Feature

by Sudipta Deb | Dec 21, 2020 | admin, Advanced Admin, flow, New Feature, Record Triggered Flow, Salesforce Release, Spring 21 | 0 comments

If you are a Salesforce Flow fan, I am sure like me, Spring 21 release is going to excite you as well. If you are dealing with situations where you need to take actions based on some future dates, till today, you can either write scheduled action in Process Builder or time-dependent actions in workflow rules. But with Spring 21 release you can implement the same in flow. This post will show you how you can take advantage of this new cool feature. I also created a video explaining the steps.

You can check my other posts which talk about some of the flow enhancements that are coming along with Spring 21 release.

Use Case:

Here is the use case which I will be implementing –

Step 1

Create a Record-Trigerred Flow and choose Freeform/Auto-Layout in the next screen.

 

Step 2

Configure the Trigger Screen as –

  • Trigger the Flow When: A record is created or updated
  • Run the Flow: After the record is saved [Note – Schedule action/path is only available after the record is saved.]

Step 3

Configure the object as “Opportunity” with the criteria to make sure flow is running only when the opportunity is open.
Important – Select “Only when a record is updated to meet the condition requirements” under the “When to run the Flow for updated records” option. This is important, otherwise, you will not find the option to configure the schedule path.

Step 4

Configure the schedule path as shown below. You will find the option in the Start element 

Step 5

Configure the immediate action. First, create the Assignment to update the checkbox and then Update the Opportunity record. You can connect them with Start element as Immediate Action.

Step 6

Configure the scheduled action. First, create the Assignment to create a task and then create the Task record. You can connect them with Start element as Scheduled Action.

Final Flow

I hope this blog post is helpful. Let me know your feedback in the comment section.
I have also created a short video showing the steps to implement this use case.

Written by

More posts by

Related Posts

New Apex Method | Extracting Picklist Values Based on Record Type Inside Apex

New Apex Method | Extracting Picklist Values Based on Record Type Inside Apex

Jan 19, 2026 | , , , ,

For years, Salesforce developers have faced a common challenge: programmatically retrieving picklist values that are specific to a certain Record Type directly within Apex. The “solutions” often involved either complex SOQL queries against metadata, relying on the UI API (with its associated callout limits and serialization overhead), or maintaining clunky custom metadata/settings.

Good news, Technical Potpourri readers! The Salesforce Spring ’26 release is bringing a game-changer that will significantly simplify your Apex code and improve performance: native Apex methods to filter picklist values by Record Type!

read more...
Apex Cursor and Its Advantages Over Batch Processing

Apex Cursor and Its Advantages Over Batch Processing

Jan 15, 2026 | , , , , , ,

Struggling with large datasets and SOQL governor limits in Salesforce? In this video, I will dive deep into Apex Cursors, the powerful new feature that revolutionizes how we process millions of records.

Apex Cursors allow developers to navigate through query results in manageable chunks within a single transaction or across Queueable jobs. In this video, I will show you the correct way to implement Apex Cursor and also when this is an exception, how to handle that and perform retry.

read more...

0 Comments

Leave a Reply