- 1:45 Intros - 2:30 Why flow / what is flow / flow types / Apex (code) / Approval Processes / Actions / Lightning Pages (Flow can be embedded) / Retirement Timeline - 16:20 Why should/must you learn Flow - 19:27 Demo of a Flow in action - 22:35 Looking at the Flow from the demo - 40:20 Looking at the Screen Flow (for each of the created Installation items from the first flow) - 51:00 Recap and Best Practices - 54:30 Q&A (one flow per object? When to use Apex instead of Flow? Thanks for posting this. Very helpful.
How exactly did you set up that installation items object that appears in the related list of the installation record ? What exactly did you so that the opportunity products appear on the Installation items records?
You can stuck into Flow in a number of positions, and developers will typically always use Flow as part of their job, so that's a good place to start. If you want to exceed beyond a developer, check out our certification infographic here to see the different pathways you can take: www.salesforceben.com/salesforce-certification-pathways/
Hey @muneerahmad5530, great question! I assume you're referring to these two Conditions: IsWon | Is Changed | TRUE AND IsWon | Equals | TRUE I'll start with the second one - we want to make sure the automation is ONLY triggered when the Opportunity is marked as won. In your org, you may have multiple different Stages that are considered "Won" in the backend (ie. Closed Won, Settled, Sold, etc), so we use the 'IsWon' flag instead of a literal StageName value. The reason for the first one - we're checking to make sure that in this particular update the IsWon value has changed. We don't want a brand new Installation record created every single time the Opportunity is update AFTER it is set to Closed Won (ie. let's say there was a process to continue updating fields after the sale is done, those would also trigger the Flow without the IsChanged check because the record IS being updated, and the IsWon IS equal to TRUE). By adding IsChanged, we're ensuring that the IsWon PRIOR VALUE was not equal to TRUE, but it is now after this particular update. I hope that makes sense! I appreciate you watching and hope you got some value from the video 🙂
![เจ็บที่ยังฮัก - ม่อน วรวิทย์ [ Official Mv ] จอนนี่มิวสิค](http://i.ytimg.com/vi/KALIGSRSjFs/mqdefault.jpg)
- 1:45 Intros
- 2:30 Why flow / what is flow / flow types / Apex (code) / Approval Processes / Actions / Lightning Pages (Flow can be embedded) / Retirement Timeline
- 16:20 Why should/must you learn Flow
- 19:27 Demo of a Flow in action
- 22:35 Looking at the Flow from the demo
- 40:20 Looking at the Screen Flow (for each of the created Installation items from the first flow)
- 51:00 Recap and Best Practices
- 54:30 Q&A (one flow per object? When to use Apex instead of Flow?
Thanks for posting this. Very helpful.
Thank you for this session. It was really helpful to understand Flows. Loved it. I'll stay tuned for more such informative sessions.
So glad to know our video was helpful. Thank you so much for the support!
Very informative and helpful explanation for beginners!!!
We're so glad we could help!
great intro! please make the recording at least 1080p (and preferably higher) next time
How exactly did you set up that installation items object that appears in the related list of the installation record ? What exactly did you so that the opportunity products appear on the Installation items records?
quality nice work
Much appreciated!
Gj guys, your content is excellent, keep it up
Thanks for your feedback Federico!
Thank you
No worries at all!
Thanks for this!
Glad we could help Alex!
Which Salesforce Certification(s) get a person to this position within a company?
You can stuck into Flow in a number of positions, and developers will typically always use Flow as part of their job, so that's a good place to start. If you want to exceed beyond a developer, check out our certification infographic here to see the different pathways you can take: www.salesforceben.com/salesforce-certification-pathways/
Great Content!
Really glad you enjoyed it!
I don't know why he is using 2 conditions instead of just first one? Can someone explain it to me please!
Hey @muneerahmad5530, great question!
I assume you're referring to these two Conditions:
IsWon | Is Changed | TRUE
AND
IsWon | Equals | TRUE
I'll start with the second one - we want to make sure the automation is ONLY triggered when the Opportunity is marked as won. In your org, you may have multiple different Stages that are considered "Won" in the backend (ie. Closed Won, Settled, Sold, etc), so we use the 'IsWon' flag instead of a literal StageName value.
The reason for the first one - we're checking to make sure that in this particular update the IsWon value has changed. We don't want a brand new Installation record created every single time the Opportunity is update AFTER it is set to Closed Won (ie. let's say there was a process to continue updating fields after the sale is done, those would also trigger the Flow without the IsChanged check because the record IS being updated, and the IsWon IS equal to TRUE). By adding IsChanged, we're ensuring that the IsWon PRIOR VALUE was not equal to TRUE, but it is now after this particular update.
I hope that makes sense! I appreciate you watching and hope you got some value from the video 🙂
@@sensiblegiraffe thanks for clearing this doubt ❤️