Winter 22 features

27 de Sep de 2021

Más contenido relacionado

Presentaciones para ti(20)


Winter 22 features

  1. Salesforce Admin Group, Trichy New Salesforce Flow Features to Shout About in Winter ’22
  2. Kadhar Basha J Salesforce Admin Group, Trichy Trailblazer Community Group Leader Salesforce Admin Group, Trichy
  3. Salesforce Admin Group, Trichy Speaker Pradeepkumar S Associate consultant Infosys
  4. Today’s Agenda • Introduction • Record Triggered Flow • Outbound Message in Flow • Configuring Batch Size • How to Invoke Subflow? • Debugging • How to Reconnect Flow Elements? • Screen Flow • Questions & Answers
  5. Record-Triggered Flow Start Element Changes Logo • Setting up the Record-Triggered Flow Start Element used to be a multi-step process. • Now, those steps have been combined into one and enhanced further. • The ‘Object’ and ‘Trigger’ sections are now on one single page, which pops up when you create the Flow.
  6. Record-Triggered Flow Start Element Changes Logo You can also optimize the Flow for a specific action set: • Fast Field Updates: a high-performance Flow designed to run before the record is saved, and will only update fields on the record that triggered the Flow • Actions and Related Records: which will run after the record has been inserted, designed to make updates, or perform actions like Send Email or Outbound etc or make changes in related to the record (but not make changes to the record itself). Note: The Actions and Related Records optimization can also be made to run asynchronously.
  7. Record Triggered Flow Old Start Element
  8. Record Triggered Flow New Start Element Logo
  9. Send Outbound Message with Salesforce Flow Logo • Outbound Messages are now available as an action in the Flow Builder. • Outbound Messages send messages to external services, beyond Salesforce. • This is a major addition that will solidify Flow’s reputation as the go-to Salesforce automation for all admins.
  10. Outbound Message in Flow action Logo
  11. DEMO Outbound Message using Flow Flow Link
  12. Configure Batch Size for Scheduled Paths in Record-Triggered Flows Logo • If you’re adding a Scheduled Path to a Record-Triggered Flow and want to be able to control the number of interviews executed within a Batch, now you can! • If you’ve got some more complex actions lined up and need to restrict the number of records that are run at the same time, simply reduce the Batch Size. It’s not recommended to increase it above the default of 200 for performance reasons (and the fact that you’ll be more likely to run into issues with Apex governor limits).
  13. Configure Batch Size for Scheduled Paths in Record-Triggered Flows Logo
  14. New ‘Minutes’ Options for Offsets (for Scheduled Paths in Record-Triggered Flows) • If you created or edited a Record-Triggered Flow prior to Winter ‘22, you’d only have the option to offset a scheduled path by days or hours. • Now, in Winter ‘22, you have the ability to offset it by minutes. • This may be useful in a fast-paced sales team when a lead comes in and you want to schedule a number of actions to be executed in quick succession.
  15. New ‘Minutes’ Options for Offsets (for Scheduled Paths in Record-Triggered Flows) Scheduled Flow Link
  16. Call a Subflow from a Record-Triggered Flow Logo • Record-Triggered Flows now can call Subflows. This was previously restricted to other Flow types. • Now, allow complex logic to be reused across multiple Record-Triggered Flows without having to be rebuilt each time.
  17. Call a Subflow from a Record-Triggered Flow Logo Main flow link
  18. Call a Subflow from a Record-Triggered Flow Logo Subflow link
  19. Debugging Enhancements for Record-Triggered Flow Logo • When debugging a Record-Triggered Flow with more than one path in Winter ‘22, the very first thing you’ll be asked to do is select which path you’d like to test. • This is valuable, making it easier for you to design more complex Flows and test each leg of it thoroughly.
  20. Debugging Enhancements for Record-Triggered Flow
  21. Ability to Reconnect Flow Elements in Auto-Layout Logo • One of the biggest issues many people have encountered with Auto-Layout Flows (myself included) is that if a slight adjustment is required to a path, you sometimes need to switch Auto-Layout off, make the change, and then switch it back on. • Looks like this is coming to an end in Winter ‘22, with the ability to reconnect elements throughout a Flow with ease.
  22. Relabel the Navigation Buttons in a Screen Flow There are times when Pause, Previous, and Next just aren’t quite exciting enough to define your navigation within your Flow. Flow link
  23. Screen Flow: New Roll Back Records Element This isn’t something I saw coming – I thought Data elements would forever be limited to Create, Read, Update, and Delete (CRUD). That’s not to say this new Data element won’t be incredibly useful! Introducing, Roll Back Records!
  24. Screen Flow: New Roll Back Records Element Rolling back your Data element changes would be useful in situations where: • A Flow encounters an error, • A user gets to a certain point in a Flow and decides they need more information before committing their changes • Or, some custom validation has been implemented to align with business rules and any breaches should be reverted. Flow link
  25. Any Questions so far
  26. 2 more minutes please !!! Workflow and Process builder are going to be Deprecated? Share us :