My last blog post was on July 8th, which is over a month ago. It turns out that you get a lot busier when your baby starts to crawl and you hadn’t quite baby-proofed the stairs yet. Who knew? Someone should really warn you about these things.
It seems like all my time is now eaten up with:
- Picking my son up off the floor, pulling the dog bowl out of his grasp, and moving him back to the living room
- Eating and sleeping
Pretty much in that order
So instead of my planned Login Flows v2 that I thought I would have easily completed by now, I thought I’d write a quick post on a few other things like becoming an MVP, Dreamforce, GTD, and what I have planned for some upcoming blog posts.
It’s not often I get excited thinking about the possibilities for something, but as of Summer ’15 I don’t see a reason why every Salesforce org shouldn’t have at least one Login Flow queued up and ready to be used at the switch of a custom setting
Login Flow is one of those underrated pieces of Salesforce that people just haven’t started using yet. I think that entering the world of Flow can be scary for a lot of people, and at first glance it also appears relatively inflexible. You can set a message, but you have to set the same message for everyone in a profile, you assign it by profile, and to change the message you have to create a new version of the flow. Just saying the words “New Version” is enough to scare off clients with a structured deployment and ALM process
This question came up on the Success Community today which triggered my memory on the release notes, which got me thinking how we can really make this work and be flexible for both messaging, and also the timing of when the message is used.
My last post explained how to leverage Process Builder and Web to Lead functionality to create a record for any object in Salesforce directly from a website.
At the end of that post I said I needed to still figure out how to delete the garbage lead that I just created, but that I’d be back to show people how, so here I am.
Web-to-Lead and Web-to-Case have been around for a long time and are a great way to capture information from a website and have it logged right in Salesforce.
But what if you wanted to use them for something different instead? Like a “Web-to-Anything” form?
Using a Developer Org is a great way to practice setting up one of these, using Process Builder to turn the lead/case into just about anything else, and seeing how it works before trying to apply it to a specific business case.
Here is how I game the Web-to-Lead process to create something else instead: