A common need in Flows is to be able to redirect the user to a new record that may have been created in the Flow. This new Lightning Flow Action can be used to redirect the user to the specified record in either View Mode or Edit Mode.
The admins at https://bigassforce.com wrote a blog on how you can create a list button that launches a flow and pass the selected record ids to be processed by the flow using an undocumented flow variable
Narender Singh form https://forcepanda.wordpress.com posted a series of blogs on how to add validation to custom flow screen components:
Narender Singh created a flow screen component for a dependent picklist tha supports picklist value selection based on the record type.
https://forcepanda.wordpress.com/2019/06/11/flow-screen-component-dependent-picklists-with-recordtype-and-multiselect-picklist-support/
Douglas Ayers and Michelle Hansen developed an Apex trigger that could know when a file was being shared to a record and then call an autolaunched flow where the business logic could be implemented declaratively.
Ever wanted to inject Einstein Next Best Action into your Flows? Check out this post by Marc Baizman.
Due to huge code contributions from Eric Smith and datapharmer, the Lookup screen component has been substantially enhanced.
a) You can now filter the Lookup component based on a particular field:
b) but you can also choose to filter based on a where clause.
For example, if you wish to return only accounts of type “Vendor” or “Partner” you could enter the Object Name: “Account” and the where clause: “Type=’Vendor’ or Type=’Partner’
c) Finally, you can even create Dependent Lookup components, where the user looks something up in component 1, and then component 2 is filtered baed on the component 1 selection:
2. New NavigateToSObject Local Action
This great new action component from Salesforce Flow VP Arnab Bose provides a powerful new tool for controlling finish behavior. For example, you might have a flow that generates a work record. At the end of the flow, you can use this component to load the work record into your browser automatically.
Note that like all Local Action, this one requires that Spring ’18 orgs be enrolled in the open pilot, which you can request from support. Summer ’18 orgs will have this functionally generally available.
3. Summer ’18 versions of Local Actions Available
Summer ’18 orgs are starting to become available over the next 8 weeks. If you have one, your Spring ’18 Local Actions will stop working because of some changes made to interface names. However, Summer ’18 versions of all of the local actions at www.lightningflow.net are now available.