This article provides a detailed guide on creating a record-triggered flow that activates upon the creation or update of an Opportunity. The flow evaluates the presence of related Opportunity Product Schedules. If none are found, it generated a task assigned to the Opportunity Owner to ensure timely follow-up or necessary action.
Step 1: Create a new Record Triggered Flow on the Opportunity object, with the following values
| Object | Opportunity |
| Configure Trigger | A record is created or updated |
| Conditions Requirements | None |
| Optimize the Flow for | Actions and Related Records |
Step 2: Now add a Get Records Element, In the Get Records Element, substitute the following values:
Notes :
| Label | Get Opportunity Products |
| Description | Provide any suitable description |
| Object | Opportunity Product |
| Condition Requirements | All Conditions Are Met (AND) |
| Logic | HasSchedule Equals {!$GlobalConstant.True} |
| How Many Records to Store | Only the first record |
Step 3 : Add a Decision Element to check if there were any schedules found or not
{!Get_Opportunity_Products} is Not NULL, it means that the schedules were found and we will End the Flow{!Get_Opportunity_Products} is Null, it means that the scheduled were not found and we will proceed to create a task for the Opportunity owner
Step 4: Under the Not Found branch of the Decision Element add a New Task Action Element and fill in the task details
| Label | Give it appropriate name |
| Assign To ID | {!$Record.OwnerId} |
| Related To ID | {!$Record.Id} |
| Status | Not Started (Give it an appropriate status) |
| Subject | Give it an appropriate subject |
Step 5: Save and Activate the Flow
________________________________________________________________
Written by: Sumeet Negi | Forum Ambassador
Sumeet Negi is a Salesforce CPQ Developer and one of the Forum Ambassador in the Trailblazer Community. He is 6x Salesforce certified and has more than 5.5 years of experience on the Salesforce platform. He is passionate about helping trailblazers get the most out of Trailblazer Community.
Submissions reflect only the opinions of the user who made available the Submission and not the opinions of Salesforce, regardless of whether the user is affiliated with Salesforce, and may contain or constitute products, services, information, data, content and other materials made available by or on behalf of third parties ("Third Party Materials). Salesforce neither controls nor endorses, nor is Salesforce responsible for, any Third Party Materials, including their accuracy, validity, timeliness, completeness, reliability, integrity, quality, legality, usefulness or safety, or any applicable intellectual property rights. Any Submissions made available through any message board or forum in response to posted questions, or that otherwise purports to answer any questions, including any questions about Salesforce or Programs, are made available for your general knowledge only and should never be relied upon as answers to your specific questions (even if an answer is marked as a “best” answer or with any similar qualifications). You should always contact Salesforce support for answers to your specific questions. Salesforce has no control over Submissions, and is not responsible for any use or misuse (including any distribution) by any third party of Submissions.
If you have questions, tap into the wisdom of our entire Trailblazer Community here: https://trailhead.salesforce.com/trailblazer-community/feed
004630365

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.