‘Flowspiration’: Why I Embraced Salesforce Automation

Share this article...

To those who know me in the Salesforce community, it won’t surprise them to hear me say I’m a flownatic – an Automation Champion, obsessed with automation! What may surprise is the reason why: I’m lazy and a little forgetful! I’ve worked out that if I put in maximum effort up front, I can exert minimal effort later.

Automation in Salesforce – though it may take weeks to plan, future proof, test, handle errors, etc – allows me to know that, once active, it will always do the same thing on the same schedule (whether time based or action triggered), even if I forget all the things it is going to do.

“Salesforce”

There is another reason I embraced automation: for most of my Salesforce career I’ve been a solo admin. With regular tasks to perform and no holiday/sickness cover, I needed a way to keep the lights on when I wasn’t there, rather than work backing up. Automation, in its various forms, gave me a way to let users help themselves: simply press a button or fill in a field and my automation will do the rest, be that simple (alert the record owner, create a task) or complex (update the financial forecast taking into account cost, margin, value, changes in realisation date, different profit take rules, anomalies due to business unit etc).

I’ll admit, some of the automation I built in the past would have been better handled in Apex. But when you’re a solo admin with no developer support and no budget to hire someone, you just make do.

That said, it amazes me that more admins don’t embrace automation, and take those first steps. It doesn’t have to just make your user’s lives’ simpler – it can also be adopted to make your life as an admin easier.

 

Automation isn’t just for User actions – it can help the System Administrator too

 

Example Salesforce Flows

Here’s some “flowspiration” for business processes you could automate:

  • Do you have an on-boarding process that could be automated?
    Use Process Builder to create learning tasks for the new User, remind their manager to arrange various briefings, post a welcome message to chatter so everyone knows who the new starter is.
  • Do you handle PII (personally identifiable information) cases?
    Create a Screen Flow to guide users through deleting/redacting records themselves. Flows can be run in ‘System Mode’ meaning you could use them to allow users to edit and delete records they would not normally have permission to touch.
  • Do you forget to remove feature licences from deactivated Users?
    Use Autolaunched Flow to remove these, plus more. Build in an alert to the Sys Admin if deactivating the User leaves a Queue empty. You could schedule the deactivation – when you know the User is leaving the company add the date to their User record and let automation do the rest.

 

What other Admin tasks can you think of that you could automate? Why not give them a go – in a sandbox, developer org or trailhead playground first, of course!

 

If you are completely new to automation, I highly recommend starting in Trailhead with the Lightning Flow module before trying to replicate my project

 

Add Comment