Repeat these steps whenever you need to look through a bunch of records
In less then 12 minutes, you’ll learn the five steps and be able to update the records in your collection.
Thanks to 100 Days of Trailhead for hosting this video on their YouTube channel and nudging me to make a follow up which will debut soon.
Continue reading 5 Steps of Flow LoopsInvocable methods used with Flow allow you to launch something in an admin friendly format that uses the massive power of Apex. For example, you have an intake screen that collects answers to a few questions, then you use Apex to loop through many related records dispersing those answers in places hard to reach from Flow.
Creating an invocable method in a nutshell: First you write an apex class with @invocable method (label and description) and whatever code you want the apex to do (easy, right?) Then make your Flow including your input and output variables. Then add an Apex action in Flow to send/receive those variables.
| Sent | Sent From | Received by | Received |
| Record Variable.id | Flow | Apex | List<Id> listOfIds |
| Record Collection Variable | Flow | Apex | List<List<Opportunity>> nameOfThis |
| List containing 1 sObject record | Apex | Flow | Record (single) variable |
| List of Lists of sObject | Apex | Flow | Record Collection Variable |
This is NOT an exhaustive list at all. I didn’t try sending a record variable (not just the ID from Flow), but I assume that will work. There are also generic sObjects that are pretty special, but I didn’t try.
Continue reading Invocable Methods: How to Send Data Between Flow and ApexThis is the second in a series on sending email with an embedded table of records of NPSP objects. The first post was a list of payments.
“Here is the use case: sending a family of a deceased relative one letter with all the names of people who have donated in memoriam. So, one letter to the family for many people who gave. Client is a large hospice so this is happening weekly. Open to different options — apps? exports & merge? other? Thanks!”
Rob asked in the Power of Us Hub, back in April
Well, I’m a few months late, but here you go, Rob. I made a Flow that sends out an email like the one below. I see now that you said “letter”…oops. Hopefully you figured out a solution by now, anyway!
Install this unmanaged package to try it out.
Continue reading Send Tables in Email in Flow – NPSP Example #2 Memorial GiftsBroad use case: Use the new Collection Sort feature in Flow to find a specific number of records that meet your criteria, and sort them with one or more criteria (criterion?)
Example use cases: I want my top 3 open opps to have a giant dollar sign image on them or I want to automatically nudge/shame the five users who logged in least last month or I want to focus a campaign on my most active volunteers in the summer.
Our specific case: I want to look at a contact record in Nonprofit Success Pack and see immediately that they are one of my top ten donors.
Install this unmanaged package to try it out.
Update: July 30, 2021 Now on the AppExchange!
Flow improved so much in 2020 (yes! a good thing actually happened in this Great-Pacific-Garbage-Patch of a year) that I was able to take out much of the complication of setting up this app.
And thanks to RAD Women Code courses 1 & 2, I was able to add a Visualforce controller and Apex Tests! I am so grateful to my incredible coaches and cohorts.
What matters for you is that it is much easier to install. It’s still not easy to install but hey, it’s 2021. You can handle what life throws at you.
Installation instructions here.
Requires Summer ‘21 and Salesforce Edition: Enterprise, Unlimited, Developer, Performance.
Continue reading Unsubscribe Link 3.10This post is building on the work of the super-smarty Narender Singh aka ForcePanda aka @Nads_P07. With Spring ’21 rich text emails, you can now send tables with lists of child objects.
I followed his tutorial and built two Flow’s specifically using Nonprofit Success Pack (NPSP) objects. The first one is a list of payments and the second is a list of completed volunteer activities. I’ll blog about the second one later. Also on the to-do list is to make one that lists all the gifts received in memory or in tribute to someone else.
In this scenario, I launch a Flow from a Visualforce page and finish the flow on a different Visualforce page instead of the standard “Your Flow Finished” page.
In earlier versions of my Unsubscribe Link app, the “Finish” button would take you a screen that said “YOUR FLOW FINISHED” which many of you pointed out, is less than ideal.
Screen one:
Screen two (old version):
And click “Finish” to get this beauty:
JULY 30, 2021 UPDATE: This version is now outdated! Please go here for the latest.
When the recipient clicks to unsubscribe, a flow will look for all contacts and leads who have this email in the Email field and mark them “Email Opt Out.” The email address owner will receive one confirmation email immediately. A custom object tracks when someone unsubscribes to allow you to report on it.
UPDATE: 1/28/21 I realized how to send the confirmation email from someone other than “Site Guest User.” More in this post.
Continue reading Unsubscribe LinkI built this really great app to allow email recipients to unsubscribe from all emails sent through Salesforce, but it hasn’t been exactly easy to set up or use. Introducing the first upgrade which makes it much more user friendly!
With the upgrade, your Salesforce users can now pull a merge field into their Lightning and Classic email templates to include the Unsubscribe Link. Bam. No more having to modify and clone confusing email templates.
I’m back from maternity leave and holy SMOKES (get it? The west coast is on fire): an update to Flow in Summer ’20 totally broke the Unsubscribe Link App. It’s okay, though. It’s fixed now and this Flow improvement is worth it.
It’s now much simpler to expose a Flow to folks who aren’t logged into Salesforce. They can click a link which launches a Flow that modifies, deletes and creates all sorts of records! (Be careful!)
All you have to do now is save your flow as System Context without Sharing–Access All Data. This eliminates the need to give a Site Guest User permission, adjust your sharing settings, and create sharing rules.
So my example is the Unsubscribe Link. You send an email through Salesforce with this link. Your recipient clicks on it and that launches the Flow which will update their contact and lead records with Email Opt Out. It’s pretty sweet.
https://yourSiteDomain/YourVisualforcePageName?flowVariable1={{{MergeField1}}}&FlowVariable2={{{MergeField1}}}In the Unsubscribe Link app, that looks like this. recordId and Email are two variables in my Flow. Everyone who sets up the app will substitute their site domain for “yourSiteDomain.”
http://yourSiteDomain/Unsubscribe?recordId={{{Recipient.Id}}}&Email={{{Recipient.Email}}}" When I put in my site domain and the fields are merged in the email, it looks like this:
https://powerfulsolutions-developer-edition.na139.force.com/Unsubscribe?recordId=0034W000029huR8&Email=georgeBailey@bbbs.comRead the instructions on the Unsubscribe Link App for details on how to create a Site and Site Domain.