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.Continue reading Send Emails with Tables in Flow – NPSP Example with Payments
In my Unsubscribe Link app, (yes, that again) the Flow sends out an email from the user running the Flow, which in that case is a Site Guest User. And the email comes from “[Insert Company Name] Site Guest User” which is weird and confusing. I’ve finally googled to learn the secrets of some fields in the Flow “Send Email” Action. And it’s pretty basic and very much a “why didn’t I google this before” moment.
In Flow’s “Send Email” Action, plug in an organization wide email addresses into “Sender Address” and type “OrgWideEmailAddress” in as Sender Type and bob’s your uncle. Want more of an explanation? Keep reading!Continue reading Send Email From Anyone* in Flow
Are you reading Samantha Shain’s blog The Data Are Alright yet? I LOVE how she talks through all the ups and downs of building her first flow – which is a really complicated one, by the way! She shares her thought processes, her research and her frustrations, pride and other feelings so openly. So if you see an increase in feelings shared here, you know who inspired me!
In Sam’s post, she mentions a few things that she had trouble figuring out. She uses a custom button or link with a URL to pass a record id to a Flow. As she guessed, there is a more elegant way to do it. So elegant even Lady Whistledown would approve.
CORRECTION: Sam tweeted “I got it from a Quick Action eventually on my own (I wish I had this resource then), but what I really needed was to pass in a *group* of ids from a list view… which afaik is not possible without code.”Continue reading Pass Record Id to Flow in Quick Action
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 two (old version):
And click “Finish” to get this beauty:Continue reading Your Flow Finished
Allow Recipients to Unsubscribe From All Email Sent via Salesforce
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.
See How It Works
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 Link 2.2
As the insanity that would be the year 2020 begins to wind down, now is a great time to reflect on all that you’ve learned this year and the work you’re especially proud of. I’ve gotten the opportunity to work on a lot of functionality and development of features this year, but for me the project that stands out the most is the configuration of a doc gen solution that involved Conga Composer and Conga Trigger. I had some previous experience with Conga Composer, but through this project, I learned more specifically about how robust Conga parameters are. Quick breakdown of how this solution works: the parameters are used to control the behavior of your doc gen solution (i.e., when and in what format your document generates and/or sends out via email) and can be built into a custom button that, when clicked, triggers generation with the parameters you’ve put in place. You can also go one step further with the use of Conga Trigger, which involves converting the custom button into a formula field, then integrating that field into a Workflow Rule and Action.Continue reading The Wonderful World of Conga Composer Parameters
This is the third iteration of my app to allow all users to opt out of email sent through Salesforce.
Last week I posted an add-on to the existing app to improve it. Here I have a totally new version with all the bells and whistles.
Could you please install it and test it for me? It should take about 10-15 minutes. After collecting enough feedback, I’ll submit this version to the AppExchange for security review.Continue reading Test the Newest Unsubscribe Link App, Please?
I 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.Continue reading Upgrade Unsubscribe Link
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.
How to Build your own externally visible Flow
- Create a screen Flow. (This is the hard part).
- Set up My Domain (it’s probably already set up).
- Create a Site domain.
- Create a new Site.
- Create a Visualforce Page to house the Flow.
- Build your link that includes variables for your flow. That looks like:
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.”
When I put in my site domain and the fields are merged in the email, it looks like this:
Read the instructions on the Unsubscribe Link App for details on how to create a Site and Site Domain.
Lashonna is a Technical Analyst for the run:CRM team at Slalom. In her role, she assists with various areas of Salesforce customization and maintenance, including composing user stories, testing, and building out enhancements for existing orgs. Lashonna was recently appointed as a board member for the non-profit organization, Amplify, which helps to empower underrepresented voices in tech, and provide resources to those who may not otherwise have access.