Why This Is Useful
Look, this one isn’t useful in the traditional sense. Let’s be honest with each other.
Here’s the case for it anyway. Even though you and I might think the things we build are cool and interesting, Janet from Sales is really not having the time of her life in Salesforce. She’s in there eight hours a day updating opportunity stages.
So let’s do something nice for Janet. Let’s lay some Easter eggs around the org so that occasionally, when she moves a deal to Closed Won, something delightful happens.
It costs you twenty minutes and it’s completely out of the box.
The Confetti Bit
Salesforce ships a genuine confetti animation and most people have no idea. It’s a Flow element.
Build a Screen Flow, add the Confetti component to a screen, and you’re most of the way there. Configure the density and how long it runs, then trigger the Flow from wherever makes sense.
I’ve covered this properly in my post on confetti celebrations and the Trailhead audio player, which also covers playing sound, because of course it does.
The classic use is firing it when an Opportunity hits Closed Won. Janet closes a deal, confetti happens, Janet’s day is measurably better. That’s a real thing you can do this afternoon.
Going Further
Once you’ve got the basic mechanism, the fun is in where you hide things.
Trigger on unexpected field changes. Not just the obvious stage change. Something that fires occasionally on a field nobody expects is much funnier than something predictable.
Make it rare. Confetti on every single save stops being delightful within about a day and becomes an annoyance by day three. Add a condition so it fires on genuinely notable events, or randomly with low probability.
Use custom notifications. A well-timed toast message with something silly in it costs nothing and catches people off guard nicely.
Custom Labels are your friend. Put your message text in a Custom Label and you can change the joke without touching the Flow. Also means you can turn it off instantly.
The Sensible Warnings
Right, I have to say some responsible things now.
Tell somebody. Do not let a colleague discover this while debugging a production issue at 11pm. That’s not a fun surprise, that’s a confusing one. Document it somewhere findable.
Build an off switch. A Custom Setting or Custom Metadata checkbox that disables the whole thing. Because the day will come when somebody’s doing a demo to an executive and confetti is not what anyone needs.
Read the room. An org handling medical records or bereavement claims is not the place for surprise animations. Know your users.
Watch the performance. Adding a Flow to every save on your busiest object for a joke is a bad trade. Keep it light and keep it targeted.
Don’t do it on your first week. Establish that you’re competent before you establish that you’re funny.
Genuinely Though
There’s a real point buried in the silliness here.
Most people’s experience of Salesforce is a form they fill in because their job requires it. If a small, well-judged bit of delight makes the system feel like something a human built rather than something imposed on them, that’s worth twenty minutes.
User adoption is a genuine problem on most implementations, and people engage more with systems they don’t resent. Not a substitute for good UX, obviously. But not nothing either.
Go make Janet’s day.
Get Coding With The Force Merch!!
We now have a redbubble store setup so you can buy cool Coding With The Force merchandise! Please check it out! Every purchase goes to supporting the blog and YouTube channel.
Get Shirts Here!
Get Cups, Artwork, Coffee Cups, Bags, Masks and more here!
Check Out More Coding With The Force Stuff!
If you liked this post make sure to follow us on all our social media outlets to stay as up to date as possible with everything!
Youtube
Patreon
Github
Facebook
Twitter
Instagram
Salesforce Development Books I Recommend
Advanced Apex Programming
Salesforce Lightning Platform Enterprise Architecture
Mastering Salesforce DevOps
Good Non-SF Specific Development Books:
Clean Code
Clean Architecture
