Ultimate Salesforce Flow Crash Course

แชร์
ฝัง
  • เผยแพร่เมื่อ 17 ม.ค. 2023
  • Check out Tim's Ultimate Flow Foundation Course here: courses.salesforceben.com/ult...
    Are you a new admin just getting started with Salesforce Flow? With an array of exciting new enhancements and Workflow Rules & Process Builder shuffling ever closer to retirement, it's the perfect time to learn.
    Join us for a crash course with Flow expert, Tim Combridge, who will be sharing his top tips and insights, covering everything you need to know as you get started with Flow.
  • บันเทิง

ความคิดเห็น • 19

  • @_taylor_v
    @_taylor_v 8 หลายเดือนก่อน +6

    - 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.

  • @K007N1
    @K007N1 ปีที่แล้ว +2

    Thank you for this session. It was really helpful to understand Flows. Loved it. I'll stay tuned for more such informative sessions.

    • @OfficialSFBen
      @OfficialSFBen  ปีที่แล้ว

      So glad to know our video was helpful. Thank you so much for the support!

  • @alexcarroll9774
    @alexcarroll9774 11 หลายเดือนก่อน

    Thanks for this!

    • @OfficialSFBen
      @OfficialSFBen  11 หลายเดือนก่อน

      Glad we could help Alex!

  • @tornubarikoboo4102
    @tornubarikoboo4102 ปีที่แล้ว

    Great Content!

  • @linodref
    @linodref ปีที่แล้ว +1

    Gj guys, your content is excellent, keep it up

    • @OfficialSFBen
      @OfficialSFBen  ปีที่แล้ว

      Thanks for your feedback Federico!

  • @konkalaedanna7845
    @konkalaedanna7845 8 หลายเดือนก่อน

    Thank you

    • @OfficialSFBen
      @OfficialSFBen  8 หลายเดือนก่อน

      No worries at all!

  • @Finite8614
    @Finite8614 6 หลายเดือนก่อน

    great intro! please make the recording at least 1080p (and preferably higher) next time

  • @TWHCTV
    @TWHCTV 4 หลายเดือนก่อน

    quality nice work

    • @OfficialSFBen
      @OfficialSFBen  4 หลายเดือนก่อน

      Much appreciated!

  • @ALCRAN2010
    @ALCRAN2010 10 หลายเดือนก่อน

    Which Salesforce Certification(s) get a person to this position within a company?

    • @OfficialSFBen
      @OfficialSFBen  10 หลายเดือนก่อน +1

      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/

  • @muneerahmad5530
    @muneerahmad5530 ปีที่แล้ว +1

    I don't know why he is using 2 conditions instead of just first one? Can someone explain it to me please!

    • @sensiblegiraffe
      @sensiblegiraffe ปีที่แล้ว +7

      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 🙂

    • @muneerahmad5530
      @muneerahmad5530 ปีที่แล้ว +1

      @@sensiblegiraffe thanks for clearing this doubt ❤️